From: Marc Glisse <marc.glisse@inria.fr>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Simple bitop reassoc in match.pd
Date: Thu, 12 May 2016 16:03:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1605121756570.1996@laptop-mg.saclay.inria.fr> (raw)
In-Reply-To: <CAFiYyc0G7uLRdYXaB6_bkPCzm=N0WbKF2od_AfwBMM8S6cC7iA@mail.gmail.com>
On Thu, 12 May 2016, Richard Biener wrote:
> Yeah - note that VRP already calls set_range_info before simplifying
> stmts. It's just that substitute_and_fold doesn't apply fold_stmt (and
> thus match.pd) to all stmts but it only applies the pass specific "fold"
> (vrp_fold_stmt) to all stmts.
Just to be sure: is the fact that VRP doesn't apply fold_stmt on purpose?
The restriction makes sense, it is just that it may yield a bit of
duplication. We already indirectly use get_range_info in match.pd and may
miss out on opportunities that only occur in branches during the VRP pass.
--
Marc Glisse
next prev parent reply other threads:[~2016-05-12 16:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 18:45 Canonicalize X u< X to UNORDERED_EXPR Marc Glisse
2016-05-02 8:37 ` Richard Biener
2016-05-02 9:19 ` Marc Glisse
2016-05-02 9:45 ` Richard Biener
2016-05-03 6:37 ` Marc Glisse
2016-05-03 11:03 ` Richard Biener
2016-05-03 13:27 ` Marc Glisse
2016-05-03 13:34 ` Richard Biener
2016-05-06 11:50 ` Simple bitop reassoc in match.pd (was: Canonicalize X u< X to UNORDERED_EXPR) Marc Glisse
2016-05-08 20:49 ` Marc Glisse
2016-05-09 10:04 ` Richard Biener
2016-05-10 6:12 ` Marc Glisse
2016-05-10 9:27 ` Richard Biener
2016-05-11 13:52 ` H.J. Lu
2016-05-11 16:17 ` Marc Glisse
2016-05-11 16:26 ` Simple bitop reassoc in match.pd Jeff Law
2016-05-11 17:56 ` Marc Glisse
2016-05-11 20:44 ` Marc Glisse
2016-05-12 8:41 ` Richard Biener
2016-05-12 16:03 ` Marc Glisse [this message]
2016-05-12 16:51 ` Richard Biener
2016-05-12 5:26 ` Marc Glisse
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.20.1605121756570.1996@laptop-mg.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.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).