public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "regehr at cs dot utah.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/52073] New: ICE: vector VEC(vec_void_p,base) index domain error, in vinfo_for_stmt at tree-vectorizer.h:620 Date: Tue, 31 Jan 2012 21:46:00 -0000 [thread overview] Message-ID: <bug-52073-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52073 Bug #: 52073 Summary: ICE: vector VEC(vec_void_p,base) index domain error, in vinfo_for_stmt at tree-vectorizer.h:620 Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: regehr@cs.utah.edu CC: chenyang@cs.utah.edu [regehr@gamow tmp]$ current-gcc -v Using built-in specs. COLLECT_GCC=current-gcc COLLECT_LTO_WRAPPER=/uusoc/exports/scratch/regehr/z/compiler-install/gcc-r183767-install/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.7.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: ../configure --with-libelf=/usr/local --enable-lto --prefix=/home/regehr/z/compiler-install/gcc-r183767-install --program-prefix=r183767- --enable-languages=c,c++ Thread model: posix gcc version 4.7.0 20120131 (experimental) (GCC) [regehr@gamow tmp]$ current-gcc -Ofast small.c small.c: In function 'fn8': small.c:28:1: internal compiler error: vector VEC(vec_void_p,base) index domain error, in vinfo_for_stmt at tree-vectorizer.h:620 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. [regehr@gamow tmp]$ cat small.c int c; int fn3 () { return c; } int d; int fn4 (ui2) { d = ui2; return 0 == d; } struct S0 { }; int e; int f; int g; int h; static unsigned long long fn5 (unsigned char); void fn6 (struct S0); void fn7 (); struct S0 j; void fn8 () { fn6 (j); fn5 (0); } unsigned long long fn5 (unsigned char p_7) { for (;; h--) fn7 (); } void fn6 (struct S0 p_16) { e = 1; } int m; int n; void fn7 () { int p; lbl_140:p = fn3 (); if (f) { if (e) goto lbl_140; for (; m;) --g; } else for (n = 5; n; n--) p = fn4 (p); if (p) { } else f = 0; }
next reply other threads:[~2012-01-31 21:21 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-31 21:46 regehr at cs dot utah.edu [this message] 2012-01-31 22:20 ` [Bug tree-optimization/52073] [4.7 Regression] " jakub at gcc dot gnu.org 2012-02-01 9:43 ` jakub at gcc dot gnu.org 2012-02-01 9:46 ` jakub at gcc dot gnu.org 2012-02-01 10:43 ` irar at il dot ibm.com 2012-02-02 8:10 ` jakub at gcc dot gnu.org 2012-02-02 8:34 ` 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-52073-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).