public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Ralf_Recker at gmx dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/22135] New: The gcc-4.1-20050611 compiler ICE's using -ftree-vectorize in conjunction with -fdump-tree-all-details-stats Date: Tue, 21 Jun 2005 07:14:00 -0000 [thread overview] Message-ID: <20050621071353.22135.Ralf_Recker@gmx.de> (raw) gcc-4.1-200506011 compiler ICE's using -ftree-vectorize AND -fdump-tree-all-details-stats in conjunction. Leave out one of both options and you got a successful compilation. Command: /opt/gcc-4.1-20050611/bin/gcc -O3 -march=pentium4 -msse3 -save-temps test.c -o test -ftree-vectorize -ftree-vectorizer-verbose=5 -fdump-tree-all-details-stats Error message: test.c: In function 'main': test.c:2: internal compiler error: in op_iter_init_maydef, at tree-flow-inline.h:1065 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. Source Code (I wrote a stupid little program to reproduce the error): int main(void) { int a[1024]; int b[1024]; int c[1024]; int i, j = 0; for (i = 0; i < 1024; i++) { a[i] = i; b[i] = 1023 - i; } for (i = 0; i < 1024; i++) c[i] = a[i] + b[i]; for (i = 0; i < 1024; i++) j = j + c[i]; return j; } P.S.: Placed under GPL by Ralf Recker <Ralf_Recker@gmx.de> :-) Preprocessed source: # 1 "test.c" # 0 "<built-in>" # 1 "<command line>" # 1 "test.c" int main(void) { int a[1024]; int b[1024]; int c[1024]; int i, j = 0; for (i = 0; i < 1024; i++) { a[i] = i; b[i] = 1023 - i; } for (i = 0; i < 1024; i++) c[i] = a[i] + b[i]; for (i = 0; i < 1024; i++) j = j + c[i]; return j; } -- Summary: The gcc-4.1-20050611 compiler ICE's using -ftree- vectorize in conjunction with -fdump-tree-all-details- stats Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: minor Priority: P2 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Ralf_Recker at gmx dot de CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i586-pc-linux-gnu GCC host triplet: i586-pc-linux-gnu GCC target triplet: i586-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22135
next reply other threads:[~2005-06-21 7:14 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-06-21 7:14 Ralf_Recker at gmx dot de [this message] 2005-06-21 7:25 ` [Bug tree-optimization/22135] " Ralf_Recker at gmx dot de 2005-06-21 12:48 ` pinskia at gcc dot gnu dot org 2005-06-23 7:08 ` Ralf_Recker at gmx dot de 2005-06-23 8:40 ` Ralf_Recker at gmx dot de 2005-07-03 11:52 ` pinskia at gcc dot gnu dot org 2005-07-05 7:25 ` Ralf_Recker at gmx dot de 2005-07-05 12:56 ` pinskia at gcc dot gnu dot org 2005-07-12 1:46 ` pinskia at gcc dot gnu dot org 2005-07-14 7:32 ` Ralf_Recker at gmx dot de
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=20050621071353.22135.Ralf_Recker@gmx.de \ --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).