From: Richard Biener <richard.guenther@gmail.com>
To: Steven Bosscher <stevenb.gcc@gmail.com>
Cc: Marek Polacek <polacek@redhat.com>,
Eric Botcazou <ebotcazou@adacore.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Don't bypass blocks with multiple latch edges (PR middle-end/54838)
Date: Thu, 29 Nov 2012 09:35:00 -0000 [thread overview]
Message-ID: <CAFiYyc1EQK16HoyV94UA3A+-6THMp-Otry+Y+_SwQzig6VJTiw@mail.gmail.com> (raw)
In-Reply-To: <CABu31nP==VqSUZ07ZE1z06y5=Tqd9a27YM_oVJnBM8_MpU=Uhg@mail.gmail.com>
On Thu, Nov 29, 2012 at 9:56 AM, Steven Bosscher <stevenb.gcc@gmail.com> wrote:
> On Thu, Nov 29, 2012 at 9:34 AM, Richard Biener wrote:
>> On Wed, Nov 28, 2012 at 7:24 PM, Marek Polacek wrote:
>>> I admit I'm not sure what to look at, maybe cprop should have in
>>> properties_destroyed PROP_loops? Well, then we need to remove one
>>> assert in loop-init.c. So something like:
>>
>> Definitely not - that means to not preserve loops until after cprop. The goal
>> is to preserve loops everywhere!
>
> It'd be nice if this was documented somewhere...
On my TODO list for stage3 ;)
Richard.
> Ciao!
> Steven
next prev parent reply other threads:[~2012-11-29 9:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 14:28 Marek Polacek
2012-11-28 9:55 ` Eric Botcazou
2012-11-28 18:39 ` Marek Polacek
2012-11-29 8:34 ` Richard Biener
2012-11-29 8:57 ` Steven Bosscher
2012-11-29 9:35 ` Richard Biener [this message]
2012-11-29 15:39 ` Marek Polacek
2012-11-29 15:42 ` Marek Polacek
2012-11-29 15:51 ` Steven Bosscher
2012-11-29 16:56 ` Marek Polacek
2012-11-29 17:45 ` Eric Botcazou
2012-11-30 9:02 ` Richard Biener
2012-11-30 16:28 ` Marek Polacek
2012-11-30 22:01 ` Eric Botcazou
2012-11-30 22:33 ` Eric Botcazou
2012-12-01 16:18 ` Marek Polacek
2012-12-02 10:06 ` Eric Botcazou
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=CAFiYyc1EQK16HoyV94UA3A+-6THMp-Otry+Y+_SwQzig6VJTiw@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=polacek@redhat.com \
--cc=stevenb.gcc@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).