fixes for faq.html

Martin Reinecke martin@MPA-Garching.MPG.DE
Fri Jul 16 05:55:00 GMT 1999


This patch adds an omitted HTML tag and an omitted word in faq.html.


Index: wwwdocs/htdocs/faq.html
===================================================================
RCS file: /cvs/egcs/wwwdocs/htdocs/faq.html,v
retrieving revision 1.131
diff -c -3 -p -r1.131 faq.html
*** faq.html    1999/07/16 09:33:14     1.131
--- faq.html    1999/07/16 12:51:39
*************** or end of these variables is an implicit
*** 418,424 ****
  <a name="testsuite"></a>
  <h1>Testsuite problems</h1>
  
! <h2><a name="testsuite">Why is there no testsuite in gcc-2.95</a>
  <p>The GCC testsuite is not included in the gcc-2.95 release due to the
  uncertain copyright status of some tests.
  
--- 418,424 ----
  <a name="testsuite"></a>
  <h1>Testsuite problems</h1>
  
! <h2><a name="testsuite">Why is there no testsuite in gcc-2.95</a></h2>
  <p>The GCC testsuite is not included in the gcc-2.95 release due to the
  uncertain copyright status of some tests.
  
*************** ANSI/ISO standard. Starting with gcc-2.9
*** 610,616 ****
  by default relies on these rules to produce more efficient code and thus
  will produce malfunctioning kernels.
  To work around this problem, the flag <CODE>-fno-strict-aliasing</CODE>
! must be added to the <CODE>CFLAGS</CODE> variable in main kernel Makefile.
  
  <p>If you try to build a 2.0.x kernel for Intel machines with any compiler
  other than gcc-2.7.2, then you are on your own.
--- 610,616 ----
  by default relies on these rules to produce more efficient code and thus
  will produce malfunctioning kernels.
  To work around this problem, the flag <CODE>-fno-strict-aliasing</CODE>
! must be added to the <CODE>CFLAGS</CODE> variable in the main kernel Makefile.
  
  <p>If you try to build a 2.0.x kernel for Intel machines with any compiler
  other than gcc-2.7.2, then you are on your own.


More information about the Gcc-patches mailing list