From: Mikael Morin <morin-mikael@orange.fr>
To: Harald Anlauf <anlauf@gmx.de>, fortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fortran: force error on bad KIND specifier [PR88552]
Date: Thu, 1 Jun 2023 22:33:07 +0200 [thread overview]
Message-ID: <e451e64b-f7a2-4757-6b06-3bf3f3275f77@orange.fr> (raw)
In-Reply-To: <trinity-1c63e58d-07b4-4137-a7be-3648399ce8db-1685646310303@3c-app-gmx-bap24>
Hello,
Le 01/06/2023 à 21:05, Harald Anlauf via Fortran a écrit :
> Dear all,
>
> we sometimes silently accept wrong declarations with unbalanced
> parentheses, as the PR and testcases therein show.
>
> It appears that the fix is obvious: use the existing error paths in
> gfc_match_kind_spec and error return from gfc_match_decl_type_spec.
> I'm still posting it here in case I have missed something not so
> obvious.
>
> The patch regtests cleanly on x86_64-pc-linux-gnu. OK for mainline?
>
It looks good, but...
> Thanks,
> Harald
>
> From a30ff5af130c4d33c086fd136978d5f49cb8bde4 Mon Sep 17 00:00:00 2001
> From: Harald Anlauf <anlauf@gmx.de>
> Date: Thu, 1 Jun 2023 20:56:11 +0200
> Subject: [PATCH] Fortran: force error on bad KIND specifier [PR88552]
>
> gcc/fortran/ChangeLog:
>
> PR fortran/88552
> * decl.cc (gfc_match_kind_spec): Use error path on missing right
> parenthesis.
> (gfc_match_decl_type_spec): Use error return when an error occurred
> during matching a KIND specifier.
>
> gcc/testsuite/ChangeLog:
>
> PR fortran/88552
> * gfortran.dg/pr88552.f90: New test.
> ---
> gcc/fortran/decl.cc | 4 ++++
> gcc/testsuite/gfortran.dg/pr88552.f90 | 6 ++++++
> 2 files changed, 10 insertions(+)
> create mode 100644 gcc/testsuite/gfortran.dg/pr88552.f90
>
> diff --git a/gcc/fortran/decl.cc b/gcc/fortran/decl.cc
> index 1de2b231242..deb20647fb9 100644
> --- a/gcc/fortran/decl.cc
> +++ b/gcc/fortran/decl.cc
> @@ -3366,6 +3366,7 @@ close_brackets:
> else
> gfc_error ("Missing right parenthesis at %C");
> m = MATCH_ERROR;
> + goto no_match;
> }
> else
> /* All tests passed. */
> @@ -4716,6 +4717,9 @@ get_kind:
> return MATCH_ERROR;
> }
>
> + if (m == MATCH_ERROR)
> + return MATCH_ERROR;
> +
... can you move this up to the place where m is set?
OK with that change.
Thanks
next prev parent reply other threads:[~2023-06-01 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 19:05 Harald Anlauf
2023-06-01 20:33 ` Mikael Morin [this message]
2023-06-01 21:11 ` Harald Anlauf
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=e451e64b-f7a2-4757-6b06-3bf3f3275f77@orange.fr \
--to=morin-mikael@orange.fr \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).