From: Pete Batard <pete@akeo.ie>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Gao, Liming" <liming.gao@intel.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH 0/4] Add ARM64 support for VS2017
Date: Fri, 16 Mar 2018 16:11:30 +0000 [thread overview]
Message-ID: <faa1422c-5888-3fe9-23a2-2243a546a3ba@akeo.ie> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E1E8137@SHSMSX104.ccr.corp.intel.com>
I understand where you're coming from, but that means I have to recreate
this patch set, and then create a new patch for the .S (because it makes
zero sense to require the same comment style on the .asm and not request
a follow through for the .S).
My time being limited, I'd rather only have to produce one new patch,
that will harmonize the comments for both .S and .asm at the same time.
The end result will be exactly the same, so I'm going to have to insist
that we split the comment harmonization (which is a very minor issue and
should hardly be seen as a showstopper for the patch series in the first
place) into a subsequent patch.
Thank you,
/Pete
On 2018.03.16 15:56, Gao, Liming wrote:
> Pete:
> I understand the existing .S file has the inconsistent comment style. I also know new added ASM files are converted from .S files. But, my comment is for this patch that adds new ASM files. I expect new added ASM files have the same style. If you check ARM arch ASM files, you will find they all have the same style.
>
> Thanks
> Liming
>> -----Original Message-----
>> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Pete Batard
>> Sent: Friday, March 16, 2018 7:04 PM
>> To: edk2-devel@lists.01.org
>> Cc: Gao, Liming <liming.gao@intel.com>; Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> Subject: Re: [edk2] [PATCH 0/4] Add ARM64 support for VS2017
>>
>> On 2018.03.16 08:24, Gao, Liming wrote:
>>> Pete:
>>> .S for GCC assembly, .asm for MSFT assembly. They can have the different comment style.
>>
>> Yes, but as I explained, the actual original issue is that our current
>> .S files do *not* have the same comment styles in the first place.
>>
>> If you look at MdePkg/Library/BaseLib/AArch64/SwitchStack.S, you'll see
>> that is uses '//' for comments, whereas other .S files, such as
>> MdePkg/Library/BaseLib/AArch64/SetJumpLongJump.S, use '#'.
>>
>> So that is our actual issue here: Regardless of VS2017, the GCC assembly
>> files for AARCH64 we currently have do not use the same comment style.
>>
>> Thus, the only reason why the .asm don't have the same comment style in
>> our proposal is because the .S, which we derived the .asm from, don't.
>> This means that either we should fix the .S too, or we shouldn't fix
>> anything at all.
>>
>>> Here, my comment is to make sure .asm files have the same comment style. I don't request to change .S file.
>>
>> And what I am saying is that it makes little sense to harmonize the
>> comment style for the .asm files, if we're not going to do the same for
>> the .S files as well. It just doesn't seem fair in my book to have the
>> VS2017 assembly files held to a higher standard than the GCC ones. So
>> either we need to fix both, or we fix none at all.
>>
>> But as I indicated in my last e-mail, I am planning to send an
>> additional patch that does comment harmonization, for both .S and .asm,
>> *after* this VS2017 series has been applied to mainline. So the change
>> you request will happen. Just not as part of this patch series.
>>
>> And the reason I have insist on splitting these changes is because, if
>> we have to alter the .S files to be consistent, then this comment
>> harmonization request should logically be handled separately from the
>> VS2017 effort.
>>
>> Please let me know if you still think having a future separate patch,
>> that will do .S and .asm comment harmonization, does not make sense.
>>
>> Regards,
>>
>> /Pete
>>
>>>
>>>> -----Original Message-----
>>>> From: Pete Batard [mailto:pete@akeo.ie]
>>>> Sent: Thursday, March 15, 2018 5:28 PM
>>>> To: Gao, Liming <liming.gao@intel.com>; edk2-devel@lists.01.org
>>>> Cc: ard.biesheuvel@linaro.org
>>>> Subject: Re: [PATCH 0/4] Add ARM64 support for VS2017
>>>>
>>>> Hi Liming,
>>>>
>>>> Thanks for reviewing the patches.
>>>>
>>>> On 2018.03.15 06:15, Gao, Liming wrote:
>>>>> Pete:
>>>>> For new added ASM file in BaseLib, could you use the same comment style
>>>>> for them? ASM use ; for the comment. Most of new files uses ; as the
>>>>> comment, but switchstack is not.
>>>>
>>>> This is because SwitchStack.asm is simply SwitchStack.S, with the GCC
>>>> assembler specifics removed, and MSVC assembler specifics added.
>>>>
>>>> I did not change the comment style from the original files, so the real
>>>> issue here is that our GCC assembly files for AARCH64 do not use the
>>>> same comment style.
>>>>
>>>> I'm fine with trying to harmonize the comment styles, but seeing as this
>>>> needs to be done for both the .S and .asm, I'd rather send a patch to do
>>>> that *after* these VS2017 changes have been applied, as I don't consider
>>>> this correction to in scope of this patch series (because logically, the
>>>> introduction of VS2017 should not alter any of the .S files, unless we
>>>> reuse them, which we don't).
>>>>
>>>> If you agree to apply this series, I'll make sure to send a non
>>>> VS2017-specific additional patch, that does what you request for both
>>>> the .S and .asm.
>>>>
>>>>> Besides, compared to Arm arch assembly
>>>>> file, I don't find CpuPause.asm. Is it required?
>>>>
>>>> That file doesn't exist for GCC (as you will see there is no
>>>> MdePkg/Library/BaseLib/AArch64/CpuPause.S), so we don't have one for
>>>> VS2017 either.
>>>>
>>>> Regards,
>>>>
>>>> /Pete
>>
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-03-16 16:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 9:49 [PATCH 0/4] Add ARM64 support for VS2017 Pete Batard
2018-02-23 9:50 ` [PATCH 1/4] MdePkg: Disable some Level 4 warnings for VS2017/ARM64 Pete Batard
2018-02-23 9:50 ` [PATCH 2/4] MdePkg/Library/BaseLib: Enable VS2017/ARM64 builds Pete Batard
2018-02-23 9:50 ` [PATCH 3/4] MdePkg/Include: Add VA list support for VS2017/ARM64 Pete Batard
2018-02-23 9:50 ` [PATCH 4/4] BaseTools/Conf: Add VS2017/ARM64 support Pete Batard
2018-02-23 11:55 ` [PATCH 0/4] Add ARM64 support for VS2017 Ard Biesheuvel
2018-02-23 13:14 ` Pete Batard
2018-03-15 6:15 ` Gao, Liming
2018-03-15 9:28 ` Pete Batard
2018-03-16 8:24 ` Gao, Liming
2018-03-16 11:03 ` Pete Batard
2018-03-16 15:56 ` Gao, Liming
2018-03-16 16:11 ` Pete Batard [this message]
2018-03-16 16:31 ` Gao, Liming
2018-03-16 16:35 ` Pete Batard
2018-03-19 9:07 ` Gao, Liming
-- strict thread matches above, loose matches on Subject: below --
2018-02-14 13:08 Pete Batard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=faa1422c-5888-3fe9-23a2-2243a546a3ba@akeo.ie \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox