From: Richard Biener <rguenther@suse.de>
To: FX Coudert <fxcoudert@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH] Add __builtin_iseqsig()
Date: Thu, 20 Jul 2023 07:17:02 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2307200716560.12935@jbgna.fhfr.qr> (raw)
In-Reply-To: <4AEED749-8689-4272-898F-D8BB23073B60@gmail.com>
On Wed, 19 Jul 2023, FX Coudert wrote:
> 6 weeks later, I?d like to ask a global maintainer to review this.
> The idea was okay?ed previously by Joseph Myers, but he asked for testing of both the quiet and signalling NaN cases, which is now done.
OK.
Thanks,
Richard.
> FX
>
>
> > Le 6 juin 2023 ? 20:15, FX Coudert <fxcoudert@gmail.com> a ?crit :
> >
> > Hi,
> >
> > (It took me a while to get back to this.)
> >
> > This is a new and improved version of the patch at https://gcc.gnu.org/pipermail/gcc-patches/2022-October/602932.html
> > It addresses the comment from Joseph that FE_INVALID should really be tested in the case of both quiet and signaling NaNs, which is now done systematically.
> >
> > Bootstrapped and regtested on x86_64-pc-linux-gnu
> > OK to commit?
> >
> > FX
> >
>
--
Richard Biener <rguenther@suse.de>
SUSE Software Solutions Germany GmbH, Frankenstrasse 146, 90461 Nuernberg,
Germany; GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman;
HRB 36809 (AG Nuernberg)
next prev parent reply other threads:[~2023-07-20 7:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 21:02 FX
2022-09-09 17:55 ` FX
2022-09-21 9:40 ` FX
2022-10-06 8:40 ` FX
2022-10-06 21:46 ` Joseph Myers
2023-06-06 18:15 ` FX Coudert
2023-06-13 16:49 ` FX Coudert
2023-06-26 8:59 ` FX Coudert
2023-07-12 9:39 ` FX Coudert
2023-07-19 14:48 ` FX Coudert
2023-07-20 7:17 ` Richard Biener [this message]
2022-10-29 5:10 ` Jeff Law
2022-10-31 18:24 ` Joseph Myers
2022-10-31 19:15 ` FX
2022-10-31 22:35 ` Joseph Myers
2022-11-20 17:10 ` Jeff Law
2022-11-20 17:28 ` FX
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=nycvar.YFH.7.77.849.2307200716560.12935@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
/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).