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/48706] Type extension inside subroutine
Date: Tue, 04 Oct 2011 20:44:00 -0000	[thread overview]
Message-ID: <bug-48706-4-BOFUnPJRHy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48706-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from janus at gcc dot gnu.org 2011-10-04 20:44:14 UTC ---
Author: janus
Date: Tue Oct  4 20:44:10 2011
New Revision: 179524

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=179524
Log:
2011-10-04  Janus Weil  <janus@gcc.gnu.org>

    PR fortran/48706
    * module.c (write_dt_extensions): Do not write extended types which
    are local to a subroutine.


2011-10-04  Janus Weil  <janus@gcc.gnu.org>

    PR fortran/48706
    * gfortran.dg/extends_12.f03: New.

Added:
    branches/gcc-4_6-branch/gcc/testsuite/gfortran.dg/extends_12.f03
Modified:
    branches/gcc-4_6-branch/gcc/fortran/ChangeLog
    branches/gcc-4_6-branch/gcc/fortran/module.c
    branches/gcc-4_6-branch/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2011-10-04 20:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20 19:40 [Bug fortran/48706] New: [OOP] ICE (segfault) with TBP burnus at gcc dot gnu.org
2011-05-18 22:01 ` [Bug fortran/48706] Type extension inside subroutine janus at gcc dot gnu.org
2011-05-18 22:07 ` janus at gcc dot gnu.org
2011-05-18 23:07 ` janus at gcc dot gnu.org
2011-05-20  9:23 ` janus at gcc dot gnu.org
2011-05-20  9:53 ` burnus at gcc dot gnu.org
2011-05-20 18:36 ` janus at gcc dot gnu.org
2011-05-20 18:46 ` janus at gcc dot gnu.org
2011-10-04 11:07 ` jakub at gcc dot gnu.org
2011-10-04 20:44 ` janus at gcc dot gnu.org [this message]
2011-10-04 20:46 ` janus 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-48706-4-BOFUnPJRHy@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).