public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steven Bosscher <stevenb.gcc@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] bb-reorder: Improve compgotos pass (PR71785)
Date: Wed, 02 Nov 2016 10:40:00 -0000	[thread overview]
Message-ID: <CABu31nN0nVowQspRjnq3DiyWjetMR0ZjAdB+GdZwdW1NCwowfg@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc2d1PC3tjrihuRadbSVKvmEQ++DPSU8y4Rr7E+7_hd36w@mail.gmail.com>

 On Wed, Nov 2, 2016 at 10:02 AM, Richard Biener
<richard.guenther@gmail.com> wrote:
> On Mon, Oct 31, 2016 at 4:35 PM, Segher Boessenkool wrote:
>> On Mon, Oct 31, 2016 at 04:09:48PM +0100, Steven Bosscher wrote:
>>> On Sun, Oct 30, 2016 at 8:10 PM, Segher Boessenkool wrote:
>>> > +      cfg_layout_finalize ();
>>>
>>> I don't think you have to go into/out-of cfglayout mode for each iteration.
>>
>> Yeah probably.  I was too lazy :-)  It needs the cleanup_cfg every
>> iteration though, I was afraid that interacts.
>
> Ick.  Why would it need a cfg-cleanup every iteration?

I don't believe it needs a cleanup on every iteration. One cleanup at
the end should work fine.

Ciao!
Steven

  reply	other threads:[~2016-11-02 10:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-30 19:11 Segher Boessenkool
2016-10-31 15:10 ` Steven Bosscher
2016-10-31 15:35   ` Segher Boessenkool
2016-11-02  9:02     ` Richard Biener
2016-11-02 10:40       ` Steven Bosscher [this message]
2016-11-02 13:41         ` Segher Boessenkool
2016-11-02 13:51           ` Richard Biener
2016-11-02 15:27             ` Segher Boessenkool
2016-11-03  8:29               ` Richard Biener
2016-11-03 15:47                 ` Segher Boessenkool
2016-11-04  8:42                   ` 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=CABu31nN0nVowQspRjnq3DiyWjetMR0ZjAdB+GdZwdW1NCwowfg@mail.gmail.com \
    --to=stevenb.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    --cc=segher@kernel.crashing.org \
    /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).