From: xyzzy@hotpop.com
To: GCC list <gcc@gcc.gnu.org>, Richard Earnshaw <rearnsha@arm.com>
Subject: Re: Backend port: Minimizing register usage in favor of memory accesses
Date: Wed, 31 Mar 2004 13:05:00 -0000 [thread overview]
Message-ID: <200403311218.38548.xyzzy@hotpop.com> (raw)
In-Reply-To: <200403310943.i2V9hwZB013582@pc960.cambridge.arm.com>
On Wednesday 31 March 2004 11:43, Richard Earnshaw wrote:
> > The goal of an optimizing compiler is to produce the fastest code for
> > the target.
>
> Not necessarily. The goal of an optimizing compiler is to minimize some
> cost metric. Sometimes that cost metric is the same as 'target execution
> time' at other times it is something else, such as 'code size'. Many of
> the specific optimizations performed will be same regardless of the
> overall cost metric being worked on; but not always.
>
> R.
Yes, my mistake... I meant to say "the BEST code for the target", which is
horribly subjective.
next prev parent reply other threads:[~2004-03-31 10:18 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
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 [this message]
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=200403311218.38548.xyzzy@hotpop.com \
--to=xyzzy@hotpop.com \
--cc=gcc@gcc.gnu.org \
--cc=rearnsha@arm.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).