From: Ian Lance Taylor <iant@google.com>
To: Nikolaos Kavvadias <nkavv@physics.auth.gr>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Extracting information from GCC register allocation
Date: Tue, 14 Nov 2006 18:23:00 -0000 [thread overview]
Message-ID: <m33b8l28i6.fsf@localhost.localdomain> (raw)
In-Reply-To: <4559DD3C.9010704@physics.auth.gr>
Nikolaos Kavvadias <nkavv@physics.auth.gr> writes:
> 1. Is it possible to emit something close to assembly with
> pseudo-registers instead of registers? I mean, is it possible to do this
> just before each one of these passes? Or would it be possible to
> devise such pass (e.g. an emitter just prior greg). I can see some RTL
> stuff with pseudos (e.g. *.lreg) but is it semantically complete in
> order to be possible to translate it to assembly (even though with
> infinite registers)?
Yes.
> 2. Is it possible to explicitly mark the fill/spill instructions (or
> RTL statements) in such RTL dumps?
It would take a bit of work in reload, but, yes, it is possible.
> 3. Supposedly a <machine.h> description is devised that has a
> ridiculously large of registers (so that spills *almost* never will
> occur).
> Will this approach the effect of register allocation for infinite
> registers or there exist other GCC-specific constraints. What are the
> limits in the number of registers, registers in classes, allocable
> registers etc (i've seen some very bad restrictions in LCC due to the
> use of masks with host-dependent size).
There are no gcc constraints of this form, up to having a few million
hard registers. Implementing a very large number of hard registers
will tend to slow the compiler down, as there are a number of arrays
and bitmaps which are sized to the number of registers.
> 4. There is some discussion around gmp/mpfr support in GCC lately. Are
> we close to using arbitrary-size integers throught the GCC
> infrastructure?
No, not at all. That would be very slow and would bring little
benefit.
Ian
prev parent reply other threads:[~2006-11-14 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1163450950.10266.ezmlm@gcc.gnu.org>
2006-11-14 15:14 ` Nikolaos Kavvadias
2006-11-14 18:23 ` Ian Lance Taylor [this message]
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=m33b8l28i6.fsf@localhost.localdomain \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=nkavv@physics.auth.gr \
/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).