From: Segher Boessenkool <segher@kernel.crashing.org>
To: Andrew Pinski <apinski@quicinc.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [RFC] New optab for `a&~b` (and future expand improvements)
Date: Wed, 15 May 2024 17:11:00 -0500 [thread overview]
Message-ID: <20240515221100.GI19790@gate.crashing.org> (raw)
In-Reply-To: <DM6PR02MB4058810C7AFCAED2E9D02F09B8EC2@DM6PR02MB4058.namprd02.prod.outlook.com>
Hi!
On Wed, May 15, 2024 at 02:39:12PM +0000, Andrew Pinski via Gcc wrote:
> * Add an optab for andnot (`a & ~b`)
RTL can just as easily recognise (AND (NOT (...))), if Gimple has
problems with that that is just a deficiency in Gimple. RTL only cares
about what an expression *means*, ans perhaps sometimes about canonical
forms. Never about silly naming things.
In RTL you never have redundant expressions things like "andnot". Such
things can at best get in the way always, and more likely be immediately
detrimental.
Segher
prev parent reply other threads:[~2024-05-15 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 14:39 Andrew Pinski
2024-05-15 17:03 ` Richard Biener
2024-05-15 22:11 ` Segher Boessenkool [this message]
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=20240515221100.GI19790@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=apinski@quicinc.com \
--cc=gcc@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).