public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Guenther <rguenther@suse.de>
To: Steven Bosscher <stevenb.gcc@gmail.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Remove basic_block->loop_depth
Date: Tue, 14 Aug 2012 11:01:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.00.1208141257570.28649@zhemvz.fhfr.qr> (raw)
In-Reply-To: <CABu31nPSFM8pJ1VYhLxQjCUwpMkYeVvQOe9jUuC-hAGqrkpP3g@mail.gmail.com>

On Tue, 14 Aug 2012, Steven Bosscher wrote:

> On Tue, Aug 14, 2012 at 12:48 PM, Richard Guenther <rguenther@suse.de> wrote:
> > If SPU md reorg would like to look at loop structures it should
> > compute them.  Simply call flow_loops_find, which hopefully works
> > in CFG RTL mode (which I think is the mode available from md reorg?).
> 
> No, the CFG is destroyed just before MD reorg, because most MD reorgs
> are not CFG aware.
> 
> But some back-ends re-surrect it (bfin, ia64, c6x, etc...), and do
> compute loops (c6x at least).

I suppose we could push down freeing the CFG to the individual MD
reorgs and make the default MD reorg simply free the CFG ...

Richard.

  reply	other threads:[~2012-08-14 11:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 13:02 Richard Guenther
2012-08-14 10:16 ` Ulrich Weigand
2012-08-14 10:51   ` Richard Guenther
2012-08-14 11:00     ` Steven Bosscher
2012-08-14 11:01       ` Richard Guenther [this message]
2012-08-15 12:04     ` [rfc] Fix SPU build (Re: [PATCH] Remove basic_block->loop_depth) Ulrich Weigand
2012-08-15 12:07       ` Richard Guenther
2012-08-15 22:18         ` Ulrich Weigand

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=alpine.LNX.2.00.1208141257570.28649@zhemvz.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=stevenb.gcc@gmail.com \
    --cc=uweigand@de.ibm.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).