From: Jakub Jelinek <jakub@redhat.com>
To: Tamar Christina <Tamar.Christina@arm.com>
Cc: Xi Ruoyao <xry111@xry111.site>,
Segher Boessenkool <segher@kernel.crashing.org>,
David Edelsohn <dje.gcc@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Andrew Pinski <apinski@marvell.com>
Subject: Re: [PATCH] rs6000: Canonicalize copysign (x, -1) back to -abs (x) in the backend [PR112606]
Date: Mon, 27 Nov 2023 09:12:40 +0100 [thread overview]
Message-ID: <ZWRPeAxnJ/rJKIns@tucnak> (raw)
In-Reply-To: <VI1PR08MB53250CD94CF678D543201B95FFBDA@VI1PR08MB5325.eurprd08.prod.outlook.com>
On Mon, Nov 27, 2023 at 07:55:52AM +0000, Tamar Christina wrote:
> > For POPCOUNT I've introduced recently a way to provide custom expand_*
> > function and decide there what optimizations to use, even when it otherwise
> > is an integral unary optab ifn.
> >
>
> Oh that sounds interesting, do you have a commit for me to look at? I couldn't
> Spot anything obvious in the history.
https://gcc.gnu.org/r14-5613
Jakub
next prev parent reply other threads:[~2023-11-27 8:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 10:17 Jakub Jelinek
2023-11-25 10:42 ` Xi Ruoyao
2023-11-25 12:03 ` Tamar Christina
2023-11-25 12:09 ` Jakub Jelinek
2023-11-27 7:55 ` Tamar Christina
2023-11-27 8:12 ` Jakub Jelinek [this message]
2023-11-27 8:22 ` Tamar Christina
2023-12-04 8:35 ` Patch ping: " Jakub Jelinek
2023-12-04 9:21 ` Kewen.Lin
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=ZWRPeAxnJ/rJKIns@tucnak \
--to=jakub@redhat.com \
--cc=Tamar.Christina@arm.com \
--cc=apinski@marvell.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=xry111@xry111.site \
/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).