public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/66780] [4.9 Regression] Compiling with -fstack-protector-strong causes binary to segfault
Date: Tue, 07 Jul 2015 12:43:00 -0000 [thread overview]
Message-ID: <bug-66780-4-mJO197Jv9K@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66780-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66780
--- Comment #4 from Kazumoto Kojima <kkojima at gcc dot gnu.org> ---
(In reply to John Paul Adrian Glaubitz from comment #2)
> Could this also be the cause for PR66312 and PR66563 after all?
My 2 cents.
I've just revert the problematic part on trunk after usual test.
I'll revert it on 4.9 when the usual test is done and to 5 when
the branch reopens.
next prev parent reply other threads:[~2015-07-07 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 15:32 [Bug target/66780] New: " glaubitz at physik dot fu-berlin.de
2015-07-07 8:54 ` [Bug target/66780] " glaubitz at physik dot fu-berlin.de
2015-07-07 11:04 ` rguenth at gcc dot gnu.org
2015-07-07 12:29 ` kkojima at gcc dot gnu.org
2015-07-07 12:43 ` kkojima at gcc dot gnu.org [this message]
2015-07-07 20:40 ` kkojima at gcc dot gnu.org
2015-07-10 9:50 ` kkojima at gcc dot gnu.org
2015-07-11 9:10 ` glaubitz at physik dot fu-berlin.de
2015-07-26 16:37 ` glaubitz at physik dot fu-berlin.de
2015-07-27 9:57 ` kkojima at gcc dot gnu.org
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=bug-66780-4-mJO197Jv9K@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).