public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/56433] New: ICE in expand_asm_operands, at stmt.c:910 Date: Sat, 23 Feb 2013 03:41:00 -0000 [thread overview] Message-ID: <bug-56433-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56433 Bug #: 56433 Summary: ICE in expand_asm_operands, at stmt.c:910 Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned@gcc.gnu.org ReportedBy: doko@gcc.gnu.org Created attachment 29527 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29527 preprocessed source seen with trunk 195917, works with 4.7 branch, fails with Linaro branch, buildings without -O doesn't show the issue. $ gcc -c -marm -mfpu=neon -O1 -c dxa.i In file included from /scratch/packages/tmp/4.8/libav-0.8.5/libavutil/intreadwrite.h:60:0, from /scratch/packages/tmp/4.8/libav-0.8.5/libavformat/dxa.c:22: /scratch/packages/tmp/4.8/libav-0.8.5/libavutil/arm/intreadwrite.h: In function 'dxa_read_packet': /scratch/packages/tmp/4.8/libav-0.8.5/libavutil/arm/intreadwrite.h:45:5: internal compiler error: in expand_asm_operands, at stmt.c:910 __asm__ ("ldr %0, %1" : "=r"(v) : "m"(*(const uint32_t *)p)); ^ Please submit a full bug report, with preprocessed source if appropriate.
next reply other threads:[~2013-02-23 3:41 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-23 3:41 doko at gcc dot gnu.org [this message] 2013-02-23 5:23 ` [Bug middle-end/56433] [4.8 Regression] " pinskia at gcc dot gnu.org 2013-02-25 15:20 ` rguenth at gcc dot gnu.org 2013-02-25 19:31 ` jakub 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-56433-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).