public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sandra at codesourcery dot com" <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: Tue, 09 Dec 2014 16:54:00 -0000 [thread overview] Message-ID: <bug-64231-4-K0spTM179D@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 #6 from Sandra Loosemore <sandra at codesourcery dot com> --- This reproduces it for me; my build is at r217852. $ aarch64-linux-gnu-gcc argp-help.i -c -O2 argp-help.c: In function '_help': argp-help.c:1684:1: internal compiler error: Segmentation fault 0x874f9b0 crash_signal /scratch/sandra/aarch64-fsf/src/gcc-mainline/gcc/toplev.c:359 0x8406cfb plus_constant(machine_mode, rtx_def*, long long, bool) /scratch/sandra/aarch64-fsf/src/gcc-mainline/gcc/explow.c:120 0x82e2db2 init_alias_analysis() /scratch/sandra/aarch64-fsf/src/gcc-mainline/gcc/alias.c:2966 0x8b59681 cse_main /scratch/sandra/aarch64-fsf/src/gcc-mainline/gcc/cse.c:6597 0x8b5a5eb rest_of_handle_cse2 /scratch/sandra/aarch64-fsf/src/gcc-mainline/gcc/cse.c:7528 0x8b5a5eb execute /scratch/sandra/aarch64-fsf/src/gcc-mainline/gcc/cse.c:7581 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions. When I have a chance, I'll see if I can dig up some more information out of the debugger and/or reduce the testcase enough to allow setting some breakpoints.
next prev parent reply other threads:[~2014-12-09 16:54 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 [this message] 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 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-K0spTM179D@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: linkBe 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).