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] PR fortran/84519 - [F2018] STOP and ERROR STOP statements with QUIET specifier
Date: Thu, 24 Feb 2022 12:50:49 +0100 [thread overview]
Message-ID: <d3af8959-804f-bc16-ba45-f54ae7430b09@orange.fr> (raw)
In-Reply-To: <trinity-86837fc5-81ea-4245-9f63-d8c2eafbf232-1645654903030@3c-app-gmx-bap14>
Le 23/02/2022 à 23:21, Harald Anlauf via Fortran a écrit :
> Dear Fortranners,
>
> Fortran 2018 added a QUIET= specifier to STOP and ERROR STOP statements.
> Janne already implemented the library side code four (4!) years ago,
> but so far the frontend implementation was missing.
>
> Furthermore, F2018 allows for non-default-integer stopcode expressions
> (finally!).
>
> The attached patch provides this implementation.
>
> That was not too much fun for the following reasons:
>
> - fixed format vs. free format
> - F95 and F2003 apparently did not require a blank between STOP and
> stopcode, while F2008+ do require it.
>
> This should explain for the three testcases.
>
> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>
> One step closer to F2018!
>
Please move the error from trans-stmt.cc to resolve.cc.
Otherwise looks good, and you have a green light by Jerry, but I would
rather defer this to gcc-13.
Mikael
next prev parent reply other threads:[~2022-02-24 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 22:21 Harald Anlauf
2022-02-24 3:07 ` Jerry D
2022-02-24 11:50 ` Mikael Morin [this message]
2022-02-24 20:06 ` Harald Anlauf
2022-02-24 20:06 ` 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=d3af8959-804f-bc16-ba45-f54ae7430b09@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).