From: Richard Henderson <rth@redhat.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: [RFC] avoiding too narrow register classes in reload
Date: Tue, 14 Dec 2004 02:06:00 -0000 [thread overview]
Message-ID: <20041214020635.GA16249@redhat.com> (raw)
In-Reply-To: <oracshki96.fsf@livre.redhat.lsd.ic.unicamp.br>
On Mon, Dec 13, 2004 at 07:20:21PM -0200, Alexandre Oliva wrote:
> Does this look like a reasonable approach?
Yes.
> Should other locations that compare
> reg_class_size with 1 be adjusted similarly?
Probably would be good.
r~
next prev parent reply other threads:[~2004-12-14 2:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 21:20 Alexandre Oliva
2004-12-14 2:06 ` Richard Henderson [this message]
2004-12-14 21:20 ` Alexandre Oliva
2004-12-14 22:31 ` Richard Henderson
2004-12-15 6:56 ` Alexandre Oliva
2004-12-15 8:09 ` Richard Henderson
2004-12-15 20:07 ` Alexandre Oliva
2004-12-16 14:14 ` Dave Korn
2004-12-14 16:22 ` Bernd Schmidt
2004-12-14 20:53 ` Alexandre Oliva
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=20041214020635.GA16249@redhat.com \
--to=rth@redhat.com \
--cc=aoliva@redhat.com \
--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).