public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "toon at moene dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/50178] New: [4.6 regression] ICE with gfortran -O3, not with gfortran -02
Date: Wed, 24 Aug 2011 17:22:00 -0000	[thread overview]
Message-ID: <bug-50178-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 50178
           Summary: [4.6 regression] ICE with gfortran -O3, not with
                    gfortran -02
    Classification: Unclassified
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: toon@moene.org


Created attachment 25089
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25089
Source code of the failing compilation.

Compiling the attached source code with gfortran 4.6.1 using optimization -O3
leads to the following Internal Compiler Error:

$ gfortran -O3 -c suedyn.f90 
suedyn.f90: In function ‘suedyn’:
suedyn.f90:10:0: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.

Compiling with -O2 instead succeeds (hence my suspicion that it is a middle-end
failure).


             reply	other threads:[~2011-08-24 17:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 17:22 toon at moene dot org [this message]
2011-08-24 17:23 ` [Bug middle-end/50178] " toon at moene dot org
2011-08-24 18:00 ` burnus at gcc dot gnu.org
2011-08-24 18:53 ` dominiq at lps dot ens.fr
2011-08-24 19:24 ` jakub at gcc dot gnu.org
2011-08-25  8:30 ` [Bug tree-optimization/50178] " rguenth at gcc dot gnu.org
2011-09-01  7:02 ` irar at il dot ibm.com
2011-09-01  8:31 ` irar at gcc dot gnu.org
2011-09-01  8:47 ` irar at gcc dot gnu.org
2011-09-01  9:05 ` irar at il dot ibm.com

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-50178-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).