public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <paolo.bonzini@polimi.it>
To: Steven Bosscher <stevenb@suse.de>
Cc: gcc@gcc.gnu.org
Subject: Re: Compile-time and execution-time impact of CSE - some numbers
Date: Tue, 31 Aug 2004 21:03:00 -0000	[thread overview]
Message-ID: <1093985632.4134e5600d3ab@webmail.polimi.it> (raw)
In-Reply-To: <200408311550.27667.stevenb@suse.de>

> The second step would be to
> make cse.c use the CFG (ie. FOR_BB_INSNS/BB_HEAD/BB_ END/etc.) instead
> of relying on block notes.

Block notes are the lesser problem.  It's using barriers and labels to detect 
edge types, that would drive me nuts :-)

> Next you'd clean up the path following code
> to track back only to the last visited block before following a jump.

Is it different from a very low --param max-cse-path-length?

Paolo

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

      reply	other threads:[~2004-08-31 20:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31 13:52 Paolo Bonzini
2004-08-31 14:39 ` Steven Bosscher
2004-08-31 21:03   ` Paolo Bonzini [this message]

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=1093985632.4134e5600d3ab@webmail.polimi.it \
    --to=paolo.bonzini@polimi.it \
    --cc=gcc@gcc.gnu.org \
    --cc=stevenb@suse.de \
    /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).