From: Brad Lucier <lucier@math.purdue.edu>
To: gcc@gcc.gnu.org
Cc: lucier@math.purdue.edu
Subject: curiosity about new-regalloc-branch
Date: Thu, 25 Jul 2002 06:10:00 -0000 [thread overview]
Message-ID: <200207250448.g6P4mgN00862@banach.math.purdue.edu> (raw)
I noted that things are still being checked into the new-regalloc-branch, e.g.,
http://gcc.gnu.org/ml/gcc-cvs/2002-07/msg00580.html
and I'm curious---since the new register allocator has been integrated into
the mainline, should these changes go into the mainline, too?
Brad
next reply other threads:[~2002-07-25 4:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 6:10 Brad Lucier [this message]
2002-07-25 9:15 ` Michael Matz
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=200207250448.g6P4mgN00862@banach.math.purdue.edu \
--to=lucier@math.purdue.edu \
--cc=gcc@gcc.gnu.org \
/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).