From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Harald Anlauf <anlauf@gmx.de>
Cc: fortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fortran: error recovery while simplifying expressions [PR103707,PR106987]
Date: Wed, 6 Mar 2024 10:51:21 +0000 [thread overview]
Message-ID: <CAGkQGiLZ9m1Jk=LYTX1QAG3GNm2XqvWn_bBzO_tG_dyPZ+m0Eg@mail.gmail.com> (raw)
In-Reply-To: <trinity-168a3a2a-979c-498c-acae-4e12dc114be7-1709673831988@3c-app-gmx-bs32>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
Hi Harald,
This all looks good to me. OK for mainline and, according to intestinal
fortitude on your part, earlier branches.
Thanks
Paul
On Tue, 5 Mar 2024 at 21:24, Harald Anlauf <anlauf@gmx.de> wrote:
> Dear all,
>
> error recovery on arithmetic errors during simplification has bugged
> me for a long time, especially since the occurence of ICEs depended
> on whether -frange-check is specified or not, whether array ctors
> were involved, etc.
>
> I've now come up with the attached patch that classifies the arithmetic
> result codes into "hard" and "soft" errors.
>
> A "soft" error means that it is an overflow or other exception (e.g. NaN)
> that is ignored with -fno-range-check. After the patch, a soft error
> will not stop simplification (a hard one will), and error status will be
> passed along.
>
> I took this opportunity to change the emitted error for division by zero
> for real and complex division dependent on whether the numerator is
> regular or not. This makes e.g. (0.)/0 a NaN and now says so, in
> accordance with some other brands.
>
> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>
> Other comments?
>
> Thanks,
> Harald
>
>
next prev parent reply other threads:[~2024-03-06 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 21:23 Harald Anlauf
2024-03-06 10:51 ` Paul Richard Thomas [this message]
2024-03-06 17:09 ` [PATCH] Fortran: error recovery while simplifying expressions [PR103707, PR106987] 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='CAGkQGiLZ9m1Jk=LYTX1QAG3GNm2XqvWn_bBzO_tG_dyPZ+m0Eg@mail.gmail.com' \
--to=paul.richard.thomas@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).