public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: FX <fxcoudert@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
	gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] Add __builtin_iseqsig()
Date: Sun, 20 Nov 2022 18:28:15 +0100	[thread overview]
Message-ID: <3CD8D4D2-BD67-475F-BDA7-67DF8AD64516@gmail.com> (raw)
In-Reply-To: <4d6d63fd-1836-96f5-502b-c5257d2c0a14@gmail.com>

Hi,

> Joseph's reply earlier in this thread has indicated a desire to verify that verifies FE_INVALID is raised when appropriate and not raised when inappropriate when the arguments come from volatile variables rather than directly from constants.
> 
> The patch itself looks pretty reasonable.  So let's get the testing coverage Joseph wanted so we can move forward.

Sadly, while I had some time to deal with it when the patch was originally submitted, once the review came back my hands were full and right now I cannot find time. I hope someone can pick it up and finish, otherwise it will have to wait for the next version.

FX


      reply	other threads:[~2022-11-20 17:28 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
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 [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=3CD8D4D2-BD67-475F-BDA7-67DF8AD64516@gmail.com \
    --to=fxcoudert@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jeffreyalaw@gmail.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).