public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mircea Namolaru <NAMOLARU@il.ibm.com>
To: weigand@i1.informatik.uni-erlangen.de
Cc: law@redhat.com, gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org,
	Ayal Zaks <ZAKS@il.ibm.com>
Subject: Re: [PATCH] Re: Bad code generated by inter-block scheduling
Date: Mon, 27 Sep 2004 14:01:00 -0000	[thread overview]
Message-ID: <OFE347DD04.8E6C84B9-ONC2256F1C.004082AB-42256F1C.004210A5@il.ibm.com> (raw)

> Instead of piling more hacks on top, I've tried to completely
> remove 'haifa_edge' and everything related to it, and use the
> standard CFG data structures instead -- this way we will
> automatically get the exit edges.

When we developed this code years ago the CFG was not maintained
during compilation. It's a good idea to use the standard CFG data 
structures.

> For the decision interblock vs. speculative, I agree that this
> should just be post-dominance.  However, the split-edges stuff
> is also used, in the speculative case, to find all the blocks
> where speculative motion could cause a variable to become live
> at start that previously wasn't.

For a speculative motion we must avoid moving a definition of a
register R into a place where it is currently live.

This is the main reason for computing the split edges. The split
edges also provide an easy way to determine if two basic blocks are 
equivalent without explicit computation of post-dominance relation.

Mircea Namolaru

             reply	other threads:[~2004-09-27 11:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-27 14:01 Mircea Namolaru [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-09-22 21:36 Jeffrey A Law
2004-09-24  1:21 ` [PATCH] " Ulrich Weigand
2004-09-24  6:46   ` Jeffrey A Law
2004-09-24 18:16     ` 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=OFE347DD04.8E6C84B9-ONC2256F1C.004082AB-42256F1C.004210A5@il.ibm.com \
    --to=namolaru@il.ibm.com \
    --cc=ZAKS@il.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=weigand@i1.informatik.uni-erlangen.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).