public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/24309] [4.1/4.2/4.3 Regression] ICE with -O3 -ftree-loop-linear Date: Wed, 10 Oct 2007 22:29:00 -0000 [thread overview] Message-ID: <20071010222856.9460.qmail@sourceware.org> (raw) In-Reply-To: <bug-24309-8902@http.gcc.gnu.org/bugzilla/> ------- Comment #18 from pthaugen at gcc dot gnu dot org 2007-10-10 22:28 ------- I'm appear to be seeing the same thing trying to build 445.gobmk from cpu2006 on PowerPC. run/build_base_gcc_64.0000> cat junk.c int board_size; void print_eye(int eye[400]) { int m, n; int mini, maxi; int minj, maxj; mini = 1; minj = 1; for (m = 0; m < board_size; m++) for (n = 0; n < board_size; n++) { if (eye[m + n] != 5) continue; if (m < mini) mini = m; if (n < minj) minj = n; } board_size = mini + minj; } run/build_base_gcc_64.0000> /home/pthaugen/install/gcc/trunk/bin/gcc -c -m64 -O2 -ftree-loop-linear junk.c junk.c: In function 'print_eye': junk.c:5: internal compiler error: in lambda_loopnest_to_gcc_loopnest, at lambda-code.c:1840 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. -- pthaugen at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pthaugen at gcc dot gnu dot | |org, bergner at gcc dot gnu | |dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24309
next prev parent reply other threads:[~2007-10-10 22:29 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-10-11 14:10 [Bug tree-optimization/24309] New: [4.1 " drab at kepler dot fjfi dot cvut dot cz 2005-10-11 14:11 ` [Bug tree-optimization/24309] " drab at kepler dot fjfi dot cvut dot cz 2005-10-11 14:12 ` pinskia at gcc dot gnu dot org 2005-10-11 14:48 ` pinskia at gcc dot gnu dot org 2005-10-11 14:56 ` drab at kepler dot fjfi dot cvut dot cz 2005-10-11 14:58 ` pinskia at gcc dot gnu dot org 2005-10-11 15:24 ` drab at kepler dot fjfi dot cvut dot cz 2005-10-11 15:27 ` dberlin at dberlin dot org 2005-10-31 6:12 ` mmitchel at gcc dot gnu dot org 2005-11-02 1:08 ` jean-marc dot valin at usherbrooke dot ca 2005-11-14 17:39 ` janis at gcc dot gnu dot org 2005-11-14 18:18 ` dberlin at gcc dot gnu dot org 2006-02-24 0:26 ` [Bug tree-optimization/24309] [4.1/4.2 " mmitchel at gcc dot gnu dot org 2006-05-18 5:51 ` pinskia at gcc dot gnu dot org 2006-05-25 2:35 ` mmitchel at gcc dot gnu dot org 2007-01-23 23:19 ` [Bug tree-optimization/24309] [4.1/4.2/4.3 " drab at kepler dot fjfi dot cvut dot cz 2007-02-14 9:07 ` mmitchel at gcc dot gnu dot org 2007-03-05 9:30 ` irar at il dot ibm dot com 2007-09-18 13:16 ` rguenth at gcc dot gnu dot org 2007-09-18 13:17 ` rguenth at gcc dot gnu dot org 2007-10-10 22:29 ` pthaugen at gcc dot gnu dot org [this message] 2007-10-11 5:58 ` ubizjak at gmail dot com 2007-10-11 6:08 ` pinskia at gcc dot gnu dot org 2007-10-11 6:13 ` pinskia at gcc dot gnu dot org 2007-10-11 19:35 ` spop at gcc dot gnu dot org 2007-10-19 19:03 ` spop at gcc dot gnu dot org 2007-10-19 19:03 ` spop at gcc dot gnu 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=20071010222856.9460.qmail@sourceware.org \ --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).