From: Jerry D <jvdelisle2@gmail.com>
To: Harald Anlauf <anlauf@gmx.de>, fortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: *PING* [PATCH] Fortran: prevent redundant integer division truncation warnings [PR108592]
Date: Sun, 5 Feb 2023 13:46:28 -0800 [thread overview]
Message-ID: <a06a8d3f-337b-d541-fe99-72044a7457f4@gmail.com> (raw)
In-Reply-To: <068251af-8b30-71be-d9be-13fa05c95447@gmx.de>
On 2/5/23 11:33 AM, Harald Anlauf via Fortran wrote:
> Early gentle ping.
>
> Am 30.01.23 um 22:55 schrieb Harald Anlauf via Gcc-patches:
>> Dear Fortranners,
>>
>> the subject says it all: in some cases we emit redundant integer division
>> truncation warnings (2 or 4), where just one would have been sufficient.
>> This is solved by using gfc_warning instead of gfc_warning_now.
>>
>> The testcase uses a suggestion by Andrew to verify that we get the
>> desired warning exactly once.
>>
>> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>>
>> Thanks,
>> Harald
>>
>
The patch is gentle enough to be OK to commit.
Thanks,
Jerry
prev parent reply other threads:[~2023-02-05 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 21:55 Harald Anlauf
2023-02-05 19:33 ` *PING* " Harald Anlauf
2023-02-05 21:46 ` Jerry D [this message]
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=a06a8d3f-337b-d541-fe99-72044a7457f4@gmail.com \
--to=jvdelisle2@gmail.com \
--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).