public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jellby at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/94270] New: Bogus unused dummy argument warning/error
Date: Mon, 23 Mar 2020 10:09:10 +0000 [thread overview]
Message-ID: <bug-94270-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94270
Bug ID: 94270
Summary: Bogus unused dummy argument warning/error
Product: gcc
Version: 7.5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: jellby at yahoo dot com
Target Milestone: ---
Apparently, passing an external procedure as an argument inside an internal
procedure triggers it:
$ cat test.f90
subroutine foo()
external bar
call meh(bar)
call foo_internal()
contains
subroutine foo_internal()
call meh(bar)
end subroutine foo_internal
end subroutine foo
$ gfortran -c test.f90 -Wall
test.f90:7:17:
call meh(bar)
1
Warning: Unused dummy argument ‘_formal_0’ at (1) [-Wunused-dummy-argument]
$ gfortran --version
GNU Fortran (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
next reply other threads:[~2020-03-23 10:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 10:09 jellby at yahoo dot com [this message]
2020-04-13 17:22 ` [Bug fortran/94270] " tkoenig at gcc dot gnu.org
2020-04-13 17:31 ` [Bug fortran/94270] [8/9/10 Regression] " tkoenig at gcc dot gnu.org
2020-04-13 18:00 ` tkoenig at gcc dot gnu.org
2020-04-14 11:51 ` cvs-commit at gcc dot gnu.org
2020-04-14 14:16 ` [Bug fortran/94270] [8/9 " cvs-commit at gcc dot gnu.org
2020-04-14 14:25 ` jellby at yahoo dot com
2020-04-14 14:35 ` tkoenig at gcc dot gnu.org
2020-04-14 16:48 ` cvs-commit at gcc dot gnu.org
2020-04-14 16:49 ` tkoenig 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-94270-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).