From: Marc Glisse <marc.glisse@inria.fr>
To: Rasmus Villemoes <rv@rasmusvillemoes.dk>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: RFC: Two minor optimization patterns
Date: Wed, 14 Jan 2015 13:14:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.11.1501141340340.2186@laptop-mg.saclay.inria.fr> (raw)
In-Reply-To: <877fwquwug.fsf@rasmusvillemoes.dk>
On Tue, 13 Jan 2015, Rasmus Villemoes wrote:
> diff --git gcc/match.pd gcc/match.pd
> index 81c4ee6..04a0bc4 100644
> --- gcc/match.pd
> +++ gcc/match.pd
> @@ -262,6 +262,16 @@ along with GCC; see the file COPYING3. If not see
> (abs tree_expr_nonnegative_p@0)
> @0)
>
> +/* x + (x & 1) -> (x + 1) & ~1 */
> +(simplify
> + (plus @0 (bit_and @0 integer_onep@1))
> + (bit_and (plus @0 @1) (bit_not @1)))
> +
> +/* x | ~(x | y) -> x | ~y */
> +(simplify
> + (bit_ior @0 (bit_not (bit_ior @0 @1)))
> + (bit_ior @0 (bit_not @1)))
You may want to consider using has_single_use (see other patterns).
--
Marc Glisse
next prev parent reply other threads:[~2015-01-14 12:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 22:47 Rasmus Villemoes
2015-01-13 22:56 ` Andrew Pinski
2015-01-14 9:52 ` Richard Biener
2015-01-14 12:45 ` Rasmus Villemoes
2015-01-14 14:01 ` Richard Biener
2015-01-21 10:50 ` [PATCH 0/4] A few " Rasmus Villemoes
2015-01-21 10:50 ` [PATCH 1/4] match.pd: Add x + (x & 1) -> (x + 1) & ~1 pattern Rasmus Villemoes
2015-04-30 9:34 ` Richard Biener
2015-05-01 18:26 ` Jeff Law
2015-01-21 10:55 ` [PATCH 2/4] match.pd: Add x & ~(x & y) -> x & ~y pattern Rasmus Villemoes
2015-05-01 18:29 ` Jeff Law
2015-01-21 10:58 ` [PATCH 3/4] match.pd: Add x | ~(x | y) -> x | " Rasmus Villemoes
2015-01-21 11:32 ` Marek Polacek
2015-01-21 11:17 ` [PATCH 4/4] match.pd: Add x + ((-x) & m) -> (x + m) & ~m pattern Rasmus Villemoes
2015-04-30 9:42 ` Richard Biener
2015-04-30 11:56 ` Marc Glisse
2015-04-30 12:25 ` Richard Biener
2015-01-14 13:14 ` Marc Glisse [this message]
2015-01-14 13:58 ` RFC: Two minor optimization patterns Richard Biener
2015-01-14 14:31 ` Marc Glisse
2015-01-14 14:49 ` Richard Biener
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.DEB.2.11.1501141340340.2186@laptop-mg.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=rv@rasmusvillemoes.dk \
/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).