From: Richard Guenther <richard.guenther@gmail.com>
To: Tom de Vries <vries@codesourcery.com>
Cc: Steven Bosscher <stevenb.gcc@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, PR43864] Gimple level duplicate block cleanup - test cases.
Date: Thu, 25 Aug 2011 10:09:00 -0000 [thread overview]
Message-ID: <CAFiYyc1PhFvpOSaD8kmhGcQFi_k0wn-dAyxu9R=XV-4SzeYJbA@mail.gmail.com> (raw)
In-Reply-To: <4E4E8F29.3060907@codesourcery.com>
On Fri, Aug 19, 2011 at 6:28 PM, Tom de Vries <vries@codesourcery.com> wrote:
> On 07/17/2011 08:33 PM, Tom de Vries wrote:
>> Updated version.
>>
>> On 06/08/2011 11:45 AM, Tom de Vries wrote:
>>> On 06/08/2011 11:42 AM, Tom de Vries wrote:
>>>
>>>> I'll send the patch with the testcases in a separate email.
>>>
>>
>
> 2 extra testcases added.
>
> OK for trunk?
Ok.
THanks,
Richard.
> Thanks,
> - Tom
>
> 2011-08-19 Tom de Vries <tom@codesourcery.com>
>
> PR middle-end/43864
> * gcc.dg/fold-compare-2.c (dg-options): Add -fno-tree-tail-merge.
> * gcc/testsuite/gcc.dg/uninit-pred-2_c.c: Same.
> * gcc.dg/pr43864.c: New test.
> * gcc.dg/pr43864-2.c: Same.
> * gcc.dg/pr43864-3.c: Same.
> * gcc.dg/pr43864-4.c: Same.
>
next prev parent reply other threads:[~2011-08-25 7:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 9:49 [PATCH, PR43864] Gimple level duplicate block cleanup Tom de Vries
2011-06-08 9:55 ` [PATCH, PR43864] Gimple level duplicate block cleanup - test cases Tom de Vries
2011-07-18 2:54 ` Tom de Vries
2011-08-19 18:38 ` Tom de Vries
2011-08-25 10:09 ` Richard Guenther [this message]
2011-06-08 10:09 ` [PATCH, PR43864] Gimple level duplicate block cleanup Richard Guenther
2011-06-08 10:40 ` Steven Bosscher
2011-06-10 17:16 ` Tom de Vries
2011-06-14 15:12 ` Richard Guenther
2011-07-12 12:21 ` Tom de Vries
2011-07-12 14:37 ` Richard Guenther
2011-07-18 0:41 ` Tom de Vries
2011-07-22 15:54 ` Richard Guenther
2011-08-19 18:33 ` Tom de Vries
2011-08-24 9:00 ` Tom de Vries
2011-08-25 1:07 ` Ian Lance Taylor
2011-08-25 9:30 ` Richard Guenther
2011-06-10 18:43 ` Jeff Law
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='CAFiYyc1PhFvpOSaD8kmhGcQFi_k0wn-dAyxu9R=XV-4SzeYJbA@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=stevenb.gcc@gmail.com \
--cc=vries@codesourcery.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).