From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, bob.c.feng@intel.com
Cc: Liming Gao <liming.gao@intel.com>
Subject: Re: [edk2-devel] [Patch 2/2] BaseTools: Add GCC flags to Basetool build.
Date: Tue, 30 Apr 2019 18:06:51 +0200 [thread overview]
Message-ID: <cddfff36-f1c1-27cb-a6df-f23c71c9d88b@redhat.com> (raw)
In-Reply-To: <20190430110701.12360-1-bob.c.feng@intel.com>
On 04/30/19 13:07, Bob Feng wrote:
> BZ:https://bugzilla.tianocore.org/show_bug.cgi?id=1764
>
> Some compiler flags restrict the compiler from making
> arbitrary decisions while handling undefined C/C++ behaviors.
> Therefore they can be used to fix some issues caused by undefined behavior.
>
> For example, for GCC, the following flags are available:
> -fno-delete-null-pointer-checks tells
> the compiler NOT to assume that null pointer deference does not exist.
> -fwrapv tells the compiler that signed overflow always wraps.
>
> This patch is going to add these 2 build options to
> BaseTool GCC build option.
>
> Signed-off-by: Bob Feng <bob.c.feng@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> ---
> BaseTools/Source/C/Makefiles/header.makefile | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/BaseTools/Source/C/Makefiles/header.makefile b/BaseTools/Source/C/Makefiles/header.makefile
> index c2397b796c..eac295b4dd 100644
> --- a/BaseTools/Source/C/Makefiles/header.makefile
> +++ b/BaseTools/Source/C/Makefiles/header.makefile
> @@ -69,11 +69,12 @@ BUILD_OPTFLAGS = -O2 $(EXTRA_OPTFLAGS)
> ifeq ($(DARWIN),Darwin)
> # assume clang or clang compatible flags on OS X
> BUILD_CFLAGS = -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror \
> -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g
> else
> -BUILD_CFLAGS = -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror \
> +BUILD_CFLAGS = -MD -fshort-wchar -fno-strict-aliasing -fwrapv \
> +-fno-delete-null-pointer-checks -Wall -Werror \
> -Wno-deprecated-declarations -Wno-stringop-truncation -Wno-restrict \
> -Wno-unused-result -nostdlib -g
> endif
> BUILD_LFLAGS =
> BUILD_CXXFLAGS = -Wno-unused-result
>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
prev parent reply other threads:[~2019-04-30 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 11:07 [Patch 2/2] BaseTools: Add GCC flags to Basetool build Bob Feng
2019-04-30 16:06 ` Laszlo Ersek [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=cddfff36-f1c1-27cb-a6df-f23c71c9d88b@redhat.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