public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernd Schmidt <bernds@codesourcery.com>
To: Richard Henderson <rth@redhat.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [RFC] Remove -freorder-blocks-and-partition
Date: Tue, 19 Jul 2011 21:56:00 -0000	[thread overview]
Message-ID: <4E25FA5E.9010303@codesourcery.com> (raw)
In-Reply-To: <4E25F810.6050904@redhat.com>

On 07/19/11 23:33, Richard Henderson wrote:
> But after pass_partition_blocks, we run into trouble.  There
> are no less than 4 other passes that add *new* crossing jumps
> without doing *any* of the subsequent fixups for less capable
> targets: pass_outof_cfg_layout_mode, pass_reorder_blocks,
> pass_sched2 (ia64 only? it's in code in haifa that looks like
> speculative load fixups), and pass_convert_to_eh_region_ranges.

Is it possible to leave it in for targets to call during their reorg
pass, which I'm assuming is late enough? Really the entire pass pipeline
after reload needs rethinking.

I'm not necessarily opposed to removing it though. I also ran into the
lack of test coverage.


Bernd

  reply	other threads:[~2011-07-19 21:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-19 21:43 Richard Henderson
2011-07-19 21:56 ` Bernd Schmidt [this message]
2011-07-19 22:09   ` Richard Henderson
2011-07-19 23:18     ` Joern Rennecke
2011-07-19 22:28 ` Joern Rennecke
2011-07-19 22:44   ` Richard Henderson
2011-07-25  7:40 ` Xinliang David Li
2011-07-25 11:05   ` Paolo Bonzini
2011-07-25 18:40     ` Xinliang David Li
2011-07-26  1:29     ` Xinliang David Li
2011-07-26  2:33       ` Joern Rennecke
2011-07-27  6:47         ` Xinliang David Li
2011-07-27  8:12           ` Paolo Bonzini
2011-08-03 21:06       ` Jan Hubicka
2011-08-03 21:46         ` Xinliang David Li
2011-08-04 13:32           ` Jan Hubicka
2011-08-04 13:39           ` Jan Hubicka
2011-08-04 16:03             ` Taras Glek
2011-08-03 20:56     ` Jan Hubicka
2011-08-03 20:50 ` Jan Hubicka
2011-07-19 22:43 Steven Bosscher

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=4E25FA5E.9010303@codesourcery.com \
    --to=bernds@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=rth@redhat.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).