public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@redhat.com>
To: Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de>
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Re: Bad code generated by inter-block scheduling
Date: Fri, 24 Sep 2004 06:46:00 -0000	[thread overview]
Message-ID: <1096001925.11715.731.camel@localhost.localdomain> (raw)
In-Reply-To: <200409240011.CAA06500@faui1m.informatik.uni-erlangen.de>

On Thu, 2004-09-23 at 18:11, Ulrich Weigand wrote:
> Maybe there's some way of retrieving this information from
> the dominator graph as well, but right now I don't really want
> to do actual algorithmic changes, just fix my bug ;-)
I understand...


> 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.  This went quite smoothly,
> I only had to change a couple of other places to use basic_block
> or edge pointers instead of indices.
Way way way cool.  That code has been on my hitlist for about 6
years now.  In the defense of the original haifa-sched developers,
their work pre-dates having a CFG, so they did just about everything
they needed inside haifa.  Removing that code as we've made the
CFG a first class structure within GCC hasn't progressed as well as
I would have liked.

I'll conditionally approve the patch -- however, the condition is
that it's updated for the edge vector changes after they go in, then
retested.  Please post the patch that actually gets installed.
[ The edge vector changes are bloody huge and I'd like to get them
  installed before we create conflicts for merging in that code. ]


> I now don't even need to call create_edge_list at all, the
> only other user of the edge_list, find_rgns, could easily
> be changed to just use the regular CFG data structures.
That would be a greatly appreciated follow-on patch.


Jeff

  reply	other threads:[~2004-09-24  4:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-22 18:52 Ulrich Weigand
2004-09-22 21:36 ` Jeffrey A Law
2004-09-24  1:21   ` [PATCH] " Ulrich Weigand
2004-09-24  6:46     ` Jeffrey A Law [this message]
2004-09-24 18:16       ` Ulrich Weigand
2004-09-27 14:01 Mircea Namolaru

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=1096001925.11715.731.camel@localhost.localdomain \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --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).