public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40743]  New: [4.5 Regression] ICE when compiling iso_varying_string.f95 at revision 149591
Date: Tue, 14 Jul 2009 08:54:00 -0000	[thread overview]
Message-ID: <bug-40743-12313@http.gcc.gnu.org/bugzilla/> (raw)

At revision 149591, compiling iso_varying_string.f95 gives the following error:

[ibook-dhum] f90/bug% gfc -c iso_varying_string.f95
iso_varying_string.f95:2548.29:

end module iso_varying_string
                             1
Internal Error at (1):
resolve_code(): Bad statement code

Probably due (or uncovered) by revision 149586.

Note that the same error occurs when compiling the codes in pr40440#0 and
pr40440#2.


-- 
           Summary: [4.5 Regression] ICE when compiling
                    iso_varying_string.f95 at revision 149591
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dominiq at lps dot ens dot fr


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


             reply	other threads:[~2009-07-14  8:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14  8:54 dominiq at lps dot ens dot fr [this message]
2009-07-14  9:46 ` [Bug fortran/40743] " burnus at gcc dot gnu dot org
2009-07-14  9:47 ` burnus at gcc dot gnu dot org
2009-07-14 10:54 ` dominiq at lps dot ens dot fr
2009-07-14 13:20 ` janus at gcc dot gnu dot org
2009-07-14 13:38 ` janus at gcc dot gnu dot org
2009-07-14 13:50 ` janus at gcc dot gnu dot org
2009-07-14 16:54 ` janus at gcc dot gnu dot org
2009-07-15  7:29 ` steven at gcc dot gnu dot org
2009-07-15  8:42 ` janus at gcc dot gnu dot org
2009-07-15  8:47 ` janus 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-40743-12313@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).