From: "H.J. Lu" <hjl.tools@gmail.com>
To: Kai Tietz <ktietz70@googlemail.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch tree-optimization]: [2 of 3]: Boolify compares & more
Date: Thu, 21 Jul 2011 15:52:00 -0000 [thread overview]
Message-ID: <CAMe9rOqj51Ca7ZgdrbLM8Q8HpjoKy63N8T5ahQcuV+1mLYN5Cw@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOrKsBgmGdHkW2QADiFzeGQ5ZnG9MaTOpkHEy0iRjT_uqw@mail.gmail.com>
On Thu, Jul 21, 2011 at 8:40 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Thu, Jul 21, 2011 at 5:12 AM, Kai Tietz <ktietz70@googlemail.com> wrote:
>> 2011/7/21 Richard Guenther <richard.guenther@gmail.com>:
>>> With these two changes the patch is ok to commit (it will also
>>> regress gcc.target/i386/andor-2.c but that is an exact duplicate
>>> of the already regressed gcc.dg/tree-ssa/vrp47.c).
>>>
>>> Thanks,
>>> Richard.
>>>
>>
>> Ok, retested with your comments and applied at rev 176563.
>>
>
> This caused:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49805
>
This also caused:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49806
--
H.J.
prev parent reply other threads:[~2011-07-21 15:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 16:08 Kai Tietz
2011-07-08 9:28 ` Richard Guenther
2011-07-08 11:35 ` Kai Tietz
2011-07-08 12:03 ` Richard Guenther
2011-07-11 15:57 ` Kai Tietz
2011-07-12 9:29 ` Richard Guenther
2011-07-12 10:00 ` Kai Tietz
2011-07-12 10:34 ` Richard Guenther
2011-07-12 12:25 ` Kai Tietz
2011-07-12 14:38 ` Richard Guenther
2011-07-19 12:08 ` Kai Tietz
2011-07-19 12:16 ` Richard Guenther
2011-07-19 22:24 ` Kai Tietz
2011-07-20 13:32 ` Kai Tietz
2011-07-20 13:41 ` Richard Guenther
2011-07-20 14:07 ` Kai Tietz
2011-07-20 14:29 ` Richard Guenther
2011-07-20 17:43 ` Kai Tietz
2011-07-21 11:34 ` Kai Tietz
2011-07-21 12:13 ` Richard Guenther
2011-07-21 12:48 ` Kai Tietz
2011-07-21 15:49 ` H.J. Lu
2011-07-21 15:52 ` H.J. Lu [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=CAMe9rOqj51Ca7ZgdrbLM8Q8HpjoKy63N8T5ahQcuV+1mLYN5Cw@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ktietz70@googlemail.com \
--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).