public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/31041] New: ice for legal code with -O2 -ftree-vectorize Date: Mon, 05 Mar 2007 10:50:00 -0000 [thread overview] Message-ID: <bug-31041-9596@http.gcc.gnu.org/bugzilla/> (raw) I just tried to compile a Suse Linux package with the GNU C++ compiler version 4.3 snapshot 20070302. The compiler said utrie.c: In function 'utrie_open_3_4': utrie.c:51: error: invalid operand to binary operator (int) j_93; utrie.c:51: error: incorrect sharing of tree nodes vect_cst_.1224_132 = {(int) j_93, stmp_var_.1221_129, stmp_var_.1222_130, stmp_var_.1223_131}; (int) j_93; utrie.c:51: internal compiler error: verify_stmts failed Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. Preprocessed source code attached. Flags -O2 -ftree-vectorize required. -- Summary: ice for legal code with -O2 -ftree-vectorize Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: dcb314 at hotmail dot com GCC host triplet: x86_64-suse-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31041
next reply other threads:[~2007-03-05 10:50 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-03-05 10:50 dcb314 at hotmail dot com [this message] 2007-03-05 10:51 ` [Bug c/31041] " dcb314 at hotmail dot com 2007-03-05 13:09 ` tbm at cyrius dot com 2007-03-05 13:11 ` [Bug c/31041] [4.3 Regression] ice (verify_stmts failed: invalid operand to binary operator) " tbm at gcc dot gnu dot org 2007-03-05 13:47 ` [Bug c/31041] [4.3 Regression] verify_stmts failed: invalid operand to binary operator " rguenth at gcc dot gnu dot org 2007-03-05 20:16 ` [Bug tree-optimization/31041] " dorit at il dot ibm dot com 2007-03-17 14:43 ` dorit at gcc dot gnu dot org 2007-04-15 6:09 ` pinskia at gcc dot gnu dot org 2008-03-03 16:21 ` tprince at computer dot 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-31041-9596@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).