public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Daniel Berlin <dberlin@redhat.com>
Cc: Robert Dewar <dewar@gnat.com>, Untitled <gcc@gcc.gnu.org>,
	Stan Shebs <shebs@apple.com>
Subject: Re: Graph coloring for register allocation?
Date: Fri, 19 Jan 2001 11:09:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.30.0101191905130.28457-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <B68BBF77.133C0%dberlin@redhat.com>

On Wed, 17 Jan 2001, Daniel Berlin wrote:

> I've been working on, besides the SSA value numbering stuff (which works
> nicely, I'm just putting the finishing touches on it before contributing.
> Probably be a few weeks. ), an register allocator that also does live range
> splitting. It's based on optimistic register coalescing
> ( http://citeseer.nj.nec.com/park98optimistic.html ).
> This is, from what I understand, pretty close to state of the art, if not
> there already.

Is this any relation to David Miller's register allocator that was being
written a couple of years ago (e.g.
http://gcc.gnu.org/ml/gcc/1999-01n/msg00221.html ), or is that now a dead
project?

-- 
Joseph S. Myers
jsm28@cam.ac.uk

  parent reply	other threads:[~2001-01-19 11:09 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
2001-01-23  9:11               ` Daniel Berlin
2001-01-19 11:09   ` Joseph S. Myers [this message]
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.LNX.4.30.0101191905130.28457-100000@kern.srcf.societies.cam.ac.uk \
    --to=jsm28@cam.ac.uk \
    --cc=dberlin@redhat.com \
    --cc=dewar@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --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).