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: Mon, 26 Feb 2007 16:48:00 -0000 [thread overview] Message-ID: <20070226164757.14145.qmail@sourceware.org> (raw) In-Reply-To: <bug-30973-13648@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from burnus at gcc dot gnu dot org 2007-02-26 16:47 ------- I checked: " USE foo, ONLY:" is syntactically correct. The problem is that "only_flag = 1;" and no symbol is in the only-list. I think one needs to modify module.c's "read_module", but I fail quickly to see were the symbol "foo" is not added/deleted from the symbol tree. All other compilers I tried (g95,ifort,nagf95,sunf95) gave an error. -- burnus at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Keywords| |accepts-invalid Last reconfirmed|0000-00-00 00:00:00 |2007-02-26 16:47:56 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30973
next prev parent reply other threads:[~2007-02-26 16:48 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 ` burnus at gcc dot gnu dot org [this message] 2007-02-26 16:55 ` [Bug fortran/30973] " 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 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=20070226164757.14145.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: linkBe 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).