public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "antoine.balestrat at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/55111] New: ICE: tree check: expected ssa_name, have integer_cst in live_on_edge, at tree-vrp.c:89 Date: Sun, 28 Oct 2012 19:17:00 -0000 [thread overview] Message-ID: <bug-55111-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55111 Bug #: 55111 Summary: ICE: tree check: expected ssa_name, have integer_cst in live_on_edge, at tree-vrp.c:89 Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: antoine.balestrat@gmail.com With GCC 4.8.0 as of 20121021, at -O2 and higher : $ cat ssa.c int a, b, c; long d; unsigned long *e; int f(void) { for(;; a++) { if(c) { for(b = d = 0; b < 1; b++) e = &d; --*e; if(d > 0) a = 0; return d; } } } $ xgcc -O2 -w ssa.c ssa.c: In function ‘f’: ssa.c:5:5: internal compiler error: tree check: expected ssa_name, have integer_cst in live_on_edge, at tree-vrp.c:89 int f(void) ^ linux-vdso.so.1: No such file or directory 0xa90b9a tree_check_failed(tree_node const*, char const*, int, char const*, ...) ../../srcdir/gcc/tree.c:8896 0xa7650d tree_check ../../srcdir/gcc/tree.h:3676 0xa7650d live_on_edge ../../srcdir/gcc/tree-vrp.c:89 0xa7ce9a register_edge_assert_for_2 ../../srcdir/gcc/tree-vrp.c:4736 0xa7e4e0 register_edge_assert_for ../../srcdir/gcc/tree-vrp.c:5216 0xa81734 find_conditional_asserts ../../srcdir/gcc/tree-vrp.c:5304 0xa81734 find_assert_locations_1 ../../srcdir/gcc/tree-vrp.c:5518 0xa88136 find_assert_locations ../../srcdir/gcc/tree-vrp.c:5658 0xa88136 insert_range_assertions ../../srcdir/gcc/tree-vrp.c:5846 0xa88136 execute_vrp ../../srcdir/gcc/tree-vrp.c:9156 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.
next reply other threads:[~2012-10-28 19:17 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-28 19:17 antoine.balestrat at gmail dot com [this message] 2012-10-29 13:42 ` [Bug tree-optimization/55111] " mpolacek at gcc dot gnu.org 2012-10-29 14:46 ` [Bug tree-optimization/55111] [4.8 Regression] " rguenth at gcc dot gnu.org 2012-10-30 10:28 ` rguenth at gcc dot gnu.org 2012-10-30 12:03 ` rguenth at gcc dot gnu.org 2012-10-30 12:03 ` 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-55111-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).