public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: FX <fxcoudert@gmail.com>
To: gcc-patches@gcc.gnu.org
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
	Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] Add __builtin_iseqsig()
Date: Fri, 9 Sep 2022 19:55:30 +0200	[thread overview]
Message-ID: <3FD18835-D09C-4073-B23F-DD1038D4D0AC@gmail.com> (raw)
In-Reply-To: <127A04DF-0BC1-40B4-956A-B22C39F97BF9@gmail.com>

ping


> Le 1 sept. 2022 à 23:02, FX <fxcoudert@gmail.com> a écrit :
> 
> Attached patch adds __builtin_iseqsig() to the middle-end and C family front-ends.
> Testing does not currently check whether the signaling part works, because with optimisation is actually does not (preexisting compiler bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106805)
> 
> Bootstrapped and regtested on x86_64-linux.
> OK to commit?
> 
> (I’m not very skilled for middle-end hacking, so I’m sure there will be modifications to make.)
> 
> FX
> <0001-Add-__builtin_iseqsig.patch>


  reply	other threads:[~2022-09-09 17:55 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 [this message]
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

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=3FD18835-D09C-4073-B23F-DD1038D4D0AC@gmail.com \
    --to=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).