From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Magnus Granberg <zorry@gentoo.org>,
libc-alpha <libc-alpha@sourceware.org>
Cc: nd <nd@arm.com>
Subject: Re: [PATCH] Bug 20662: checking whether x86_64-pc-linux-gnu-gcc implicitly enables -fstack-protector no (32bit gcc 6.2.0 pie and ssp enable)
Date: Fri, 21 Oct 2016 08:58:00 -0000 [thread overview]
Message-ID: <5809D8A0.7030906@arm.com> (raw)
In-Reply-To: <1784772.eOhSpX4WhJ@laptop1.gw.ume.nu>
On 20/10/16 21:01, Magnus Granberg wrote:
> When glibc get compile with gcc 6.2 that have been configured with
> --enable-default-pie and --enable-default-ssp. The check that check if the
> compiler use -fstack-protector as default fail on the 32bit part.
>
i'm not against this patch, just note that any reasonable ssp
implementation would not make a call in case of failure, but
crash the application immediately, i hope gcc will have an
option in the future to do that, which means this check will
not work (the test would have to look for canary access, which
is target specific).
next prev parent reply other threads:[~2016-10-21 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 20:02 Magnus Granberg
2016-10-21 8:58 ` Szabolcs Nagy [this message]
2016-10-22 13:03 ` Magnus Granberg
2016-11-15 19:37 ` [PATCH/committed 2.23] configure: accept __stack_chk_fail_local for ssp support too [BZ #20662] Mike Frysinger
2016-11-15 19:37 ` [PATCH] Bug 20662: checking whether x86_64-pc-linux-gnu-gcc implicitly enables -fstack-protector no (32bit gcc 6.2.0 pie and ssp enable) Mike Frysinger
2016-11-15 19:37 ` [PATCH/committed 2.24] configure: accept __stack_chk_fail_local for ssp support too [BZ #20662] Mike Frysinger
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-all 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=5809D8A0.7030906@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=zorry@gentoo.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).