Re: Mechanism to configure default scheduling model on PA

["John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca>]

> If you wanted to get more correct, then you'd look at the actual
> model # and map that into 700, 7100, 7100lc, 7200, 7300 or 8000.

I just went with a default based on the specified target architecture
because it's only possible to look at the model number in a native
build.  I didn't think it was worthwhile trying to get more precise
because of this and because it's possible to override the default
in BOOT_CFLAGS.

> 
> FWIW, PA700 is actually the first generation PA1.1 machines -- we never
> bothered writing descriptions for the original PA1.0 machines.  It's also
> the case that the previous default was 7100LC, not 7100.

Thanks for the clarification.

> So what I might recommend would be to use PA8000 for PA2.0 and newer and
> PA7100LC for the others.

It's easier to use PA7100LC for hppa1.0 and hppa1.1 targets, and PA8000 
for the rest.  A target with an unspecified architecture would use
PA8000.  The idea was to force people to specify their target
completely if they want something other than the default, and default
to the newer architecture.  Of course, config.guess generates a complete
specification if no target option is provided.

Does this approach sound ok?  In a similar vein, Stefan Becker was
interested in being able to change the default architecture without
hacking config.gcc.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)