public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/63919] New: Segfault with r217560 building 462.libquantum from cpu2006
Date: Mon, 17 Nov 2014 17:24:00 -0000 [thread overview]
Message-ID: <bug-63919-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63919
Bug ID: 63919
Summary: Segfault with r217560 building 462.libquantum from
cpu2006
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: pthaugen at gcc dot gnu.org
CC: bergner at gcc dot gnu.org, dje at gcc dot gnu.org,
rguenth at gcc dot gnu.org
Host: powerpc64-unknown-linux-gnu
Target: powerpc64-unknown-linux-gnu
Build: powerpc64-unknown-linux-gnu
Created attachment 34004
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34004&action=edit
reduced testcase
462.libquantum fails to build with current trunk, bisected to r217560.
Attaching reduced testcase.
> gcc -c -m64 -O3 -ffast-math measure.c
gcc: internal compiler error: Segmentation fault (program cc1)
0x1000e6c7 execute
/home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/gcc.c:2912
0x1000f853 do_spec_1
/home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/gcc.c:4837
0x1000f5fb process_brace_body
/home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/gcc.c:6120
0x1000f5fb handle_braces
/home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/gcc.c:6034
0x1001077b do_spec_1
/home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/gcc.c:5491
0x1000f5fb process_brace_body
/home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/gcc.c:6120
...
next reply other threads:[~2014-11-17 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 17:24 pthaugen at gcc dot gnu.org [this message]
2014-11-17 17:47 ` [Bug tree-optimization/63919] " hjl.tools at gmail dot com
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-63919-4@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).