From: Hans-Peter Nilsson <hp@bitrange.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Ajit Agarwal <aagarwa1@linux.ibm.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
Peter Bergner <bergner@linux.ibm.com>,
Richard Biener <richard.guenther@gmail.com>
Subject: Re: [PATCH v4 4/4] ree: Improve ree pass for rs6000 target using defined ABI interfaces.
Date: Fri, 28 Apr 2023 19:49:52 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.20.16.2304281945220.60626@arjuna.pair.com> (raw)
In-Reply-To: <77213cc0-f666-8233-5af7-0aa199455b54@gmail.com>
On Fri, 28 Apr 2023, Jeff Law wrote:
> On 4/28/23 16:42, Hans-Peter Nilsson wrote:
> > On Sat, 22 Apr 2023, Ajit Agarwal via Gcc-patches wrote:
> > I don't see anything in those functions that checks if
> > ZERO_EXTEND is actually a feature of the ABI, e.g. as opposed to
> > no extension or SIGN_EXTEND. Do I miss something?
> I don't think you missed anything. That was one of the points I was making
> last week. Somewhere, somehow we need to describe what the ABI mandates and
> guarantees.
Right, I thought this was the new version.
> So while what Ajit has done is a step forward, at some point the actual
> details of the ABI need to be described in a way that can be checked and
> consumed by REE.
IIRC I also commented and suggested a few target macros that
*should* have helped to that effect. Ajit, I suggest you see my
previous reply in this or a related conversation.
brgds, H-P
next prev parent reply other threads:[~2023-04-28 23:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 9:06 Ajit Agarwal
2023-04-28 22:42 ` Hans-Peter Nilsson
2023-04-28 23:33 ` Jeff Law
2023-04-28 23:49 ` Hans-Peter Nilsson [this message]
2023-05-02 22:00 ` Peter Bergner
2023-05-16 12:35 ` Ajit Agarwal
2023-05-19 19:32 ` Jeff Law
2023-05-01 16:21 ` Segher Boessenkool
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=alpine.BSF.2.20.16.2304281945220.60626@arjuna.pair.com \
--to=hp@bitrange.com \
--cc=aagarwa1@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=richard.guenther@gmail.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).