From: "gaoliming" <gaoliming@byosoft.com.cn>
To: "'Oliver Steffen'" <osteffen@redhat.com>, <devel@edk2.groups.io>,
<ardb@kernel.org>
Cc: <bob.c.feng@intel.com>, <yuwei.chen@intel.com>
Subject: 回复: [PATCH v2 1/1] BaseTools: disable stack protector (gcc, AARCH64)
Date: Thu, 21 Apr 2022 09:27:51 +0800 [thread overview]
Message-ID: <000001d8551f$04a24480$0de6cd80$@byosoft.com.cn> (raw)
In-Reply-To: <20220420081603.27503-2-osteffen@redhat.com>
Oliver:
The change is good to me. I also include ARM maintainer Ard to review this
change.
Reviewed-by: Liming Gao <gaoliming@byosoft.com.cn>
Thanks
Liming
> -----邮件原件-----
> 发件人: Oliver Steffen <osteffen@redhat.com>
> 发送时间: 2022年4月20日 16:16
> 收件人: devel@edk2.groups.io
> 抄送: bob.c.feng@intel.com; gaoliming@byosoft.com.cn;
> yuwei.chen@intel.com; Oliver Steffen <osteffen@redhat.com>
> 主题: [PATCH v2 1/1] BaseTools: disable stack protector (gcc, AARCH64)
>
> Explicity disable the stack protection with
> -fno-stack-protection for builds using GCC on
> AARCH64.
>
> The gcc on Ubuntu enables -fstack-protector-strong
> by default starting with Ubuntu 21.10.
>
> GenFw fails if stack protection is enabled.
>
> Signed-off-by: Oliver Steffen <osteffen@redhat.com>
> ---
> BaseTools/Conf/tools_def.template | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/BaseTools/Conf/tools_def.template
> b/BaseTools/Conf/tools_def.template
> index 9c310cf23d25..1a49671a2708 100755
> --- a/BaseTools/Conf/tools_def.template
> +++ b/BaseTools/Conf/tools_def.template
> @@ -1915,7 +1915,7 @@ DEFINE GCC48_ARM_ASM_FLAGS =
> $(ARCHASM_FLAGS) $(PLATFORM_FLAGS) DEF(GC
> DEFINE GCC48_AARCH64_ASM_FLAGS = $(ARCHASM_FLAGS)
> $(PLATFORM_FLAGS) DEF(GCC_ASM_FLAGS) -mlittle-endian
> DEFINE GCC48_ARM_CC_FLAGS = $(ARCHCC_FLAGS)
> $(PLATFORM_FLAGS) DEF(GCC_ARM_CC_FLAGS) -fstack-protector
> -mword-relocations
> DEFINE GCC48_ARM_CC_XIPFLAGS =
> DEF(GCC_ARM_CC_XIPFLAGS)
> -DEFINE GCC48_AARCH64_CC_FLAGS = $(ARCHCC_FLAGS)
> $(PLATFORM_FLAGS) -mcmodel=large DEF(GCC_AARCH64_CC_FLAGS)
> +DEFINE GCC48_AARCH64_CC_FLAGS = $(ARCHCC_FLAGS)
> $(PLATFORM_FLAGS) -mcmodel=large DEF(GCC_AARCH64_CC_FLAGS)
> -fno-stack-protector
> DEFINE GCC48_AARCH64_CC_XIPFLAGS =
> DEF(GCC_AARCH64_CC_XIPFLAGS)
> DEFINE GCC48_ARM_DLINK_FLAGS =
> DEF(GCC_ARM_DLINK_FLAGS) -Wl,--oformat=elf32-littlearm
> DEFINE GCC48_ARM_DLINK2_FLAGS =
> DEF(GCC_DLINK2_FLAGS_COMMON)
> -Wl,--defsym=PECOFF_HEADER_SIZE=0x220
> --
> 2.36.0
prev parent reply other threads:[~2022-04-21 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16E78AC5D5F67B5F.27458@groups.io>
2022-04-20 8:16 ` [PATCH v2 0/1] BaseTools: disable stack protector (gcc, AARCH64) Oliver Steffen
2022-04-20 8:16 ` [PATCH v2 1/1] " Oliver Steffen
2022-04-21 1:27 ` gaoliming [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='000001d8551f$04a24480$0de6cd80$@byosoft.com.cn' \
--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