From: "Rebecca Cran" <rebecca@nuviainc.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: devel@edk2.groups.io, Leif Lindholm <leif@nuviainc.com>,
"Liming Gao (Byosoft address)" <gaoliming@byosoft.com.cn>,
Ard Biesheuvel <ardb+tianocore@kernel.org>
Subject: Re: [edk2-devel] GCC49 DEBUG AARCH64 and ARM builds use -O0
Date: Tue, 13 Apr 2021 06:12:44 -0600 [thread overview]
Message-ID: <8d7b63bb-a143-c836-5689-b265e4c0a92b@nuviainc.com> (raw)
In-Reply-To: <13e8c66f-2282-7fcd-b9ea-07bb063bc635@redhat.com>
+Ard (with the correct email address)
On 4/13/21 4:32 AM, Laszlo Ersek wrote:
> +Liming
>
> On 04/12/21 17:10, Rebecca Cran wrote:
>> I noticed the GCC49 (and GCC48) AARCH64 and ARM DEBUG builds use -O0,
>> unlike IA32 and X64 platforms which build with -Os.
>>
>> e.g. from
>> https://github.com/tianocore/edk2/blob/master/BaseTools/Conf/tools_def.template
>> :
>>
>> DEBUG_GCC49_AARCH64_CC_FLAGS = DEF(GCC49_AARCH64_CC_FLAGS) -O0
>>
>> Is that deliberate, or should it be like X64 where DEBUG builds are
>> optimized and NOOPT is used when unoptimized binaries are needed?
>>
>
> Seems to go back to commit dafe0fedc508 ("BaseTools: Add GCC49
> toolchain; align data sections to 0x40", 2014-07-28). My guess is that
> in 2014, gcc (4.9) may have had issues with arm64 code generation with -Os.
>
> You hint at DEBUG_GCC48_AARCH64_CC_FLAGS too, which seems like a
> promising clue at first -- because, perhaps the GCC49 flags in the
> above-mentioned commit had simply been modeled on the then-existent
> GCC48 ones.
>
> Unfortunately however, the GCC48 entry appeared in the
> less-than-helpfully-explained commit 2bc3256ca6d4 ("Sync BaseTool trunk
> (version r2640) into EDKII BaseTools.", 2014-01-10).
>
> Thanks
> Laszlo
>
next prev parent reply other threads:[~2021-04-13 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 15:10 GCC49 DEBUG AARCH64 and ARM builds use -O0 Rebecca Cran
2021-04-13 10:32 ` [edk2-devel] " Laszlo Ersek
2021-04-13 12:12 ` Rebecca Cran [this message]
2021-04-13 16:36 ` Ard Biesheuvel
2021-04-14 1:09 ` 回复: " gaoliming
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=8d7b63bb-a143-c836-5689-b265e4c0a92b@nuviainc.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