public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/45991] New: [4.6 Regression] ICE: verify_stmts failed: Invalid address operand in in TARGET_MEM_REF. with -fstrict-overflow Date: Tue, 12 Oct 2010 19:26:00 -0000 [thread overview] Message-ID: <bug-45991-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45991 Summary: [4.6 Regression] ICE: verify_stmts failed: Invalid address operand in in TARGET_MEM_REF. with -fstrict-overflow Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: zsojka@seznam.cz Created attachment 22024 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22024 reduced testcase Command line: $ gcc -O -fstrict-overflow pr45991.c Compiler output: $ gcc -O -fstrict-overflow pr45991.c pr45991.c: In function 'foo': pr45991.c:8:6: error: Invalid address operand in in TARGET_MEM_REF. # VUSE <.MEM_25> b_10 = MEM[symbol: A[20], index: ivtmp.9_20, offset: 0B]; pr45991.c:8:6: internal compiler error: verify_stmts failed Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. Tested revisions: r165354 - crash r163636 - OK 4.5 r163761 - OK
next reply other threads:[~2010-10-12 19:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-12 19:26 zsojka at seznam dot cz [this message] 2010-10-13 4:29 ` [Bug tree-optimization/45991] " hjl.tools at gmail dot com 2010-10-26 4:01 ` jakub at gcc dot gnu.org 2010-11-04 12:17 ` rguenth at gcc dot gnu.org 2010-11-04 12:29 ` rguenth at gcc dot gnu.org 2010-11-04 14:08 ` rguenth at gcc dot gnu.org 2010-11-04 14:08 ` rguenth 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-45991-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).