🚀 go-pugleaf

I just read in 'INSTALL' of gcc-2.5.7:
>    The GNU compiler does not really support the Super SPARC processor
> that is used in SPARC Station 10 and similar class machines.  You can
> get code that runs by specifying `sparc' as the cpu type; however, its
> performance is not very good, and may vary widely according to the
> compiler version and optimization options used.  This is because the
> instruction scheduling parameters designed for the Sparc are not correct
> for the Super SPARC.  Implementing scheduling parameters for the Super
> SPARC might be a good project for someone who is willing to learn a
> great deal about instruction scheduling in GNU CC.

I've got a few questions on this. If someone knows the answers, please
let me know. 

? Does this mean, that SPARC 10 needs special Code that would not run
  on vanilla SPARC anymore? [I assume yes]

? How much faster would native SPARC 10 code be.?
  10-20%? 50%?  100-200%?

? Does this apply to integer or floating point or both?

? How solves the unbundled Sun compiler this problem? Does it have a
  switch to produce native SPARC 10 code?

? If native SPARC 10 code doesn't run on older SPARC, is all the
  software distributet in binary form compiled for old SPARC and don't
  make use of SPARC 10? Or is there a mechanism to have two code
  versions in one binary?

? And last but not least (you guessed it :-): are there plans to make
  gcc able to produce native SPARC 10 code this year?

-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@wavehh.hanse.de>,Voice+4940-5221829,Fax.-5228536

Smile!   >8=B  >:)