public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Harald Anlauf <anlauf@gmx.de>
To: fortran@gcc.gnu.org
Cc: 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 21:06:52 +0100	[thread overview]
Message-ID: <d62010fe-56dd-adc1-b3ec-d1b5f9c84355@gmx.de> (raw)
In-Reply-To: <d3af8959-804f-bc16-ba45-f54ae7430b09@orange.fr>

Dear Jerry, Mikael,

thanks for the feedback!

Am 24.02.22 um 12:50 schrieb Mikael Morin:
> 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.

That is certainly cleaner.  I've done this and rerun the regtest.

As suggested by Jerry a simple run-time testcase with QUIET=.true. has
been added.  However, since I could not find a way to convince dejagnu
that there should be no output, I simply check that the right values
are passed to the runtime library.

If somebody knows how to solve this and feels strongly about this,
please proceed.

Pushed as https://gcc.gnu.org/g:916b809fbfdd2740006270baf549bf22fe9ec3c4

> Otherwise looks good, and you have a green light by Jerry, but I would 
> rather defer this to gcc-13.
> 
> Mikael
> 

Thanks,
Harald


WARNING: multiple messages have this Message-ID
From: Harald Anlauf <anlauf@gmx.de>
To: Mikael Morin <morin-mikael@orange.fr>,
	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 21:06:52 +0100	[thread overview]
Message-ID: <d62010fe-56dd-adc1-b3ec-d1b5f9c84355@gmx.de> (raw)
Message-ID: <20220224200652.-kOdEN5NjxJToH2ChgvUTM8uuc826rsYiwQ84eazTSA@z> (raw)
In-Reply-To: <d3af8959-804f-bc16-ba45-f54ae7430b09@orange.fr>

Dear Jerry, Mikael,

thanks for the feedback!

Am 24.02.22 um 12:50 schrieb Mikael Morin:
> 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.

That is certainly cleaner.  I've done this and rerun the regtest.

As suggested by Jerry a simple run-time testcase with QUIET=.true. has
been added.  However, since I could not find a way to convince dejagnu
that there should be no output, I simply check that the right values
are passed to the runtime library.

If somebody knows how to solve this and feels strongly about this,
please proceed.

Pushed as https://gcc.gnu.org/g:916b809fbfdd2740006270baf549bf22fe9ec3c4

> Otherwise looks good, and you have a green light by Jerry, but I would
> rather defer this to gcc-13.
>
> Mikael
>

Thanks,
Harald

  reply	other threads:[~2022-02-24 20:07 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
2022-02-24 20:06   ` Harald Anlauf [this message]
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=d62010fe-56dd-adc1-b3ec-d1b5f9c84355@gmx.de \
    --to=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).