public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Vineet Gupta <vineetg@rivosinc.com>
To: Jeff Law <jeffreyalaw@gmail.com>,
	HAO CHEN GUI <guihaoc@linux.ibm.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
	David <dje.gcc@gmail.com>, "Kewen.Lin" <linkw@linux.ibm.com>,
	Peter Bergner <bergner@linux.ibm.com>,
	Mikael Morin <morin-mikael@orange.fr>,
	"MacLeod, Andrew" <amacleod@redhat.com>,
	Aldy Hernandez <aldyh@redhat.com>,
	Jakub Jelinek <jakub@redhat.com>,
	Richard Sandiford <richard.sandiford@arm.com>
Subject: Re: Ping^4 [PATCH-2v4] Value Range: Add range op for builtin isfinite
Date: Tue, 13 Aug 2024 10:24:01 -0700	[thread overview]
Message-ID: <9951dca1-7518-4ca1-95e0-d576db0a54e0@rivosinc.com> (raw)
In-Reply-To: <4c222b38-dcf8-42b3-8a0b-3f8b04350863@gmail.com>

Hi Hao Gui,

Can you commit this soon - some of the arch patches might be waiting on this.

Thx,
-Vineet

On 8/5/24 07:59, Jeff Law wrote:
> On 7/21/24 8:10 PM, HAO CHEN GUI wrote:
>> Hi,
>>    Gently ping it.
>> https://gcc.gnu.org/pipermail/gcc-patches/2024-May/653094.html
> OK.  Sorry for the delays.

  reply	other threads:[~2024-08-13 17:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30  2:46 HAO CHEN GUI
2024-06-20  6:57 ` HAO CHEN GUI
2024-06-24  1:41   ` Ping^2 " HAO CHEN GUI
2024-07-01  1:11     ` Ping^3 " HAO CHEN GUI
2024-07-22  2:10       ` Ping^4 " HAO CHEN GUI
2024-08-05 14:59         ` Jeff Law
2024-08-13 17:24           ` Vineet Gupta [this message]
2024-08-14  7:25             ` HAO CHEN GUI

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=9951dca1-7518-4ca1-95e0-d576db0a54e0@rivosinc.com \
    --to=vineetg@rivosinc.com \
    --cc=aldyh@redhat.com \
    --cc=amacleod@redhat.com \
    --cc=bergner@linux.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=guihaoc@linux.ibm.com \
    --cc=jakub@redhat.com \
    --cc=jeffreyalaw@gmail.com \
    --cc=linkw@linux.ibm.com \
    --cc=morin-mikael@orange.fr \
    --cc=richard.sandiford@arm.com \
    --cc=segher@kernel.crashing.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).