public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/55330] New: [4.8 Regression] ICE: Maximum number of LRA constraint passes is achieved (15) on gfortran.dg/actual_array_constructor_1.f90
Date: Wed, 14 Nov 2012 20:59:00 -0000	[thread overview]
Message-ID: <bug-55330-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55330
           Summary: [4.8 Regression] ICE: Maximum number of LRA constraint
                    passes is achieved (15) on
                    gfortran.dg/actual_array_constructor_1.f90
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: rtl-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: zsojka@seznam.cz


Created attachment 28690
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28690
gfortran.dg/actual_array_constructor_1.f90

Compiler output:
$ gcc -O -fPIC -fno-dse -fno-guess-branch-probability
actual_array_constructor_1.f90
actual_array_constructor_1.f90: In function 'p':
actual_array_constructor_1.f90:20:0: internal compiler error: Maximum number of
LRA constraint passes is achieved (15)

   end subroutine
 ^
0x95f97e lra_constraints(bool)
        /mnt/svn/gcc-trunk/gcc/lra-constraints.c:3284
0x94ec3c lra(_IO_FILE*)
        /mnt/svn/gcc-trunk/gcc/lra.c:2274
0x906456 do_reload
        /mnt/svn/gcc-trunk/gcc/ira.c:4624
0x906456 rest_of_handle_reload
        /mnt/svn/gcc-trunk/gcc/ira.c:4737
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.


Another set of compiler flags with the same result:
$ gcc -O -fPIC -fstack-protector -fno-guess-branch-probability
actual_array_constructor_1.f90
actual_array_constructor_1.f90: In function 'p':
actual_array_constructor_1.f90:20:0: internal compiler error: Maximum number of
LRA constraint passes is achieved (15)

   end subroutine
 ^
0x95f97e lra_constraints(bool)
        /mnt/svn/gcc-trunk/gcc/lra-constraints.c:3284
0x94ec3c lra(_IO_FILE*)
        /mnt/svn/gcc-trunk/gcc/lra.c:2274
0x906456 do_reload
        /mnt/svn/gcc-trunk/gcc/ira.c:4624
0x906456 rest_of_handle_reload
        /mnt/svn/gcc-trunk/gcc/ira.c:4737
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.

Tested revisions:
r193495 - crash


             reply	other threads:[~2012-11-14 20:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14 20:59 zsojka at seznam dot cz [this message]
2012-11-14 21:43 ` [Bug rtl-optimization/55330] " dominiq at lps dot ens.fr
2012-11-15 10:47 ` jakub at gcc dot gnu.org
2012-11-16  9:14 ` dcb314 at hotmail dot com
2012-11-16 16:32 ` vmakarov at gcc dot gnu.org
2012-11-16 16:39 ` vmakarov at redhat dot com
2012-12-07 10:08 ` rguenth 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-55330-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).