From: Richard Biener <richard.guenther@gmail.com>
To: Marc Glisse <marc.glisse@inria.fr>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: PR71206: inconsistent types after match.pd transformation
Date: Fri, 20 May 2016 09:31:00 -0000 [thread overview]
Message-ID: <CAFiYyc3woshBW-X=tg85QQ5GPtXMj_kkCvgtWqYOVbsUugYvsw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1605200909280.1967@laptop-mg.saclay.inria.fr>
On Fri, May 20, 2016 at 9:12 AM, Marc Glisse <marc.glisse@inria.fr> wrote:
> On Fri, 20 May 2016, Marc Glisse wrote:
>
>> Hello,
>>
>> this was bootstrapped and regtested on powerpc64le-unknown-linux-gnu.
>>
>> 2016-05-20 Marc Glisse <marc.glisse@inria.fr>
>
>
> PR tree-optimization/71079
> PR tree-optimization/71206
Ok.
Thanks,
Richard.
>
>> gcc/
>> * match.pd ((X ^ Y) ^ (X ^ Z)): Convert the arguments.
>>
>> gcc/testsuite/
>> * gcc.dg/tree-ssa/pr71206.c: New testcase.
>
>
> --
> Marc Glisse
prev parent reply other threads:[~2016-05-20 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 23:23 Marc Glisse
2016-05-20 7:12 ` Marc Glisse
2016-05-20 9:31 ` Richard Biener [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='CAFiYyc3woshBW-X=tg85QQ5GPtXMj_kkCvgtWqYOVbsUugYvsw@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=marc.glisse@inria.fr \
/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).