public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/50121] New: Labels in a TYPE statement should be put in the derived type's scope
Date: Thu, 18 Aug 2011 23:15:00 -0000	[thread overview]
Message-ID: <bug-50121-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 50121
           Summary: Labels in a TYPE statement should be put in the
                    derived type's scope
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: mikael@gcc.gnu.org


Follow-up to PR 50071, reported by Tobias at:
http://gcc.gnu.org/ml/fortran/2011-08/msg00109.html

gfortran doesn't put labels declared in a derived type in their own scope. 
PR 50071 fixed all cases but the one where the label is in the first line of
the derived type definition:

1 type t
    integer :: i
  end type t

  goto 1
1 print *, 'Hello'
end


This case is more difficult, as at the time we insert the label, we haven't
parsed the TYPE statement yet, thus the derived type scope is not available
yet.


             reply	other threads:[~2011-08-18 23:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18 23:15 mikael at gcc dot gnu.org [this message]
2011-08-18 23:18 ` [Bug fortran/50121] " mikael at gcc dot gnu.org
2011-08-19  8:05 ` 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-50121-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).