From: Bruce Cran <bruce@cran.org.uk>
To: Laszlo Ersek <lersek@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "Jordan Justen (Intel address)" <jordan.l.justen@intel.com>,
edk2-devel@ml01.01.org, Liming Gao <liming.gao@intel.com>,
andrey.warkentin@gmail.com
Subject: Re: [Patch] BaseTools: support the NOOPT target with the GCC tool chains
Date: Mon, 3 Oct 2016 10:13:11 -0600 [thread overview]
Message-ID: <8704782d-411a-e085-eaf3-b177f36ffa1c@cran.org.uk> (raw)
In-Reply-To: <162b108f-7fc1-8402-0bd5-dcb099f0a0a8@redhat.com>
On 10/3/2016 10:09 AM, Laszlo Ersek wrote:
> "BaseTools/Scripts/GccBase.lds" discards the gnu_debuglink section --
> intentionally, from commit efe690cab3fb5 ("BaseTools GCC: add unified
> GCC linker script for all archs and versions").
>
> If this section is necessary for debugging, then why does the DEBUG
> build work? In other words, why does the DEBUG build contain
> gnu_debuglink despite the discard rule? Ard, any idea?
tools_def.template contains a command to add it:
DEBUG_*_*_OBJCOPY_ADDDEBUGFLAG =
--add-gnu-debuglink=$(DEBUG_DIR)/$(MODULE_NAME).debug
I've followed up with the original email to say that adding a NOOPT line
fixes debugging for me.
--
Bruce
next prev parent reply other threads:[~2016-10-03 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 7:44 [Patch] BaseTools: support the NOOPT target with the GCC tool chains Yonghong Zhu
2016-09-30 10:11 ` Laszlo Ersek
2016-10-03 1:45 ` Bruce Cran
2016-10-03 8:59 ` Laszlo Ersek
2016-10-03 16:02 ` Bruce Cran
2016-10-03 16:09 ` Laszlo Ersek
2016-10-03 16:13 ` Bruce Cran [this message]
2016-10-03 16:53 ` Laszlo Ersek
2016-10-05 1:32 ` Zhu, Yonghong
2016-10-03 16:11 ` Bruce Cran
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=8704782d-411a-e085-eaf3-b177f36ffa1c@cran.org.uk \
--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