public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "belagod at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64231] [5 Regression] SIGSEGV building glibc on aarch64-linux-gnu from r217852
Date: Thu, 15 Jan 2015 14:39:00 -0000 [thread overview]
Message-ID: <bug-64231-4-xtR5Bae2uU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64231-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64231
--- Comment #13 from Tejas Belagod <belagod at gcc dot gnu.org> ---
(In reply to Sandra Loosemore from comment #12)
> I'm using a 4.7.3 based gcc as the host compiler (built from one of our own
> CodeBench release branches).
>
> Regardless of whether the actual failure is reproducible, if you look at the
> code I pointed at in comment 7, there is clearly a bug here: if
> force_const_mem returns NULL, GCC will crash, not just here but in several
> other places as well.
I tried with a build of cross aarch64-linux-gnu with 4.7.4 as the host compiler
and my gcc sources at HEAD and r217852 of trunk, but no luck! :-(
next prev parent reply other threads:[~2015-01-15 14:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 1:43 [Bug target/64231] New: " sandra at codesourcery dot com
2014-12-09 1:47 ` [Bug target/64231] " pinskia at gcc dot gnu.org
2014-12-09 1:48 ` pinskia at gcc dot gnu.org
2014-12-09 3:16 ` sandra at codesourcery dot com
2014-12-09 3:19 ` sandra at codesourcery dot com
2014-12-09 9:23 ` ktkachov at gcc dot gnu.org
2014-12-09 12:38 ` [Bug target/64231] [5 Regression] " rguenth at gcc dot gnu.org
2014-12-09 16:54 ` sandra at codesourcery dot com
2014-12-09 21:27 ` sandra at codesourcery dot com
2014-12-15 15:54 ` belagod at gcc dot gnu.org
2015-01-13 14:26 ` ramana at gcc dot gnu.org
2015-01-13 14:31 ` pinskia at gcc dot gnu.org
2015-01-13 15:05 ` ramana at gcc dot gnu.org
2015-01-13 15:10 ` sandra at codesourcery dot com
2015-01-15 14:39 ` belagod at gcc dot gnu.org [this message]
2015-01-15 16:28 ` belagod at gcc dot gnu.org
2015-01-21 2:41 ` pinskia at gcc dot gnu.org
2015-01-21 8:11 ` jakub at gcc dot gnu.org
2015-01-22 14:18 ` jakub at gcc dot gnu.org
2015-01-23 10:27 ` ramana at gcc dot gnu.org
2015-02-02 15:55 ` belagod at gcc dot gnu.org
2015-02-02 15:59 ` belagod at gcc dot gnu.org
2015-04-15 8:12 ` clyon 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-64231-4-xtR5Bae2uU@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).