public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/94270] [8/9 Regression] Bogus unused dummy argument warning/error
Date: Tue, 14 Apr 2020 14:16:44 +0000 [thread overview]
Message-ID: <bug-94270-4-lmyYL0hSU7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94270-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94270
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Thomas Kथà¤nig
<tkoenig@gcc.gnu.org>:
https://gcc.gnu.org/g:7c94472580af3e2328bebb1493e7693c2b9cadc2
commit r9-8497-g7c94472580af3e2328bebb1493e7693c2b9cadc2
Author: Thomas König <tkoenig@gcc.gnu.org>
Date: Tue Apr 14 16:15:49 2020 +0200
Backport from trunk of the fix for PR 94270.
2020-04-14 Thomas Koenig <tkoenig@gcc.gnu.org>
Backport from trunk
PR fortran/94270
* gfortran.dg/warn_unused_dummy_argument_6.f90: New test.
2020-04-14 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/94270
* gfortran.dg/warn_unused_dummy_argument_6.f90: New test.
next prev parent reply other threads:[~2020-04-14 14:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 10:09 [Bug fortran/94270] New: " jellby at yahoo dot com
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 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-14 14:25 ` [Bug fortran/94270] [8/9 " 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-lmyYL0hSU7@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).