public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Harald Anlauf <anlauf@gmx.de>
To: FX Coudert <fxcoudert@gmail.com>, fortran@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fortran: add IEEE_QUIET_* and IEEE_SIGNALING_* comparisons
Date: Thu, 8 Jun 2023 14:26:42 +0200	[thread overview]
Message-ID: <8d3773e6-58a4-ec38-cfd1-f4fb7666e7e3@gmx.de> (raw)
In-Reply-To: <C1565A65-4FA2-4C16-8AF9-E8A2776D5067@gmail.com>

Hi FX,

Am 06.06.23 um 21:29 schrieb FX Coudert via Gcc-patches:
> Hi,
>
> This is a repost of the patch at https://gcc.gnu.org/pipermail/gcc-patches/2022-September/600887.html
> which never really got green light, but I stopped pushing because stage 1 was closing and I was out of time.

I just looked at that thread.  I guess if you answer Mikael's
questions at

   https://gcc.gnu.org/pipermail/gcc-patches/2022-September/601744.html

the patch will be fine.

> It depends on a middle-end patch adding a type-generic __builtin_iseqsig(), which I posted for review at: https://gcc.gnu.org/pipermail/gcc-patches/2023-June/620801.html
>
> Bootstrapped and regtested on x86_64-pc-linux-gnu, OK to commit (once the middle-end patch is accepted)?
>
> FX
>

Thanks,
Harald


WARNING: multiple messages have this Message-ID

From: Harald Anlauf <anlauf@gmx.de>
To: gcc-patches@gcc.gnu.org
Cc: fortran@gcc.gnu.org
Subject: Re: [PATCH] Fortran: add IEEE_QUIET_* and IEEE_SIGNALING_* comparisons
Date: Thu, 8 Jun 2023 14:26:42 +0200	[thread overview]
Message-ID: <8d3773e6-58a4-ec38-cfd1-f4fb7666e7e3@gmx.de> (raw)
Message-ID: <20230608122642.xXennAi2ygGXE6b8dqRwGdikC_ZA_sMAN9WECGDWHXE@z> (raw)
In-Reply-To: <C1565A65-4FA2-4C16-8AF9-E8A2776D5067@gmail.com>

Hi FX,

Am 06.06.23 um 21:29 schrieb FX Coudert via Gcc-patches:
> Hi,
> 
> This is a repost of the patch at https://gcc.gnu.org/pipermail/gcc-patches/2022-September/600887.html
> which never really got green light, but I stopped pushing because stage 1 was closing and I was out of time.

I just looked at that thread.  I guess if you answer Mikael's
questions at

   https://gcc.gnu.org/pipermail/gcc-patches/2022-September/601744.html

the patch will be fine.

> It depends on a middle-end patch adding a type-generic __builtin_iseqsig(), which I posted for review at: https://gcc.gnu.org/pipermail/gcc-patches/2023-June/620801.html
> 
> Bootstrapped and regtested on x86_64-pc-linux-gnu, OK to commit (once the middle-end patch is accepted)?
> 
> FX
> 

Thanks,
Harald



  reply	other threads:[~2023-06-08 12:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 19:29 FX Coudert
2023-06-08 12:26 ` Harald Anlauf [this message]
2023-06-08 12:26   ` Harald Anlauf
2023-06-10 15:21   ` FX Coudert
  -- strict thread matches above, loose matches on Subject: below --
2022-09-02 11:37 FX
2022-09-02 15:37 ` Bernhard Reutner-Fischer
2022-09-02 15:54   ` FX
2022-09-02 16:03     ` Bernhard Reutner-Fischer
2022-09-02 16:17       ` FX
2022-09-17 11:58 ` Mikael Morin

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=8d3773e6-58a4-ec38-cfd1-f4fb7666e7e3@gmx.de \
    --to=anlauf@gmx.de \
    --cc=fortran@gcc.gnu.org \
    --cc=fxcoudert@gmail.com \
    --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).