public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kazu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/38997]  New: -ftree-loop-distribution ICEs
Date: Wed, 28 Jan 2009 07:06:00 -0000	[thread overview]
Message-ID: <bug-38997-5009@http.gcc.gnu.org/bugzilla/> (raw)

Consider:

char a[8][8];
char b[8];

void
foo (int i)
{
  int j;
  for (j = 0; j < 8; j++)
    {
      a[i][j] = 0;
      b[j] = j;
    }
}

I get:

$ ./cc1 -quiet -O2 -ftree-loop-distribution min.c
min.c: In function 'foo':
min.c:5: internal compiler error: in build2_stat, at tree.c:3298
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.


-- 
           Summary: -ftree-loop-distribution ICEs
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: kazu at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38997


             reply	other threads:[~2009-01-28  7:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28  7:06 kazu at gcc dot gnu dot org [this message]
2009-01-28  8:40 ` [Bug tree-optimization/38997] " kazu at gcc dot gnu dot org
2009-01-28 18:17 ` kazu at gcc dot gnu dot org
2009-01-28 18:17 ` kazu at gcc dot gnu dot org
2009-01-28 18:19 ` kazu 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=bug-38997-5009@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: link
Be 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).