From: Laszlo Ersek <lersek@redhat.com>
To: Leif Lindholm <leif.lindholm@linaro.org>,
Alexei Fedorov <Alexei.Fedorov@arm.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"liming.gao@intel.com" <liming.gao@intel.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH 2/2] BaseTools/tools_def AARCH64: avoid SIMD register in XIP code
Date: Thu, 13 Jul 2017 22:09:30 +0200 [thread overview]
Message-ID: <86c37ee5-71d2-6fd5-7706-5505d38ba380@redhat.com> (raw)
In-Reply-To: <20170713173119.GG26676@bivouac.eciton.net>
On 07/13/17 19:31, Leif Lindholm wrote:
> How are you ending up with all of those -O3?
Sorry for butting in, but personally I consider -O3 "suicidal".
The only -O3's I can currently see in BaseTools are:
> Conf/tools_def.template:DEBUG_CLANG38_IA32_DLINK2_FLAGS = DEF(GCC5_IA32_DLINK2_FLAGS) -O3
> Conf/tools_def.template:RELEASE_CLANG38_IA32_DLINK2_FLAGS = DEF(GCC5_IA32_DLINK2_FLAGS) -O3
> Conf/tools_def.template:DEBUG_CLANG38_X64_DLINK2_FLAGS = DEF(GCC5_X64_DLINK2_FLAGS) -O3
> Conf/tools_def.template:RELEASE_CLANG38_X64_DLINK2_FLAGS = DEF(GCC5_X64_DLINK2_FLAGS) -O3
Since I don't use CLANG, I don't mind these, but for gcc, I would.
In the past, Liming once suggested -O3 for the build tools themselves
(via -Ofast) -- meaning full well, of course! --, and I protested:
http://mid.mail-archive.com/ed237dbc-25f0-d0a9-3252-9a503de67ee4@redhat.com
And so we have commit 202726b3ceb3 ("BaseTools Makefile: Enable O2
option for GCC tool chain", 2016-09-29) today.
... I realize my email can appear as FUD, but I think there's a reason
most distros build their packages with -O2. Even upstream Linux uses -O2
generally (the only mention of -O3 I find right now in "Makefile" is
about problems it causes with gcc-4.8).
Thanks
Laszlo
next prev parent reply other threads:[~2017-07-13 20:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 12:48 [PATCH 1/2] BaseTools/tools_def AARCH64: mark register x18 as reserved Ard Biesheuvel
2017-07-13 12:48 ` [PATCH 2/2] BaseTools/tools_def AARCH64: avoid SIMD register in XIP code Ard Biesheuvel
2017-07-13 14:11 ` Leif Lindholm
2017-07-13 16:15 ` Alexei Fedorov
2017-07-13 16:17 ` Ard Biesheuvel
[not found] ` <HE1PR0802MB2299B668C33778EC20CE6DDA9AAC0@HE1PR0802MB2299.eurprd08.prod.outlook.com>
2017-07-13 17:00 ` Ard Biesheuvel
2017-07-13 17:06 ` Alexei Fedorov
2017-07-13 17:31 ` Leif Lindholm
2017-07-13 20:09 ` Laszlo Ersek [this message]
2017-07-13 14:11 ` [PATCH 1/2] BaseTools/tools_def AARCH64: mark register x18 as reserved Leif Lindholm
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=86c37ee5-71d2-6fd5-7706-5505d38ba380@redhat.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