public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Yonghong Zhu <yonghong.zhu@intel.com>,
	 "edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>,
	Liming Gao <liming.gao@intel.com>
Subject: Re: [Patch V2] BaseTools: support the NOOPT target with the GCC tool chains
Date: Wed, 5 Oct 2016 17:06:59 +0100	[thread overview]
Message-ID: <CAKv+Gu-N36fXjapogcByC8GD6jWRPBhd5fPUh2Ap0Fq37DyJyw@mail.gmail.com> (raw)
In-Reply-To: <32c1e2a5-50e4-3152-0678-806f6bcc6bff@redhat.com>

On 5 October 2016 at 15:48, Laszlo Ersek <lersek@redhat.com> wrote:
> On 10/05/16 03:30, Yonghong Zhu wrote:
>> Update the tools_def.template to add NOOPT support with GCC tool chains.
>>
>> Cc: Liming Gao <liming.gao@intel.com>
>> Cc: Laszlo Ersek <lersek@redhat.com>
>> Contributed-under: TianoCore Contribution Agreement 1.0
>> Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
>> ---
>>  BaseTools/Conf/tools_def.template | 28 ++++++++++++++++++++++++++++
>>  1 file changed, 28 insertions(+)
>
> I thought I understood what was going on, but apparently I was wrong
> about that.
>
> In this patch, we add or modify:
> - NOOPT_*_*_OBJCOPY_ADDDEBUGFLAG -- okay
> - NOOPT_GCC*_(IA32|X64|ARM|AARCH64)_CC_FLAGS -- okay
>
> So that part is fine with me. But then we also add / modify:
> - NOOPT_GCC(49|5)_AARCH64_DLINK_(FLAGS|XIPFLAGS)
> - NOOPT_GCC5_ARM_DLINK_FLAGS
>
> First I thought the latter set of changes was unnecessary, because "ld"
> didn't use "-O". I checked the manual, and I was wrong: "ld" does know /
> use "-O". So those changes are fine, I guess.
>

Yes, especially under LTO, in which case code generation is performed
during the link stage, which should adhere to the same rules as the
compiler. This not only applies to -O, but also to things like
-march/-mcpu and -mstrict-align. This is why we pass all CFLAGS to the
linker for the GCC5 LTO builds.

> But then: is the patch *complete*? Because I can see some more DLINK
> stuff, for IA32 and X64 (not just ARM and AARCH64). Is it okay to ignore
> those? For example:
>
> *_GCC5_IA32_DLINK_FLAGS          = DEF(GCC5_IA32_X64_DLINK_FLAGS) -Os
> -Wl,-m,elf_i386,--oformat=elf32-i386
>
>
> *_GCC5_X64_DLINK_FLAGS           = DEF(GCC5_X64_DLINK_FLAGS) -Os
>
> Where GCC5_X64_DLINK_FLAGS and GCC5_IA32_X64_DLINK_FLAGS even include
> -flto. (I don't know if "-flto" hampers source level debugging or not.)
>

The GCC man page documents -flto as being a bad idea, i.e.,

"""
Link-time optimization does not work well with generation of debugging
information.  Combining -flto with -g is currently experimental and
expected to produce unexpected results.
"""

(which raises a philosophical question as well, i.e., to which extent
expected unexpected results are still unexpected results. But I
digress ...)

Another note: the DEBUG build for ARM and AARCH64 is essentially NOOPT
already, not DEBUG. How does this patch intend to deal with that?


  reply	other threads:[~2016-10-05 16:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05  1:30 [Patch V2] BaseTools: support the NOOPT target with the GCC tool chains Yonghong Zhu
2016-10-05 14:48 ` Laszlo Ersek
2016-10-05 16:06   ` Ard Biesheuvel [this message]
2016-10-05 17:56     ` Laszlo Ersek
2016-10-05 18:06       ` Ard Biesheuvel
2016-10-05 22:46         ` B Cran
2016-10-05 22:39 ` Bruce Cran
2016-10-06  8:19   ` Laszlo Ersek
2016-10-06  8:20     ` Ard Biesheuvel
2016-10-08  7:20       ` Gao, Liming

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=CAKv+Gu-N36fXjapogcByC8GD6jWRPBhd5fPUh2Ap0Fq37DyJyw@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