Re: sparcv9 FAQ entry

[Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>]

On Sat, 15 Jan 2000, Martin von Loewis wrote:
> Since I still can't get the FAQ-o-matic to work for me, I gave up
> and added the entry below to the old FAQ.

I see a couple of issues with the FAQ-o-matic as well and am strongly
considering tu suggest that we keep the ``old'' FAQ, but I'll bring
this up on gcc@gcc.gnu.org shortly.

> +    <li><a href="#sparcv9">How to build a compiler for sparcv9/sparc64/ultrasparc</a></li>

Hmm, this is a bit on the border-line of being better suited for
install/specific.html, but I guess it's okay for the FAQ as well.

Please note that it's UltraSPARC, not ultrasparc. I agree we can (and
should) use the lower-case versions when referring to strings as used by
configure, but ultrasparc is a proper name.

> +<p>Therefore, it is recommended to use gcc in 32-bit mode only on
> +UltraSparc machines, even on Solaris 7 or newer.If

s/gcc/GCC/
s/newer.If/newer. If/

> +to experiment with a compiler for that architecture, you may want to
> +try the development snapshots; it contains a number of
       ^^^^                    ^^^^^        ^

I installed the patch below to fix these issues.

Thanks for your original contribution, of course!

Gerald

Index: faq.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/faq.html,v
retrieving revision 1.154
diff -c -r1.154 faq.html
*** faq.html	2000/01/14 23:30:32	1.154
--- faq.html	2000/01/17 20:41:21
***************
*** 53,59 ****
  
    <li><a href="#platform">Platform-specific issues</a>
    <ol>    	  
!     <li><a href="#sparcv9">How to build a compiler for sparcv9/sparc64/ultrasparc</a></li>
      <li><a href="#x86eh">Problems with exception handling on x86 platforms</a></li>
      <li><a href="#asmclobber">Problems with <tt>Invalid `asm' statement</tt>s</a></li>
      <li><a href="#linuxkernel">Building Linux kernels</a>  </li>
--- 53,59 ----
  
    <li><a href="#platform">Platform-specific issues</a>
    <ol>    	  
!     <li><a href="#sparcv9">How to build a compiler for sparcv9/sparc64/UltraSPARC</a></li>
      <li><a href="#x86eh">Problems with exception handling on x86 platforms</a></li>
      <li><a href="#asmclobber">Problems with <tt>Invalid `asm' statement</tt>s</a></li>
      <li><a href="#linuxkernel">Building Linux kernels</a>  </li>
***************
*** 520,526 ****
  
  <p>Please read the <a href="install/specific.html">host/target specific
installation</a> notes, too.</p>
  
! <h2><a name="sparcv9">How to build a compiler for sparcv9/sparc64/ultrasparc?</a></h2>
  
  <p>GCC up to version 2.95.x does not fully support the SPARC version 9
  architecture. Even though the port for this architecture is in use by
--- 520,526 ----
  
  <p>Please read the <a href="install/specific.html">host/target specific
installation</a> notes, too.</p>
  
! <h2><a name="sparcv9">How to build a compiler for sparcv9/sparc64/UltraSPARC?</a></h2>
  
  <p>GCC up to version 2.95.x does not fully support the SPARC version 9
  architecture. Even though the port for this architecture is in use by
***************
*** 530,540 ****
  floating-point operations. You don't need to report that there are
  bugs; we know.</p>
  
! <p>Therefore, it is recommended to use gcc in 32-bit mode only on
! UltraSparc machines, even on Solaris 7 or newer.If you absolutely need
  to experiment with a compiler for that architecture, you may want to
! try the development snapshots; it contains a number of
! improvements. Hopefully, the next major release of gcc will support
  this architecture.</p>
  
  <h2><a name="x86eh">Problems with exception handling on x86
platforms</a></h2>
--- 530,540 ----
  floating-point operations. You don't need to report that there are
  bugs; we know.</p>
  
! <p>Therefore, it is recommended to use GCC in 32-bit mode only on
! UltraSPARC machines, even on Solaris 7 or newer. If you absolutely need
  to experiment with a compiler for that architecture, you may want to
! try our development snapshots, which contain a number of
! improvements. Hopefully, the next major release of GCC will support
  this architecture.</p>
  
  <h2><a name="x86eh">Problems with exception handling on x86
platforms</a></h2>
***************
*** 1190,1196 ****
  <hr>
  
  <p><a href="index.html">Return to the GCC home page</a></p>
! <p><i>Last modified: December 24, 1999</i></p>
  
  </body>
  </html>
--- 1190,1196 ----
  <hr>