From: Leif Lindholm <leif.lindholm@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH edk2-platforms] Silicon/SynQuacer: add stage 2 override translation tables for PCIe
Date: Tue, 27 Feb 2018 18:10:23 +0000 [thread overview]
Message-ID: <20180227181023.laplmremvchew535@bivouac.eciton.net> (raw)
In-Reply-To: <CAKv+Gu8DA0FKNbNGKzXCwQkh5B2-gvZj4tQ7YMGTCCyYrJ9E0A@mail.gmail.com>
On Tue, Feb 27, 2018 at 05:45:09PM +0000, Ard Biesheuvel wrote:
> >> > +[Sources]
> >> > + Stage2Tables.S
> >> > +
> >> > +[Packages]
> >> > + MdePkg/MdePkg.dec
> >> > + Silicon/Socionext/SynQuacer/SynQuacer.dec
> >> > +
> >> > +[BuildOptions]
> >> > + *_*_*_OBJCOPY_PATH == objcopy
> >> > + *_*_*_OBJCOPY_FLAGS == -I elf64-little -O binary -j .rodata
> >>
> >> I can improve this and fix Clang at the same time by adding
> >>
> >> *_*_*_ASM_FLAGS == -nostdlib
> >> -Wl,-e,0x81f8000,--section-start=.rodata=0x81f8000
> >> *_CLANG35_*_ASM_FLAGS = -no-integrated-as
> >> *_CLANG38_*_ASM_FLAGS = -no-integrated-as
> >>
> >> (and remove the linker arguments from the Makefile)
> >
> > I can confirm this resolves the CLANG issue.
> >
> > Could we do this with a CLANG_ALL_ASM_FLAGS, rather than listing each
> > new toolchain profile as they get added?
>
> No, not really. CLANG3x is not a separate toolchain family, so we can
> apply things to GCC+CLANG combined, or to certain versions
> individually.
Ah, I had managed to miss that bit up until now. Thanks!
In that case, with these latest changes:
Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
/
Leif
next prev parent reply other threads:[~2018-02-27 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 13:47 [PATCH edk2-platforms] Silicon/SynQuacer: add stage 2 override translation tables for PCIe Ard Biesheuvel
2018-02-27 17:19 ` Ard Biesheuvel
2018-02-27 17:36 ` Leif Lindholm
2018-02-27 17:45 ` Ard Biesheuvel
2018-02-27 18:10 ` Leif Lindholm [this message]
2018-02-28 9:18 ` Ard Biesheuvel
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=20180227181023.laplmremvchew535@bivouac.eciton.net \
--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