public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zeccav at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/50538] formal argument cannot be same as procedure name in ENTRY Date: Sat, 27 Feb 2021 09:00:41 +0000 [thread overview] Message-ID: <bug-50538-4-pnujQ3Nl9R@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50538-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50538 --- Comment #4 from Vittorio Zecca <zeccav at gmail dot com> --- Still present in current trunk. The compilers NAG nagfor and Intel ifort detect the issue. nagfor -S -w gfbug78.f NAG Fortran Compiler Release 7.0(Yurakucho) Build 7042 Error: gfbug78.f, line 4: Dummy argument SUB has the same name as the subprogram detected at (@SUB [NAG Fortran Compiler pass 1 error termination, 1 error] [vitti f95]$ifort -S -w gfbug78.f gfbug78.f(4): error #6406: Conflicting attributes or multiple declaration of name. [SUB] entry e(sub) --------------^ compilation aborted for gfbug78.f (code 1)
prev parent reply other threads:[~2021-02-27 9:00 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-27 14:19 [Bug fortran/50538] New: formal argument cannot be same as procedure name (r178939) zeccav at gmail dot com 2013-06-22 15:15 ` [Bug fortran/50538] " dominiq at lps dot ens.fr 2021-02-27 9:00 ` zeccav at gmail dot com [this message]
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-50538-4-pnujQ3Nl9R@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).