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 14:43:27 -0400 (EDT)
- Subject: Re: Mechanism to configure default scheduling model on PA
> > In a similar vein, Stefan Becker was
> > interested in being able to change the default architecture without
> > hacking config.gcc.
> I've been pondering this kind of thing recently as well. Specifically, I've
> been thinking about requesting comments on changing GCC's behavior when
> configured/built on a PA2.0 machine.
>
> Right now if config.guess returns hppa1.0*, then you get PA1.0. If it
> returns hppa1.1* or hppa2.0*, then you get PA1.1. What I've been pondering
> is changing the behavior of hppa2.0* so that you'd get PA2.0 code generation.
> (note you'd still have to configure hppa64 to get PA64).
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.
I still like the idea of being able to configure the default in case a
more portable default is desired.
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)