From: Bruce Cran <bruce@cran.org.uk>
To: Yonghong Zhu <yonghong.zhu@intel.com>, edk2-devel@lists.01.org
Cc: Laszlo Ersek <lersek@redhat.com>, Liming Gao <liming.gao@intel.com>
Subject: Re: [Patch V4] BaseTools: support the NOOPT target with the GCC tool chains
Date: Tue, 11 Oct 2016 09:16:37 -0600 [thread overview]
Message-ID: <056a28fe-e4d9-da57-72b6-73a65c8c225f@cran.org.uk> (raw)
In-Reply-To: <1476151236-43084-1-git-send-email-yonghong.zhu@intel.com>
On 10/10/2016 8:00 PM, Yonghong Zhu wrote:
> Update the tools_def.template to add NOOPT support with GCC tool chains.
> Also disable -flto and -Os in NOOPT target for GCC5.
>
> 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>
Tested-by: Bruce Cran <bruce.cran@sandisk.com>
Tested with GCC49 and GCC5 toolchain builds and verified neither causes
gdb single-stepping to jump around.
--
Bruce
next prev parent reply other threads:[~2016-10-11 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 2:00 [Patch V4] BaseTools: support the NOOPT target with the GCC tool chains Yonghong Zhu
2016-10-11 2:18 ` Gao, Liming
2016-10-11 12:45 ` Laszlo Ersek
2016-10-11 15:16 ` Bruce Cran [this message]
2016-10-11 15:24 ` Laszlo Ersek
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=056a28fe-e4d9-da57-72b6-73a65c8c225f@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