public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "juha.kallioinen at nokia dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/48183] New: ICE [arm] immed_double_const at emit-rtl.c (-mfpu=neon -g -O1) Date: Fri, 18 Mar 2011 15:54:00 -0000 [thread overview] Message-ID: <bug-48183-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48183 Summary: ICE [arm] immed_double_const at emit-rtl.c (-mfpu=neon -g -O1) Product: gcc Version: 4.5.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: juha.kallioinen@nokia.com Created attachment 23707 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23707 pre-processed source When compiling the attached pre-processed source for arm (-march=armv7-a -mtune=cortex-a8) and using options -mfpu=neon -g -O1 I get an ICE. kaltsi@kaltsnatty:~/tmp/ice$ arm-linux-gnueabi-gcc-4.5 -mfpu=neon -O1 -g -c emit-rtl-ice.i optimized.c: In function ‘move_16bit_to_32bit’: optimized.c:4:6: internal compiler error: in immed_double_const, at emit-rtl.c:552 Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-4.5/README.Bugs> for instructions. This does not happen if I leave the -g option out. Also reported to linaro: https://bugs.launchpad.net/gcc-linaro/+bug/736007
next reply other threads:[~2011-03-18 15:48 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-18 15:54 juha.kallioinen at nokia dot com [this message] 2011-04-04 20:54 ` [Bug target/48183] " ramana at gcc dot gnu.org 2011-12-01 19:58 ` havard.graff at gmail dot com 2014-07-09 8:35 ` 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-48183-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: 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).