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/34871] New: Flavor VARIABLE vs. FUNCTION: Accepts invalid Date: Sat, 19 Jan 2008 12:09:00 -0000 [thread overview] Message-ID: <bug-34871-13404@http.gcc.gnu.org/bugzilla/> (raw) MODULE TESTS dimension :: k(4) CONTAINS function k() k = 35 end function k END MODULE is invalid (variable "k" vs. function "k"), but not detected. Needs to be fixed in decl.c's get_proc_name; I have a patch, but it causes regressions -- Summary: Flavor VARIABLE vs. FUNCTION: Accepts invalid Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: rejects-valid Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34871
next reply other threads:[~2008-01-19 12:00 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-19 12:09 burnus at gcc dot gnu dot org [this message] 2008-01-21 23:11 ` [Bug fortran/34871] " dfranke at gcc dot gnu dot org 2008-01-21 23:26 ` dfranke at gcc dot gnu dot org 2008-11-18 19:37 ` pault 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=bug-34871-13404@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: 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).