From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: Richard.Earnshaw@arm.com
Cc: drow@mvista.com, gcc-patches@gcc.gnu.org
Subject: Re: RFC: New approach to --with-cpu
Date: Thu, 01 Aug 2002 07:41:00 -0000 [thread overview]
Message-ID: <200208011440.g71Eesdr003625@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <200208011329.OAA23413@cam-mail2.cambridge.arm.com> from "Richard Earnshaw" at Aug 1, 2002 02:29:56 pm
> But why would a *user* of the compiler want to use a different set of
> 'cost' metrics in another part of the compiler from the 'cost' metrics
> used by the scheduler?
The scheduler supports generation of code using several different
scheduling models. This allows testing of the models without having
to have a different compiler for each. Where binaries are being
distributed, the compiler may be running on the latest PA gizmo
but a more portable arch and scheduling model may be desired for
the code being distributed.
The HP ansi compiler supports options to select the target architecture,
data model, apptype, OS, and scheduler model (tuning).
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
next prev parent reply other threads:[~2002-08-01 14:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 18:54 John David Anglin
2002-07-30 23:03 ` Daniel Jacobowitz
2002-07-31 7:53 ` John David Anglin
2002-07-31 8:09 ` Daniel Jacobowitz
2002-07-31 8:30 ` Richard Earnshaw
2002-07-31 9:02 ` Daniel Jacobowitz
2002-07-31 10:34 ` John David Anglin
2002-07-31 13:27 ` Daniel Jacobowitz
2002-08-01 3:31 ` Richard Sandiford
2002-08-01 3:57 ` Richard Earnshaw
2002-08-01 8:15 ` John David Anglin
2002-08-01 8:23 ` Daniel Jacobowitz
2002-08-01 11:40 ` John David Anglin
2002-08-01 6:30 ` Richard Earnshaw
2002-08-01 7:41 ` John David Anglin [this message]
[not found] <20020801125224.GA5374@nevyn.them.org>
2002-08-01 6:04 ` Richard Earnshaw
2002-08-01 6:25 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2002-07-30 15:27 Daniel Jacobowitz
2002-07-31 6:35 ` Richard Sandiford
2002-07-31 6:41 ` Daniel Jacobowitz
2002-07-31 6:54 ` Richard Sandiford
2002-07-31 7:28 ` Daniel Jacobowitz
2002-07-31 7:36 ` Richard Sandiford
2002-07-31 7:46 ` Daniel Jacobowitz
2002-07-31 7:50 ` Richard Sandiford
2002-07-31 8:04 ` Daniel Jacobowitz
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=200208011440.g71Eesdr003625@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=Richard.Earnshaw@arm.com \
--cc=drow@mvista.com \
--cc=gcc-patches@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).