public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "spop at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/45199]  New: ICE in loop distribution
Date: Thu, 05 Aug 2010 20:20:00 -0000	[thread overview]
Message-ID: <bug-45199-7780@http.gcc.gnu.org/bugzilla/> (raw)

When compiled with -O3 the following code ICEs on amd64-linux.

      parameter(numlev=3,numoblev=1000)
      integer i_otyp(numoblev,numlev), i_styp(numoblev,numlev)
      logical l_numob(numoblev,numlev)
      do ixe=1,numoblev
         do iye=1,numlev
            i_otyp(ixe,iye)=0
            i_styp(ixe,iye)=0
            l_numob(ixe,iye)=.false.
         enddo
      enddo
      do i=1,m
         do j=1,n
            if (l_numob(i,j)) then
               write(20,'(7I4,F12.2,4F16.10)') i_otyp(i,j),i_styp(i,j)
            endif 
         enddo
      enddo
      end


-- 
           Summary: ICE in loop distribution
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: spop at gcc dot gnu dot org
        ReportedBy: spop at gcc dot gnu dot org


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


             reply	other threads:[~2010-08-05 20:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-05 20:20 spop at gcc dot gnu dot org [this message]
2010-08-05 21:11 ` [Bug tree-optimization/45199] " dominiq at lps dot ens dot fr
2010-08-05 21:40 ` dominiq at lps dot ens dot fr
2010-08-06 11:11 ` [Bug tree-optimization/45199] [4.6 Regression] ICE in loop distribution at -O3 rguenth at gcc dot gnu dot org
2010-09-02 11:15 ` rguenth 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-45199-7780@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).