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/95829] Bogus error with additional blanks in type(*)
Date: Wed, 01 Jul 2020 10:23:27 +0000 [thread overview]
Message-ID: <bug-95829-4-9HniZHxdwa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95829-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95829
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Mark Eggleston
<markeggleston@gcc.gnu.org>:
https://gcc.gnu.org/g:e025298cfcb1aae9d3ff674cdc1c4fb271cb2bdd
commit r10-8405-ge025298cfcb1aae9d3ff674cdc1c4fb271cb2bdd
Author: Mark Eggleston <markeggleston@gcc.gnu.org>
Date: Tue Jun 23 11:01:28 2020 +0100
Fortran : Bogus error with additional blanks in type(*) PR95829
Checking for "* ) " instead of "*)" clears the bogus error.
2020-07-01 Steven G. Kargl <kargl@gcc.gnu.org>
gcc/fortran/
PR fortran/95829
* decl.c (gfc_match_decl_type_spec): Compare with "* ) " instead
of "*)".
2020-07-01 Mark Eggleston <markeggleston@gcc.gnu.org>
gcc/testsuite/
PR fortran/95829
* gfortran.dg/pr95829.f90: New test.
(cherry picked from commit 624e60f080989fa57756575a0bb47a97748b52b8)
next prev parent reply other threads:[~2020-07-01 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 20:23 [Bug fortran/95829] New: " gscfq@t-online.de
2020-06-22 23:31 ` [Bug fortran/95829] " kargl at gcc dot gnu.org
2020-07-01 9:14 ` cvs-commit at gcc dot gnu.org
2020-07-01 10:23 ` cvs-commit at gcc dot gnu.org [this message]
2020-07-01 12:10 ` cvs-commit at gcc dot gnu.org
2020-07-01 13:08 ` cvs-commit at gcc dot gnu.org
2020-07-01 13:09 ` markeggleston 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-95829-4-9HniZHxdwa@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).