From: Marc Glisse <marc.glisse@inria.fr>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix PR77826
Date: Sat, 15 Oct 2016 21:50:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1610152333350.1941@laptop-mg.saclay.inria.fr> (raw)
In-Reply-To: <alpine.LSU.2.11.1610131023091.26629@t29.fhfr.qr>
On Thu, 13 Oct 2016, Richard Biener wrote:
> The patch introduces '@@' captures which do two things - first they
> change the comparison used for matching back to operand_equal_p
> only (thus perform "value-matching"), second the @@ capture denotes
> the specific operand that should be refered to in the result
> section (ifs and result expressions).
>
> When we face (plus @0 @1) (convert? @@0) for example this is lowered
> to (plus @__2 @1) (convert? @__2@0) marking the @__2 match for
> value handling.
Funny, I had the opposite convention in mind ;-)
On a completely artificial example:
(minus (plus (plus @0 @@0) @@0) @0)
would correspond to:
(minus (plus (plus @1 @2) @3) @4)
where either @1 or @4 is captured as @0, say @1 for example, @4 is
compared strictly to @1, while @2 and @3 are value-compared to @1 (lax).
This way, when we talk about @0 later in the transformation, we are indeed
talking about the thing that was called @0 in the input pattern, while @@0
is not-quite-@0.
But your version should be fine.
> I modified the patterns you identified and the ones I did and
> removed the operand_equal_p uses where possible.
Thanks. (some can be further generalized, as you explained in an earlier
message, but we can do that later as the need arises)
--
Marc Glisse
next prev parent reply other threads:[~2016-10-15 21:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 10:34 Richard Biener
2016-10-05 11:38 ` Richard Biener
2016-10-06 18:44 ` Marc Glisse
2016-10-07 7:36 ` Richard Biener
2016-10-10 8:47 ` Marc Glisse
2016-10-11 9:09 ` Richard Biener
2016-10-11 20:35 ` Marc Glisse
2016-10-12 11:34 ` Richard Biener
2016-10-12 12:49 ` Marc Glisse
2016-10-12 13:25 ` Richard Biener
2016-10-13 8:29 ` Richard Biener
2016-10-15 21:50 ` Marc Glisse [this message]
2016-10-17 7:59 ` 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.20.1610152333350.1941@laptop-mg.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).