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/30973] undetected name conflict: variables may be named like modules
Date: Thu, 08 Mar 2007 12:31:00 -0000	[thread overview]
Message-ID: <20070308123116.25893.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30973-13648@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from burnus at gcc dot gnu dot org  2007-03-08 12:31 -------
Subject: Bug 30973

Author: burnus
Date: Thu Mar  8 12:30:58 2007
New Revision: 122696

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=122696
Log:
2007-03-08  Tobias Burnus  <burnus@net-b.de>

        PR fortran/30973
        * module.c (read_module): Always import module name as symbol.
        (gfc_match_use): Disallow module name in the only clause of
        a use statement.

2007-03-08  Tobias Burnus  <burnus@net-b.de>

        PR fortran/30973
        * gfortran.dg/use_4.f90: New test.
        * gfortran.dg/used_dummy_types_7.f90: Correct ambiguous symbol.


Added:
    trunk/gcc/testsuite/gfortran.dg/use_4.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/module.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gfortran.dg/used_dummy_types_7.f90


-- 


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


  parent reply	other threads:[~2007-03-08 12:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-26 14:42 [Bug fortran/30973] New: " dfranke at gcc dot gnu dot org
2007-02-26 16:48 ` [Bug fortran/30973] " burnus at gcc dot gnu dot org
2007-02-26 16:55 ` dfranke at gcc dot gnu dot org
2007-02-26 21:36 ` burnus at gcc dot gnu dot org
2007-02-27 17:44 ` burnus at gcc dot gnu dot org
2007-02-27 17:46 ` patchapp at dberlin dot org
2007-03-08 12:31 ` burnus at gcc dot gnu dot org [this message]
2007-03-31 22:05 ` [Bug fortran/30973] [4.1, 4.2 only] " burnus 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=20070308123116.25893.qmail@sourceware.org \
    --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).