From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>,
Andrew Fish <afish@apple.com>
Cc: Leif Lindholm <leif@nuviainc.com>
Subject: Re: [edk2-devel] AArch64 assembly compatibility for Xcode and GCC
Date: Wed, 5 Jan 2022 23:31:24 +0000 [thread overview]
Message-ID: <CAKbZUD3B=Uajs3Z+STNuPVuA5mutn_52izM3QD0EtL=33B27Lw@mail.gmail.com> (raw)
In-Reply-To: <962A1DA2-CB34-49F5-A721-AE7E5C82FA04@apple.com>
[-- Attachment #1: Type: text/plain, Size: 2232 bytes --]
Hi,
GNU Assembler and the clang assembler support more complex macros natively
(using the .macro and.endm directives), without the need for the C
preprocessor.
This completely sidesteps the need for explicit ";" as the GAS macros
respect newlines inside the macro.
See https://godbolt.org/z/6zzqoeKE4 for a very simple example.
Of course, you can also pass arguments, see
https://sourceware.org/binutils/docs/as/Macro.html for the full
documentation.
Best regards,
Pedro
On Wed, Jan 5, 2022 at 8:36 PM Andrew Fish via groups.io <afish=
apple.com@groups.io> wrote:
> I was playing around with getting Xcode to compile AArch64 code and I hit
> an interesting compatibility issue. The assembler line continuation token
> for GCC (;) is a comment for the Xcode clang assembler. For Xcode clang you
> need to use %%. Yikes [1]
>
> I was wondering if any one else has hit this in another project and if
> there was any cool workaround?
>
> The only thing I can think of is the “big hammer” on both (well you only
> need one) ends. We could replace ; with a #define that matches the
> assembler. It looks like this issue mostly hits in Code that is using C
> pre-processor macros so we could refactor the code. I’m a little concerned
> that the C pre processor is getting used since the macro languages of the
> assembler might also have some compatibility issues?
>
> Looking for ideas and opinions on the best way to fix this if we want to
> add Xcode as an ARM compiler in the future.
>
>
> [1]
> https://github.com/tianocore/edk2/blob/master/MdePkg/Library/BaseLib/AArch64/SetJumpLongJump.S#L13
>
> #define GPR_LAYOUT \
> REG_PAIR (x19, x20, 0); \
> REG_PAIR (x21, x22, 16); \
> REG_PAIR (x23, x24, 32); \
> REG_PAIR (x25, x26, 48); \
> REG_PAIR (x27, x28, 64); \
> REG_PAIR (x29, x30, 80);/*FP, LR*/ \
> REG_ONE (x16, 96) /*IP0*/
> I had to change it to:
>
> #define GPR_LAYOUT \
> REG_PAIR (x19, x20, 0)%% \
> REG_PAIR (x21, x22, 16)%% \
> REG_PAIR (x23, x24, 32)%% \
> REG_PAIR (x25, x26, 48)%% \
> REG_PAIR (x27, x28, 64)%% \
> REG_PAIR (x29, x30, 80)%%/*FP, LR*/ \
> REG_ONE (x16, 96) /*IP0*/
>
> Thanks,
>
> Andrew Fish
>
>
>
>
--
Pedro Falcato
[-- Attachment #2: Type: text/html, Size: 17350 bytes --]
next prev parent reply other threads:[~2022-01-05 23:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 20:36 AArch64 assembly compatibility for Xcode and GCC Andrew Fish
2022-01-05 23:31 ` Pedro Falcato [this message]
2022-01-06 10:38 ` [edk2-devel] " Akira Moroo
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='CAKbZUD3B=Uajs3Z+STNuPVuA5mutn_52izM3QD0EtL=33B27Lw@mail.gmail.com' \
--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