From: "Zhu, Yonghong" <yonghong.zhu@intel.com>
To: Laszlo Ersek <lersek@redhat.com>, Bruce Cran <bruce@cran.org.uk>,
"Ard Biesheuvel" <ard.biesheuvel@linaro.org>
Cc: "Justen, Jordan L" <jordan.l.justen@intel.com>,
"edk2-devel@ml01.01.org" <edk2-devel@ml01.01.org>,
"Gao, Liming" <liming.gao@intel.com>,
"andrey.warkentin@gmail.com" <andrey.warkentin@gmail.com>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: [Patch] BaseTools: support the NOOPT target with the GCC tool chains
Date: Wed, 5 Oct 2016 01:32:05 +0000 [thread overview]
Message-ID: <B9726D6DCCFB8B4CA276A9169B02216D4F39803F@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <8a96524f-f936-8bf5-379c-743ca497a085@redhat.com>
Thanks Laszlo and Bruce!
I sent a V2 to add "NOOPT_*_*_OBJCOPY_ADDDEBUGFLAG = --add-gnu-debuglink=$(DEBUG_DIR)/$(MODULE_NAME).debug"
Best Regards,
Zhu Yonghong
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Laszlo Ersek
Sent: Tuesday, October 4, 2016 12:53 AM
To: Bruce Cran <bruce@cran.org.uk>; Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Justen, Jordan L <jordan.l.justen@intel.com>; edk2-devel@ml01.01.org; Gao, Liming <liming.gao@intel.com>; andrey.warkentin@gmail.com
Subject: Re: [edk2] [Patch] BaseTools: support the NOOPT target with the GCC tool chains
On 10/03/16 18:13, Bruce Cran wrote:
> 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.
>
Thank you, perfect!
Laszlo
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2016-10-05 1:32 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
2016-10-03 16:53 ` Laszlo Ersek
2016-10-05 1:32 ` Zhu, Yonghong [this message]
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=B9726D6DCCFB8B4CA276A9169B02216D4F39803F@SHSMSX103.ccr.corp.intel.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