This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[patch] typos in web pages
- To: gcc-patches at gcc dot gnu dot org
- Subject: [patch] typos in web pages
- From: Jan van Male <jan dot vanmale at fenk dot wau dot nl>
- Date: Sun, 15 Oct 2000 18:01:30 +0200
Hi,
Attached is a patch to fix some typos in the web pages. Note that they
include patches to pages from the egcs releases. I'm unsure whether these
pages are considered frozen.
jan
Index: htdocs/cvswrite.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/cvswrite.html,v
retrieving revision 1.34
diff -c -2 -p -r1.34 cvswrite.html
*** cvswrite.html 2000/10/07 11:24:42 1.34
--- cvswrite.html 2000/10/15 15:39:24
*************** the appropriate policies.</p>
*** 95,99 ****
<dt>Global write permission.</dt> <dd>A very limited number of
developers have global write permission over the entire
! repostiory.</dd>
<dt>Localized write permission.</dt> <dd>This is for people who have
--- 95,99 ----
<dt>Global write permission.</dt> <dd>A very limited number of
developers have global write permission over the entire
! repository.</dd>
<dt>Localized write permission.</dt> <dd>This is for people who have
*************** Sun Feb 8 08:02:13 1998 John Carr <
*** 229,233 ****
</blockquote>
! <h3>First, I sync my local respository.</h3>
<blockquote>
--- 229,233 ----
</blockquote>
! <h3>First, I sync my local repository.</h3>
<blockquote>
Index: htdocs/extensions.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/extensions.html,v
retrieving revision 1.10
diff -c -2 -p -r1.10 extensions.html
*** extensions.html 2000/10/07 18:05:03 1.10
--- extensions.html 2000/10/15 15:39:25
*************** installation on non-Sun systems or when
*** 54,58 ****
provide a variety of C++ programming tools and other support to
GNU C++ programmers. It has been available for quite some time
! now, and, although it has been superceeded by <code>libstdc++</code>,
it is still providing some useful services. And, it has proven to
be a good testsuite for the compiler...
--- 54,58 ----
provide a variety of C++ programming tools and other support to
GNU C++ programmers. It has been available for quite some time
! now, and, although it has been superseded by <code>libstdc++</code>,
it is still providing some useful services. And, it has proven to
be a good testsuite for the compiler...
Index: htdocs/gnats.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gnats.html,v
retrieving revision 1.6
diff -c -2 -p -r1.6 gnats.html
*** gnats.html 2000/10/09 12:45:41 1.6
--- gnats.html 2000/10/15 15:39:25
*************** does not foo", "objc crashes when doing
*** 98,102 ****
<dd>A problem with the Objective C compiler.</dd>
<dt>optimization</dt>
! <dd>A problem only occuring under optimization.</dd>
<dt>target</dt>
<dd>The problem depends on the specific target architecture.</dd>
--- 98,102 ----
<dd>A problem with the Objective C compiler.</dd>
<dt>optimization</dt>
! <dd>A problem only occurring under optimization.</dd>
<dt>target</dt>
<dd>The problem depends on the specific target architecture.</dd>
*************** does not foo", "objc crashes when doing
*** 112,116 ****
<dl>
<dt>doc-bug</dt>
! <dd>The doumentation is incorrect.</dd>
<dt>accepts-illegal</dt>
<dd>GCC fails to reject erroneous code.</dd>
--- 112,116 ----
<dl>
<dt>doc-bug</dt>
! <dd>The documentation is incorrect.</dd>
<dt>accepts-illegal</dt>
<dd>GCC fails to reject erroneous code.</dd>
Index: htdocs/lists.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/lists.html,v
retrieving revision 1.50
diff -c -2 -p -r1.50 lists.html
*** lists.html 2000/10/13 23:54:30 1.50
--- lists.html 2000/10/15 15:39:25
*************** it to the list.
*** 88,92 ****
and try to avoid cross posting a message to several lists.
! <p>Please refrain from sending messages in HTML, RTF or similiar formats.</p>
--- 88,92 ----
and try to avoid cross posting a message to several lists.
! <p>Please refrain from sending messages in HTML, RTF or similar formats.</p>
Index: htdocs/news.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/news.html,v
retrieving revision 1.52
diff -c -2 -p -r1.52 news.html
*** news.html 2000/10/11 23:47:06 1.52
--- news.html 2000/10/15 15:39:25
*************** href="mailto:gcc@gcc.gnu.org?subject=g77
*** 168,172 ****
<dt><b>October 12, 1999</b></dt>
<dd>
! We are pleased to annouce Richard Earnshaw and Jason Merrill have been
given global write permissions throughout the GCC sources.
</dd>
--- 168,172 ----
<dt><b>October 12, 1999</b></dt>
<dd>
! We are pleased to announce that Richard Earnshaw and Jason Merrill have been
given global write permissions throughout the GCC sources.
</dd>
*************** The sixth snapshot of the ongoing re-wri
*** 304,308 ****
been released. It includes SGI STL 3.2, an automatically generated
<code><limits></code>, a partially re-written valarray, a working
! stringbuf and stringstream (for basic types). For more informtaion,
please check <a href="http://sources.redhat.com/libstdc++/">
libstdc++-2.90.5</a>.
--- 304,308 ----
been released. It includes SGI STL 3.2, an automatically generated
<code><limits></code>, a partially re-written valarray, a working
! stringbuf and stringstream (for basic types). For more information,
please check <a href="http://sources.redhat.com/libstdc++/">
libstdc++-2.90.5</a>.
Index: htdocs/releases.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/releases.html,v
retrieving revision 1.8
diff -c -2 -p -r1.8 releases.html
*** releases.html 2000/10/08 17:37:21 1.8
--- releases.html 2000/10/15 15:39:25
*************** number is maintained.</p>
*** 48,52 ****
<p>If you have evidence for a missing release date, please send it in.
! Numbers in parens are EGCS release numbers. </p>
<table border=1 cellspacing=0 cellpadding=5>
--- 48,52 ----
<p>If you have evidence for a missing release date, please send it in.
! Numbers in parentheses are EGCS release numbers. </p>
<table border=1 cellspacing=0 cellpadding=5>
Index: htdocs/egcs-1.0/egcs-1.0.2.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/egcs-1.0/egcs-1.0.2.html,v
retrieving revision 1.10
diff -c -2 -p -r1.10 egcs-1.0.2.html
*** egcs-1.0.2.html 1999/11/23 00:12:40 1.10
--- egcs-1.0.2.html 2000/10/15 15:39:25
*************** serious problems in EGCS 1.0.1.
*** 20,24 ****
<li> General improvements and fixes
<ul>
! <li> Memory comsumption significantly reduced, especially for templates
and inline functions.
<li> Fix various problems with glibc2.1.
--- 20,24 ----
<li> General improvements and fixes
<ul>
! <li> Memory consumption significantly reduced, especially for templates
and inline functions.
<li> Fix various problems with glibc2.1.
Index: htdocs/egcs-1.1/features.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/egcs-1.1/features.html,v
retrieving revision 1.11
diff -c -2 -p -r1.11 features.html
*** features.html 1999/09/04 15:16:25 1.11
--- features.html 2000/10/15 15:39:25
***************
*** 41,45 ****
<li> cpplib has been greatly improved and may be suitable for limited use.
<li> Memory footprint for the compiler has been significantly reduced
! for some pathalogical cases.
<li> The time to build EGCS has been improved for certain targets
(particularly the alpha and mips platforms).
--- 41,45 ----
<li> cpplib has been greatly improved and may be suitable for limited use.
<li> Memory footprint for the compiler has been significantly reduced
! for some pathological cases.
<li> The time to build EGCS has been improved for certain targets
(particularly the alpha and mips platforms).
***************
*** 52,56 ****
uses the Haifa scheduler.
<li> Alpha port has been tuned for the EV6 processor and has an
! optimized expanstion of memcpy/bzero. The Alpha port now uses
the Haifa scheduler.
<li> RS6000/PowerPC: EGCS 1.1 includes support for the Power64
--- 52,56 ----
uses the Haifa scheduler.
<li> Alpha port has been tuned for the EV6 processor and has an
! optimized expansion of memcpy/bzero. The Alpha port now uses
the Haifa scheduler.
<li> RS6000/PowerPC: EGCS 1.1 includes support for the Power64
Index: htdocs/egcs-1.1/news.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/egcs-1.1/news.html,v
retrieving revision 1.4
diff -c -2 -p -r1.4 news.html
*** news.html 1999/07/29 04:27:45 1.4
--- news.html 2000/10/15 15:39:25
*************** cpplib has been greatly improved. It is
*** 66,70 ****
Memory footprint for the compiler has been significantly reduced for certain
! pathalogical cases.
Build time improvements for targets which support lots of sched parameters
--- 66,70 ----
Memory footprint for the compiler has been significantly reduced for certain
! pathological cases.
Build time improvements for targets which support lots of sched parameters
Index: htdocs/egcs-1.1/schedule.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/egcs-1.1/schedule.html,v
retrieving revision 1.6
diff -c -2 -p -r1.6 schedule.html
*** schedule.html 1999/07/29 04:27:45 1.6
--- schedule.html 2000/10/15 15:39:25
*************** EGCS 1.1 branch</a>.
*** 30,34 ****
ready yet, but we are actively working on solidifying the testing plan.
! <p>The tenative schedule for the EGCS 1.1 release is:
<ul>
--- 30,34 ----
ready yet, but we are actively working on solidifying the testing plan.
! <p>The tentative schedule for the EGCS 1.1 release is:
<ul>
*************** EGCS 1.1 branch</a>.
*** 41,45 ****
<p> It is also possible some patches which have been submitted and are
accepted for EGCS 1.1 will not have been installed by this date due to
! EOQ committments for many of the Cygnus volunteers.
<p> After July 3, 1998, only bugfix submissions will be considered for
--- 41,45 ----
<p> It is also possible some patches which have been submitted and are
accepted for EGCS 1.1 will not have been installed by this date due to
! EOQ commitments for many of the Cygnus volunteers.
<p> After July 3, 1998, only bugfix submissions will be considered for
Index: htdocs/fsf-forms/disclaim.manual
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/fsf-forms/disclaim.manual,v
retrieving revision 1.1.1.1
diff -c -2 -p -r1.1.1.1 disclaim.manual
*** disclaim.manual 1998/02/13 23:29:38 1.1.1.1
--- disclaim.manual 2000/10/15 15:39:25
*************** worth our trying to assert a copyleft.)
*** 4,8 ****
I, <name of person>, hereby disclaim all copyright interest in my
! manual <manual> which does <one-line desription>.
I affirm that I have no other intellectual property interest
--- 4,8 ----
I, <name of person>, hereby disclaim all copyright interest in my
! manual <manual> which does <one-line description>.
I affirm that I have no other intellectual property interest
Index: htdocs/fsf-forms/disclaim.program
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/fsf-forms/disclaim.program,v
retrieving revision 1.1.1.1
diff -c -2 -p -r1.1.1.1 disclaim.program
*** disclaim.program 1998/02/13 23:29:38 1.1.1.1
--- disclaim.program 2000/10/15 15:39:26
*************** worth our trying to assert a copyleft.)
*** 4,8 ****
I, <name of person>, hereby disclaim all copyright interest in my
! program <program> which does <one-line desription>.
I affirm that I have no other intellectual property interest
--- 4,8 ----
I, <name of person>, hereby disclaim all copyright interest in my
! program <program> which does <one-line description>.
I affirm that I have no other intellectual property interest
Index: htdocs/gcc-2.95/caveats.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-2.95/caveats.html,v
retrieving revision 1.15
diff -c -2 -p -r1.15 caveats.html
*** caveats.html 2000/10/13 23:54:30 1.15
--- caveats.html 2000/10/15 15:39:26
***************
*** 11,15 ****
<li>GCC 2.95 will issue an error for invalid asm statements that had been
silently accepted by earlier versions of the compiler. This is particularly
! noticable when compiling older versions of the Linux kernel (2.0.xx).
Please refer to the <a href="../faq.html#asmclobber">FAQ</a> for more
information on this issue.
--- 11,15 ----
<li>GCC 2.95 will issue an error for invalid asm statements that had been
silently accepted by earlier versions of the compiler. This is particularly
! noticeable when compiling older versions of the Linux kernel (2.0.xx).
Please refer to the <a href="../faq.html#asmclobber">FAQ</a> for more
information on this issue.
Index: htdocs/gcc-2.95/gcc-2.95.1.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-2.95/gcc-2.95.1.html,v
retrieving revision 1.7
diff -c -2 -p -r1.7 gcc-2.95.1.html
*** gcc-2.95.1.html 2000/08/27 22:27:08 1.7
--- gcc-2.95.1.html 2000/10/15 15:39:26
*************** release.
*** 48,52 ****
<li> Fix various problems with 64bit code generation for the rs6000/ppc
port.
! <li> Fix codegen bug which cuased tetex to be mis-compiled on the x86
<li> Fix compiler abort in new cfg code exposed by x86 port.
<li> Fix out of range array reference in code convert flat
--- 48,52 ----
<li> Fix various problems with 64bit code generation for the rs6000/ppc
port.
! <li> Fix codegen bug which caused tetex to be mis-compiled on the x86
<li> Fix compiler abort in new cfg code exposed by x86 port.
<li> Fix out of range array reference in code convert flat
Index: htdocs/gcc-2.95/gcc-2.95.2.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-2.95/gcc-2.95.2.html,v
retrieving revision 1.7
diff -c -2 -p -r1.7 gcc-2.95.2.html
*** gcc-2.95.2.html 2000/08/27 22:27:08 1.7
--- gcc-2.95.2.html 2000/10/15 15:39:26
*************** old non-conforming code.
*** 26,30 ****
which violates the C/C++ standards, but those warnings are not ready for
widespread use at this time. Rather than wait for those warnings the GCC
! developers have choosen to disable -fstrict-aliasing by default for the
GCC 2.95.2 release.
--- 26,30 ----
which violates the C/C++ standards, but those warnings are not ready for
widespread use at this time. Rather than wait for those warnings the GCC
! developers have chosen to disable -fstrict-aliasing by default for the
GCC 2.95.2 release.
Index: htdocs/gcc-2.95/schedule.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-2.95/schedule.html,v
retrieving revision 1.10
diff -c -2 -p -r1.10 schedule.html
*** schedule.html 2000/10/07 18:23:13 1.10
--- schedule.html 2000/10/15 15:39:26
*************** we will not have to slip the schedule fu
*** 67,71 ****
(original critical bugfreeze date was June 15, 1999).
! <p> <li> <b>July 8, 1999. Tenative Release date</b>.
<p>July 8, 1999 is the updated target date for the actual release
(original date was July 1, 1999).
--- 67,71 ----
(original critical bugfreeze date was June 15, 1999).
! <p> <li> <b>July 8, 1999. Tentative Release date</b>.
<p>July 8, 1999 is the updated target date for the actual release
(original date was July 1, 1999).
Index: htdocs/gcc-3.0/criteria.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.0/criteria.html,v
retrieving revision 1.10
diff -c -2 -p -r1.10 criteria.html
*** criteria.html 2000/10/14 12:08:34 1.10
--- criteria.html 2000/10/15 15:39:26
*************** commitment doesn't necessarily mean fixi
*** 119,123 ****
example, if you are a manager for a company with GCC expertise you
could be the volunteer if you'll commit to donating your employee's
! efforst as necessary. The release manager, and the GCC development
team, will make reasonable efforts to assist these volunteers by
answering questions and reviewing patches as time permits.</p>
--- 119,123 ----
example, if you are a manager for a company with GCC expertise you
could be the volunteer if you'll commit to donating your employee's
! efforts as necessary. The release manager, and the GCC development
team, will make reasonable efforts to assist these volunteers by
answering questions and reviewing patches as time permits.</p>
*************** supported platforms. In particular, the
*** 171,175 ****
will be run using GCC 2.95.2 on each of the supported platforms; those
results can then be compared with the output from a release candidate.
! Becuase there have often been issues with generating PIC code, we will
test with <code>-fPIC</code> as well.</p>
--- 171,175 ----
will be run using GCC 2.95.2 on each of the supported platforms; those
results can then be compared with the output from a release candidate.
! Because there have often been issues with generating PIC code, we will
test with <code>-fPIC</code> as well.</p>
Index: htdocs/gcc-3.0/lapack-guide.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.0/lapack-guide.html,v
retrieving revision 1.2
diff -c -2 -p -r1.2 lapack-guide.html
*** lapack-guide.html 2000/05/10 11:57:51 1.2
--- lapack-guide.html 2000/10/15 15:39:26
*************** without specifying the <code>-femulate-c
*** 63,67 ****
using GCC 3.0 should not need that flag.</p>
! <p>On Alpha's it is necessary to add the flag <code>-mieee</code> to OPTS,
NOOPT and LOADOPTS.</p>
--- 63,67 ----
using GCC 3.0 should not need that flag.</p>
! <p>On Alphas it is necessary to add the flag <code>-mieee</code> to OPTS,
NOOPT and LOADOPTS.</p>
Index: htdocs/gcc-3.0/libgcc.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.0/libgcc.html,v
retrieving revision 1.2
diff -c -2 -p -r1.2 libgcc.html
*** libgcc.html 2000/10/07 18:23:13 1.2
--- libgcc.html 2000/10/15 15:39:26
*************** that message is paraphrased here:
*** 101,105 ****
<p>The GNU C library project needs to be made aware of these
! conclusions, as they may need to take actions that faciliate this
policy in new versions of the GNU C library.</p>
</body>
--- 101,105 ----
<p>The GNU C library project needs to be made aware of these
! conclusions, as they may need to take actions that facilitate this
policy in new versions of the GNU C library.</p>
</body>
Index: htdocs/news/announcement.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/news/announcement.html,v
retrieving revision 1.1
diff -c -2 -p -r1.1 announcement.html
*** announcement.html 2000/06/08 23:02:52 1.1
--- announcement.html 2000/10/15 15:39:26
*************** Why are we doing this? It's become incr
*** 27,31 ****
of hacking events that the FSF's needs for gcc2 are at odds with the
objectives of many in the community who have done lots of hacking and
! improvment over the years. GCC is part of the FSF's publicity for the
GNU project, as well as being the GNU system's compiler, so stability
is paramount for them. On the other hand, Cygnus, the Linux folks,
--- 27,31 ----
of hacking events that the FSF's needs for gcc2 are at odds with the
objectives of many in the community who have done lots of hacking and
! improvement over the years. GCC is part of the FSF's publicity for the
GNU project, as well as being the GNU system's compiler, so stability
is paramount for them. On the other hand, Cygnus, the Linux folks,
*************** will include some subset of the followin
*** 80,84 ****
live range splitting.
More features of IBM Haifa's instruction scheduling,
! including software pipelineing, and branch scheduling.
sibling call opts.
various new embedded targets.
--- 80,84 ----
live range splitting.
More features of IBM Haifa's instruction scheduling,
! including software pipelining, and branch scheduling.
sibling call opts.
various new embedded targets.
Index: htdocs/news/cfg.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/news/cfg.html,v
retrieving revision 1.2
diff -c -2 -p -r1.2 cfg.html
*** cfg.html 2000/01/10 02:27:15 1.2
--- cfg.html 2000/10/15 15:39:26
*************** optimization passes in the compiler.
*** 19,23 ****
<p>The rewrite consists of building and maintaining two primary data
! structures, basic blocks and conrol edges between basic blocks.
Each data structure contains information about the block/edge, pointers
to the other data structure and the ability to attach pass specific
--- 19,23 ----
<p>The rewrite consists of building and maintaining two primary data
! structures, basic blocks and control edges between basic blocks.
Each data structure contains information about the block/edge, pointers
to the other data structure and the ability to attach pass specific
Index: htdocs/news/null.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/news/null.html,v
retrieving revision 1.3
diff -c -2 -p -r1.3 null.html
*** null.html 2000/01/10 02:27:16 1.3
--- null.html 2000/10/15 15:39:26
*************** to have a non-null value.
*** 31,35 ****
<p>It is important to realize the compiler does not care what value is in
! the reigster, only whether or not the register is known to have a non-null
value.
--- 31,35 ----
<p>It is important to realize the compiler does not care what value is in
! the register, only whether or not the register is known to have a non-null
value.
Index: htdocs/news/sparc.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/news/sparc.html,v
retrieving revision 1.3
diff -c -2 -p -r1.3 sparc.html
*** sparc.html 2000/01/10 02:27:16 1.3
--- sparc.html 2000/10/15 15:39:26
*************** improve long term maintainability of the
*** 16,20 ****
<pre>
1) Improved instruction and delayed branch scheduling for operations
! on "long long" and double float quanties on 32-bit SPARC targets.
Simple example:
--- 16,20 ----
<pre>
1) Improved instruction and delayed branch scheduling for operations
! on "long long" and double float quantities on 32-bit SPARC targets.
Simple example:
*************** improve long term maintainability of the
*** 138,142 ****
backwards compatibility with older GCC versions), and 32bit.
! 4) Tremendously improved support for instruction level parallism on
UltraSPARC. Using some new pieces of infrastructure added to
the Haifa scheduler recently, the SPARC backend can now achieve
--- 138,142 ----
backwards compatibility with older GCC versions), and 32bit.
! 4) Tremendously improved support for instruction level parallelism on
UltraSPARC. Using some new pieces of infrastructure added to
the Haifa scheduler recently, the SPARC backend can now achieve
*************** improve long term maintainability of the
*** 144,148 ****
has ever been possible before.
! Common problems previosly were in cases where interlocking and
slotting rules of the UltraSPARC could not be accurately described
to the compiler. Here are a few examples:
--- 144,148 ----
has ever been possible before.
! Common problems previously were in cases where interlocking and
slotting rules of the UltraSPARC could not be accurately described
to the compiler. Here are a few examples:
*************** improve long term maintainability of the
*** 193,197 ****
Previously a single RTL pattern which generated multiple
instructions was used by the SPARC port to load label addresses
! when generating position-independant code. Now, jump tables are
output after the function and the label address loading sequence
is described fully in RTL for each sub-operation involved. This
--- 193,197 ----
Previously a single RTL pattern which generated multiple
instructions was used by the SPARC port to load label addresses
! when generating position-independent code. Now, jump tables are
output after the function and the label address loading sequence
is described fully in RTL for each sub-operation involved. This
Index: htdocs/news/unify.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/news/unify.html,v
retrieving revision 1.2
diff -c -2 -p -r1.2 unify.html
*** unify.html 2000/01/10 02:27:16 1.2
--- unify.html 2000/10/15 15:39:26
*************** through the function.
*** 24,28 ****
<p>The optimization works by building a set of expressions which are computed
in each basic block and which are safe to move to the start of the block
! in which they are computed (anticipatable exrpessions). The optimizer also
computes which expressions are killed by each basic block.
--- 24,28 ----
<p>The optimization works by building a set of expressions which are computed
in each basic block and which are safe to move to the start of the block
! in which they are computed (anticipatable expressions). The optimizer also
computes which expressions are killed by each basic block.
Index: htdocs/projects/bp/main.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/bp/main.html,v
retrieving revision 1.16
diff -c -2 -p -r1.16 main.html
*** main.html 2000/09/04 08:03:01 1.16
--- main.html 2000/10/15 15:39:27
*************** Fixes appear in 2.0h</p>
*** 639,644 ****
</ul>
! <p>100% of the test suite passes after fixing the bug listed above,
! and compliling with ``<code>gcc ... -fno-strict-aliasing</code>''.
A strict-aliasing bug for i586 and i686 caused two assertion failures
in <code>kpathsea</code>.</p>
--- 639,644 ----
</ul>
! <p>100% of the test suite passes after fixing the bug listed above
! and compiling with ``<code>gcc ... -fno-strict-aliasing</code>''.
A strict-aliasing bug for i586 and i686 caused two assertion failures
in <code>kpathsea</code>.</p>