From: Jim Wilson <wilson@specifixinc.com>
To: xyzzy@hotpop.com
Cc: gcc@gcc.gnu.org
Subject: Re: Backend port: Minimizing register usage in favor of memory accesses
Date: Wed, 31 Mar 2004 01:48:00 -0000 [thread overview]
Message-ID: <4069D937.9000507@specifixinc.com> (raw)
In-Reply-To: <200403301148.19194.xyzzy@hotpop.com>
xyzzy@hotpop.com wrote:
> I understand that one of the goals of any optimizing compiler is to maximize
> use of registers since this is the fastest and least space consuming type of
> instruction on most processors.
The goal of an optimizing compiler is to produce the fastest code for
the target. If the target wants registers to be used, then we use
registers. If the target doesn't want registers to be used, then we
don't use registers.
> Is there any way to force the GCC backend to do this, if at all?
We have been doing this since the beginning for an i386 target.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2004-03-30 20:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 17:48 xyzzy
2004-03-31 1:43 ` Joern Rennecke
2004-03-31 1:48 ` Jim Wilson [this message]
2004-03-31 12:23 ` xyzzy
2004-04-01 19:48 ` Jim Wilson
2004-03-31 12:53 ` Richard Earnshaw
2004-03-31 13:05 ` xyzzy
2004-03-31 13:49 ` Robert Dewar
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=4069D937.9000507@specifixinc.com \
--to=wilson@specifixinc.com \
--cc=gcc@gcc.gnu.org \
--cc=xyzzy@hotpop.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).