public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64152] New: internal compiler error: in gen_add2_insn
Date: Tue, 02 Dec 2014 14:11:00 -0000 [thread overview]
Message-ID: <bug-64152-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64152
Bug ID: 64152
Summary: internal compiler error: in gen_add2_insn
Product: gcc
Version: 4.9.3
Status: UNCONFIRMED
Keywords: ra
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target: aarch64
Created attachment 34163
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34163&action=edit
preprocessed testcase
When compiling the attached testcase with
-O -fPIC -fstack-protector -fomit-frame-pointer -mno-lra
I get
gen/wxe_funcs.cpp:31754:2: internal compiler error: in gen_add2_insn, at
optabs.c:4719
0xac23bb gen_add2_insn(rtx_def*, rtx_def*)
/space/rguenther/src/svn/gcc-4_9-branch/gcc/optabs.c:4719
0xb1dbd8 gen_reload
/space/rguenther/src/svn/gcc-4_9-branch/gcc/reload1.c:8713
0xb23327 emit_input_reload_insns
/space/rguenther/src/svn/gcc-4_9-branch/gcc/reload1.c:7669
0xb23327 do_input_reload
/space/rguenther/src/svn/gcc-4_9-branch/gcc/reload1.c:7955
0xb23327 emit_reload_insns
/space/rguenther/src/svn/gcc-4_9-branch/gcc/reload1.c:8147
0xb23327 reload_as_needed
/space/rguenther/src/svn/gcc-4_9-branch/gcc/reload1.c:4665
0xb27800 reload(rtx_def*, int)
/space/rguenther/src/svn/gcc-4_9-branch/gcc/reload1.c:1037
0xa2b588 do_reload
/space/rguenther/src/svn/gcc-4_9-branch/gcc/ira.c:5469
0xa2b588 rest_of_handle_reload
/space/rguenther/src/svn/gcc-4_9-branch/gcc/ira.c:5598
0xa2b588 execute
/space/rguenther/src/svn/gcc-4_9-branch/gcc/ira.c:5627
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.
this also happens on the 4.8 branch if you backport stack-protector support
and without -mno-lra (reload is still the default there).
On trunk things have rotted faster and I run into PR64149.
next reply other threads:[~2014-12-02 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 14:11 rguenth at gcc dot gnu.org [this message]
2014-12-02 14:17 ` [Bug target/64152] " rguenth at gcc dot gnu.org
2014-12-02 15:22 ` ktkachov at gcc dot gnu.org
2014-12-02 15:22 ` ktkachov 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-64152-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).