public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/45965] New: [4.6 Regression] ICE on powerpc-apple-darwin9: gfortran.dg/subref_array_pointer_4.f90
Date: Mon, 11 Oct 2010 13:05:00 -0000	[thread overview]
Message-ID: <bug-45965-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: [4.6 Regression] ICE on powerpc-apple-darwin9:
                    gfortran.dg/subref_array_pointer_4.f90
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: dominiq@lps.ens.fr
                CC: spop@gcc.gnu.org, irar@il.ibm.com
              Host: powerpc-apple-darwin9
            Target: powerpc-apple-darwin9
             Build: powerpc-apple-darwin9


On powerpc-apple-darwin9, between revisions 164750 and 164814 the following
failures

FAIL: gfortran.dg/subref_array_pointer_4.f90  -O3 -fomit-frame-pointer 
(internal compiler error)
FAIL: gfortran.dg/subref_array_pointer_4.f90  -O3 -fomit-frame-pointer  (test
for excess errors)
WARNING: gfortran.dg/subref_array_pointer_4.f90  -O3 -fomit-frame-pointer 
compilation failed to produce executable
FAIL: gfortran.dg/subref_array_pointer_4.f90  -O3 -fomit-frame-pointer
-funroll-loops  (internal compiler error)
FAIL: gfortran.dg/subref_array_pointer_4.f90  -O3 -fomit-frame-pointer
-funroll-loops  (test for excess errors)
WARNING: gfortran.dg/subref_array_pointer_4.f90  -O3 -fomit-frame-pointer
-funroll-loops  compilation failed to produce executable
FAIL: gfortran.dg/subref_array_pointer_4.f90  -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions  (internal compiler error)
FAIL: gfortran.dg/subref_array_pointer_4.f90  -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions  (test for excess errors)
WARNING: gfortran.dg/subref_array_pointer_4.f90  -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions  compilation failed to produce executable
FAIL: gfortran.dg/subref_array_pointer_4.f90  -O3 -g  (internal compiler error)
FAIL: gfortran.dg/subref_array_pointer_4.f90  -O3 -g  (test for excess errors)
WARNING: gfortran.dg/subref_array_pointer_4.f90  -O3 -g  compilation failed to
produce executable

appeared (see http://gcc.gnu.org/ml/gcc-testresults/2010-09/msg02570.html and
http://gcc.gnu.org/ml/gcc-testresults/2010-10/msg00006.html ). These ICEs
disappear with -m64 and the minimal options are '-O1 -ftree-vectorize':

[karma] f90/bug% gfc -O1 -ftree-vectorize
/opt/gcc/_gcc_clean/gcc/testsuite/gfortran.dg/subref_array_pointer_4.f90
/opt/gcc/_gcc_clean/gcc/testsuite/gfortran.dg/subref_array_pointer_4.f90: In
function 'main':
/opt/gcc/_gcc_clean/gcc/testsuite/gfortran.dg/subref_array_pointer_4.f90:21:0:
internal compiler error: Bus error

The ICE disappears when using gdb.

I have had a quick look to the commits in the range and most of the significant
ones are related to graphite (I am trying to reduce the range).


             reply	other threads:[~2010-10-11 13:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11 13:05 dominiq at lps dot ens.fr [this message]
2010-10-11 15:55 ` [Bug tree-optimization/45965] " dominiq at lps dot ens.fr
2010-10-11 16:40 ` dominiq at lps dot ens.fr
2010-11-03 15:39 ` rguenth at gcc dot gnu.org
2010-11-03 19:22 ` spop at gcc dot gnu.org
2010-11-03 19:49 ` dominiq at lps dot ens.fr
2010-11-15 11:45 ` rguenth at gcc dot gnu.org
2010-11-15 11:50 ` dominiq at lps dot ens.fr
2010-12-20 10:26 ` dominiq at lps dot ens.fr
2010-12-20 10:52 ` dominiq at lps dot ens.fr
2010-12-20 11:17 ` 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-45965-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: 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).