public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/53111] [4.7/4.8 Regression] Derived types cannot be included again with -std=f95
Date: Wed, 25 Apr 2012 11:42:00 -0000	[thread overview]
Message-ID: <bug-53111-4-zMLRZ1oYva@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53111-4@http.gcc.gnu.org/bugzilla/>

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

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-04-25
                 CC|                            |janus at gcc dot gnu.org
            Summary|Derived types cannot be     |[4.7/4.8 Regression]
                   |included again when using   |Derived types cannot be
                   |standard Fortran 95         |included again with
                   |                            |-std=f95
     Ever Confirmed|0                           |1

--- Comment #1 from janus at gcc dot gnu.org 2012-04-25 11:41:43 UTC ---
Confirmed. This is a regression in gfortran 4.7 (and trunk, 4.6 works).
Slightly reduced test case:

module a
  type :: my
    real :: x
  end type
end module

module b
  use a
end module

program test
  use a
  use b
end program


  reply	other threads:[~2012-04-25 11:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-25 10:21 [Bug fortran/53111] New: Derived types cannot be included again when using standard Fortran 95 middag at users dot sourceforge.net
2012-04-25 11:42 ` janus at gcc dot gnu.org [this message]
2012-04-25 13:01 ` [Bug fortran/53111] [4.7/4.8 Regression] Derived types cannot be USE-associated again with -std=f95 burnus at gcc dot gnu.org
2012-04-26 14:24 ` rguenth at gcc dot gnu.org
2012-05-02  6:08 ` burnus at gcc dot gnu.org
2012-05-04 18:54 ` burnus at gcc dot gnu.org
2012-05-05 10:00 ` burnus at gcc dot gnu.org
2012-05-05 10:07 ` burnus 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-53111-4-zMLRZ1oYva@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).