This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Mechanism to configure default scheduling model on PA
- From: "John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca>
- To: law at redhat dot com
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Fri, 31 May 2002 15:44:53 -0400 (EDT)
- Subject: Re: Mechanism to configure default scheduling model on PA
> In message <200205311843.g4VIhRDk006815@hiauly1.hia.nrc.ca>, "John David
> Anglin" writes:
> > Yes, it seems reasonable to default to the most advanced architecture
> > that the target supports. That should give the best overall performance.
> > It will also provide a better range of testing for each architecture.
> My suggestion was to default to whatever machine you're building the compiler
> on. Not the most modern architecture.
The compiler itself needs to be built with an architecture that's consistent
with the host machine, not the build machine. I would argue that the
default output of the compiler should be determined by the architecture
of the target machine.
In cases where build, host and target differ, then we have a cross
compiler scenario and the generated code may not run on the host or
build machine.
As you note, we don't need any new configuration option for architecture
selection.
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)