public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41951]  New: [OOP] ICE in gfc_match_varspec, at fortran/primary.c:1815
Date: Thu, 05 Nov 2009 17:00:00 -0000	[thread overview]
Message-ID: <bug-41951-13404@http.gcc.gnu.org/bugzilla/> (raw)

The following program is an extension to the one in PR 41539. It finally
requires to many features that ifort 11.1 does not like it - nor the dated NAG
f95 5.1 (current is 5.2). And while gfortran should have everything needed, it
still does not work.

I have no idea whether the code is correct - probably not - but an ICE is
definitely wrong. (For other issues see PR 41539.)

$ gfortran sort.f90
f951: internal compiler error: in gfc_match_varspec, at fortran/primary.c:1815
Please submit a full bug report


-- 
           Summary: [OOP] ICE in gfc_match_varspec, at
                    fortran/primary.c:1815
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: burnus at gcc dot gnu dot org
 BugsThisDependsOn: 41539


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


             reply	other threads:[~2009-11-05 17:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-05 17:00 burnus at gcc dot gnu dot org [this message]
2009-11-05 17:01 ` [Bug fortran/41951] " burnus at gcc dot gnu dot org
2009-11-06 10:36 ` janus at gcc dot gnu dot org
2009-12-05 22:15 ` tkoenig 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-41951-13404@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).