From: Jeff Law <jeffreyalaw@gmail.com>
To: Richard Biener <rguenther@suse.de>,
Tobias Burnus <tobias@codesourcery.com>
Cc: richard.sandiford@arm.com,
Roger Sayle <roger@nextmovesoftware.com>,
gcc-patches@gcc.gnu.org, Jeff Law <law@redhat.com>
Subject: Re: PING**3 - [PATCH] middle-end: Support ABIs that pass FP values as wider integers.
Date: Wed, 2 Mar 2022 12:18:06 -0700 [thread overview]
Message-ID: <7f9a2be7-61a8-952c-4a73-d51a3562e93e@gmail.com> (raw)
In-Reply-To: <9023r58q-7n1-9pr0-769r-45oo426n3p9r@fhfr.qr>
On 2/28/2022 5:54 AM, Richard Biener via Gcc-patches wrote:
> On Mon, 28 Feb 2022, Tobias Burnus wrote:
>
>> Ping**3
>>
>> On 23.02.22 09:42, Tobias Burnus wrote:
>>> PING**2 for the ME review or at least comments to that patch,
>>> which fixes a build issue/ICE with nvptx
>>>
>>> Patch:
>>> https://gcc.gnu.org/pipermail/gcc-patches/2022-February/590139.html
>>> (for gcc/cfgexpand.cc + gcc/expr.cc)
>>>
>>> (There is some discussion by Tom and Roger about the BE in the patch
>>> thread, which only not relate to the ME patch. But there is no
>>> ME-patch comment so far.)
>> The related BE patch has been already committed, but to be effective, it
>> needs the ME patch.
> I'm not sure I'm qualified to review this - maybe Richard is.
I'd initially ignored the patch as it didn't seem a good fit for stage4,
subsequent messages changed my mind about it, but I never went back to
take a deeper look at Roger's patch.
jeff
next prev parent reply other threads:[~2022-03-02 19:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 20:12 Roger Sayle
2022-02-17 14:35 ` PING - " Tobias Burnus
2022-02-23 8:42 ` PING**2 " Tobias Burnus
2022-02-28 9:41 ` PING**3 " Tobias Burnus
2022-02-28 12:54 ` Richard Biener
2022-03-02 19:18 ` Jeff Law [this message]
2022-03-14 8:06 ` PING**4 " Tom de Vries
2022-03-14 8:39 ` Roger Sayle
2022-03-14 9:09 ` Richard Biener
2022-03-14 9:46 ` Roger Sayle
2022-03-14 10:14 ` Richard Biener
2022-03-14 11:49 ` Roger Sayle
2022-03-14 13:27 ` Richard Biener
2022-03-14 14:30 ` Roger Sayle
2022-03-14 14:40 ` Richard Biener
2022-03-14 15:31 ` Richard Sandiford
2022-03-14 14:59 ` Jeff Law
2022-03-14 15:08 ` Jeff Law
2022-02-22 15:42 ` Tom de Vries
2022-02-22 16:08 ` Roger Sayle
2022-02-22 22:09 ` Tom de Vries
2022-02-22 23:19 ` Roger Sayle
2022-03-14 15:30 ` Jeff Law
2022-03-14 17:24 ` Roger Sayle
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=7f9a2be7-61a8-952c-4a73-d51a3562e93e@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=rguenther@suse.de \
--cc=richard.sandiford@arm.com \
--cc=roger@nextmovesoftware.com \
--cc=tobias@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).