From: "Gao, Liming" <liming.gao@intel.com>
To: Laszlo Ersek <lersek@redhat.com>, Bruce Cran <bruce@cran.org.uk>,
"edk2-devel@ml01.01.org" <edk2-devel@ml01.01.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: NOOPT OVMF build (or otherwise with optimizations disabled)
Date: Fri, 23 Sep 2016 02:44:53 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14B47BF36@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <c6729144-453e-0c6a-0a40-89ac6d4c1eaa@redhat.com>
Thanks! Ok for yonghong.
> -----Original Message-----
> From: Laszlo Ersek [mailto:lersek@redhat.com]
> Sent: Friday, September 23, 2016 10:44 AM
> To: Gao, Liming <liming.gao@intel.com>; Bruce Cran <bruce@cran.org.uk>;
> edk2-devel@ml01.01.org
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>; Zhu, Yonghong
> <yonghong.zhu@intel.com>
> Subject: Re: [edk2] NOOPT OVMF build (or otherwise with optimizations
> disabled)
>
> On 09/22/16 06:52, Gao, Liming wrote:
> > Laszlo:
> > Yes. GCC tool chain has no NOOPT setting in tools_def.txt. Could you
> > help submit one bug in Bugzilla?
>
> I filed <https://bugzilla.tianocore.org/show_bug.cgi?id=129>.
>
> Since all (open?) BaseTools BZs seem to be assigned to Yonghong at the
> moment, I followed suit here. If that's not okay, please modify the
> Assignee field accordingly.
>
> Thanks!
> Laszlo
>
> >> -----Original Message-----
> >> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> >> Laszlo Ersek
> >> Sent: Thursday, September 22, 2016 11:41 AM
> >> To: Bruce Cran <bruce@cran.org.uk>; edk2-devel@ml01.01.org
> >> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> >> Subject: Re: [edk2] NOOPT OVMF build (or otherwise with optimizations
> >> disabled)
> >>
> >> On 09/22/16 05:02, Bruce Cran wrote:
> >>> Would it be possible to either have a NOOPT build for OVMF added, or
> >>> have the DEBUG build disable optimizations? Personally I'd expect
> >>> debug builds in general to disable optimizations to allow easy
> >>> source-level debugging, but it seems the decision has been made to
> keep
> >>> optimizations enabled for EDK2 and have a NOOPT configuration for
> >>> debugging?
> >>
> >> Yes, I seem to recall that DEBUG means optimizations enabled, but debug
> >> code (such as DEBUG(), ASSERT(), DEBUG_CODE(...),
> ASSERT_EFI_ERROR())
> >> included. Indeed NOOPT seems to be what edk2 assigns generally to the
> >> build you'd like.
> >>
> >> A NOOPT build target for OVMF (and more generally for GCC toolchains I
> >> guess?) should be possible, likely even welcome, I believe. If only
> >> someone contributed such BaseTools patches. :)
> >>
> >> ('git grep -e NOOPT --and -e GCC -- BaseTools' returns no hits.)
> >>
> >> Thanks
> >> Laszlo
> >>
> >> _______________________________________________
> >> edk2-devel mailing list
> >> edk2-devel@lists.01.org
> >> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2016-09-23 2:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 3:02 NOOPT OVMF build (or otherwise with optimizations disabled) Bruce Cran
2016-09-22 3:40 ` Laszlo Ersek
2016-09-22 4:52 ` Gao, Liming
2016-09-23 2:43 ` Laszlo Ersek
2016-09-23 2:44 ` Zhu, Yonghong
2016-09-23 2:44 ` Gao, Liming [this message]
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=4A89E2EF3DFEDB4C8BFDE51014F606A14B47BF36@shsmsx102.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