public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Matz <matzmich@cs.tu-berlin.de>
To: Daniel Berlin <dberlin@redhat.com>
Cc: Michael Hayes <m.hayes@elec.canterbury.ac.nz>,
	Robert Dewar <dewar@gnat.com>, Untitled <gcc@gcc.gnu.org>,
	Stan Shebs <shebs@apple.com>
Subject: Re: Graph coloring for register allocation?
Date: Tue, 23 Jan 2001 03:26:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.21.0101231213170.11475-100000@platon> (raw)
In-Reply-To: <Pine.LNX.4.31.0101211250250.4158-100000@www.cgsoftware.com>

Hi,

On Sun, 21 Jan 2001, Daniel Berlin wrote:
> > Yep, I have them, but not looked at them closely due to missing time.
> > Also, meanwhile I was playing with the thought of building the
> > interference graph incrementally (as proposed in one of the newer
> > articles), and for that u/d-d/u-chains are not the best source. But at
> > least for gathering the info your routines seem very handy.
> What papers show how to build it incrementally?
> I couldn't find any.

Well, not incrementally, but sparse construction which can be more easily
extended for incremental updates (it only needs all def/use site of a
variable, no global information, and no incremental update of local
liveness per basic block). It's from the MLRISC guys in their new register
allocator: http://cm.bell-labs.com/cm/cs/what/smlnj/compiler-notes/new-ra.ps

> Because there are so many implementations available, i've started with
> Iterated Register Coalescing, and will convert it to optimistic when it's
> done.
> Works well so far.

Cool. Any code, CVS branches or similar stuff?

> Just so we are all on the same page, everyone realizes that the new
> register allocator will replace the regmove, the local-alloc, and the
> global-alloc passes, right?

Yep, and probably much (though not all) of reload*.c. 


Ciao,
Michael.

  parent reply	other threads:[~2001-01-23  3:26 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-17 17:48 dewar
2001-01-17 18:31 ` Daniel Berlin
2001-01-17 20:40   ` Michael Matz
2001-01-19 10:58     ` Daniel Berlin
2001-01-19 14:16       ` Michael Hayes
2001-01-19 14:51         ` Daniel Berlin
2001-01-19 16:51           ` Michael Hayes
2001-01-20 11:16             ` Daniel Berlin
2001-01-20 13:03               ` Michael Hayes
2001-01-20 15:29         ` Michael Matz
2001-01-21  9:57           ` Daniel Berlin
2001-01-21 13:45             ` Daniel Berlin
2001-01-22  2:05               ` Nick Ing-Simmons
2001-01-22 14:23               ` Richard Henderson
2001-01-22 14:32                 ` Daniel Berlin
2001-01-22 15:07                   ` Richard Henderson
2001-01-22 16:25                     ` Daniel Berlin
2001-01-24  0:17               ` Zack Weinberg
2001-01-24 10:08                 ` Daniel Berlin
2001-01-24 10:47                   ` Zack Weinberg
2001-01-24 11:19                     ` David Edelsohn
2001-01-24 13:48                     ` Richard Henderson
2001-01-24 14:53                       ` Michael Hayes
2001-01-24 14:58                         ` Richard Henderson
2001-01-24 15:07                           ` Michael Hayes
2001-01-24 15:33                             ` Richard Henderson
2001-01-24 11:23                   ` Michael Matz
2001-01-24 12:10                     ` Zack Weinberg
2001-01-24 12:18                       ` Daniel Berlin
2001-01-24 17:22                       ` Jeffrey A Law
2001-01-25  1:07                   ` Nick Ing-Simmons
2001-01-21 21:31             ` Phil Edwards
2001-01-23  3:26             ` Michael Matz [this message]
2001-01-23  9:11               ` Daniel Berlin
2001-01-19 11:09   ` Joseph S. Myers
2001-01-19 11:27     ` Daniel Berlin
  -- strict thread matches above, loose matches on Subject: below --
2001-01-21 13:47 dewar
2001-01-17 17:36 Stan Shebs

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=Pine.GSO.4.21.0101231213170.11475-100000@platon \
    --to=matzmich@cs.tu-berlin.de \
    --cc=dberlin@redhat.com \
    --cc=dewar@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=m.hayes@elec.canterbury.ac.nz \
    --cc=shebs@apple.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).