Index: /trunk/src/gcc/NEWS
===================================================================
--- /trunk/src/gcc/NEWS	(revision 1462)
+++ /trunk/src/gcc/NEWS	(revision 1462)
@@ -0,0 +1,5296 @@
+This file contains information about GCC releases which has been generated
+automatically from the online release notes.  It covers releases of GCC
+(and the former EGCS project) since EGCS 1.0, on the line of development
+that led to GCC 3. For information on GCC 2.8.1 and older releases of GCC 2,
+see ONEWS.
+
+======================================================================
+http://gcc.gnu.org/gcc-3.3/index.html
+
+                           GCC 3.3 Release Series
+
+   February 24, 2004
+
+   The [1]GNU project and the GCC developers are pleased to announce the
+   release of GCC 3.3.3. This release was actually completed on February
+   14, but technical issues with the transition to new security measures
+   for protecting FSF servers required a delay in the announcement.
+
+   The GCC 3.3 release series includes numerous [2]new features,
+   improvements, bug fixes, and other changes, thanks to an [3]amazing
+   group of volunteers.
+
+Release History
+
+   GCC 3.3.3
+          February 14, 2004 ([4]changes)
+
+   GCC 3.3.2
+          October 16, 2003 ([5]changes)
+
+   GCC 3.3.1
+          August 8, 2003 ([6]changes)
+
+   GCC 3.3
+          May 14, 2003 ([7]changes)
+
+References and Acknowledgements
+
+   GCC used to stand for the GNU C Compiler, but since the compiler
+   supports several other languages aside from C, it now stands for the
+   GNU Compiler Collection.
+
+   A list of [8]successful builds is updated as new information becomes
+   available.
+
+   The GCC developers would like to thank the numerous people that have
+   contributed new features, improvements, bug fixes, and other changes
+   as well as test results to GCC. This [9]amazing group of volunteers is
+   what makes GCC successful.
+
+   For additional information about GCC please refer to the [10]GCC
+   project web site or contact the [11]GCC development mailing list.
+
+   To obtain GCC please use [12]our mirror sites, one of the [13]GNU
+   mirror sites, or [14]our CVS server.
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [15]gnu@gnu.org. There
+   are also [16]other ways to contact the FSF.
+
+   These pages are maintained by [17]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [18]GCC manuals. If that fails, the
+    [19]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [20]gcc@gnu.org or
+    [21]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2004-02-29 [22]Valid XHTML 1.0 
+
+References
+
+   1. http://www.gnu.org/
+   2. http://gcc.gnu.org/gcc-3.3/changes.html
+   3. http://gcc.gnu.org/onlinedocs/gcc/Contributors.html
+   4. http://gcc.gnu.org/gcc-3.3/changes.html#3.3.3
+   5. http://gcc.gnu.org/gcc-3.3/changes.html#3.3.2
+   6. http://gcc.gnu.org/gcc-3.3/changes.html#3.3.1
+   7. http://gcc.gnu.org/gcc-3.3/changes.html
+   8. http://gcc.gnu.org/gcc-3.3/buildstat.html
+   9. http://gcc.gnu.org/onlinedocs/gcc/Contributors.html
+  10. http://gcc.gnu.org/index.html
+  11. mailto:gcc@gcc.gnu.org
+  12. http://gcc.gnu.org/mirrors.html
+  13. http://www.gnu.org/order/ftp.html
+  14. http://gcc.gnu.org/cvs.html
+  15. mailto:gnu@gnu.org
+  16. http://www.gnu.org/home.html#ContactInfo
+  17. http://gcc.gnu.org/about.html
+  18. http://gcc.gnu.org/onlinedocs/
+  19. mailto:gcc-help@gcc.gnu.org
+  20. mailto:gcc@gnu.org
+  21. mailto:gcc@gcc.gnu.org
+  22. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/gcc-3.3/changes.html
+
+                           GCC 3.3 Release Series
+                      Changes, New Features, and Fixes
+
+   The latest release in the 3.3 release series is [1]GCC 3.3.3.
+
+Caveats
+
+     * The preprocessor no longer accepts multi-line string literals.
+       They were deprecated in 3.0, 3.1, and 3.2.
+     * The preprocessor no longer supports the -A- switch when appearing
+       alone. -A- followed by an assertion is still supported.
+     * Support for all the systems [2]obsoleted in GCC 3.1 has been
+       removed from GCC 3.3. See below for a [3]list of systems which are
+       obsoleted in this release.
+     * Checking for null format arguments has been decoupled from the
+       rest of the format checking mechanism. Programs which use the
+       format attribute may regain this functionality by using the new
+       [4]nonnull function attribute. Note that all functions for which
+       GCC has a built-in format attribute, an appropriate built-in
+       nonnull attribute is also applied.
+     * The DWARF (version 1) debugging format has been deprecated and
+       will be removed in a future version of GCC. Version 2 of the DWARF
+       debugging format will continue to be supported for the foreseeable
+       future.
+     * The C and Objective-C compilers no longer accept the "Naming
+       Types" extension (typedef foo = bar); it was already unavailable
+       in C++. Code which uses it will need to be changed to use the
+       "typeof" extension instead: typedef typeof(bar) foo. (We have
+       removed this extension without a period of deprecation because it
+       has caused the compiler to crash since version 3.0 and no one
+       noticed until very recently. Thus we conclude it is not in
+       widespread use.)
+     * The -traditional C compiler option has been removed. It was
+       deprecated in 3.1 and 3.2. (Traditional preprocessing remains
+       available.) The <varargs.h> header, used for writing variadic
+       functions in traditional C, still exists but will produce an error
+       message if used.
+     * GCC 3.3.1 automatically places zero-initialized variables in the
+       .bss section on some operating systems. Versions of GNU Emacs up
+       to (and including) 21.3 will not work correctly when using this
+       optimization; you can use -fno-zero-initialized-in-bss to disable
+       it.
+
+General Optimizer Improvements
+
+     * A new scheme for accurately describing processor pipelines, the
+       [5]DFA scheduler, has been added.
+     * Pavel Nejedly, Charles University Prague, has contributed new file
+       format used by the edge coverage profiler (-fprofile-arcs).
+       The new format is robust and diagnoses common mistakes where
+       profiles from different versions (or compilations) of the program
+       are combined resulting in nonsensical profiles and slow code to
+       produced with profile feedback. Additionally this format allows
+       extra data to be gathered. Currently, overall statistics are
+       produced helping optimizers to identify hot spots of a program
+       globally replacing the old intra-procedural scheme and resulting
+       in better code. Note that the gcov tool from older GCC versions
+       will not be able to parse the profiles generated by GCC 3.3 and
+       vice versa.
+     * Jan Hubicka, SuSE Labs, has contributed a new superblock formation
+       pass enabled using -ftracer. This pass simplifies the control flow
+       of functions allowing other optimizations to do better job.
+       He also contributed the function reordering pass
+       (-freorder-functions) to optimize function placement using profile
+       feedback.
+
+New Languages and Language specific improvements
+
+  C/ObjC/C++
+
+     * The preprocessor now accepts directives within macro arguments. It
+       processes them just as if they had not been within macro
+       arguments.
+     * The separate ISO and traditional preprocessors have been
+       completely removed. The front end handles either type of
+       preprocessed output if necessary.
+     * In C99 mode preprocessor arithmetic is done in the precision of
+       the target's intmax_t, as required by that standard.
+     * The preprocessor can now copy comments inside macros to the output
+       file when the macro is expanded. This feature, enabled using the
+       -CC option, is intended for use by applications which place
+       metadata or directives inside comments, such as lint.
+     * The method of constructing the list of directories to be searched
+       for header files has been revised. If a directory named by a -I
+       option is a standard system include directory, the option is
+       ignored to ensure that the default search order for system
+       directories and the special treatment of system header files are
+       not defeated.
+     * A few more [6]ISO C99 features now work correctly.
+     * A new function attribute, nonnull, has been added which allows
+       pointer arguments to functions to be specified as requiring a
+       non-null value. The compiler currently uses this information to
+       issue a warning when it detects a null value passed in such an
+       argument slot.
+     * A new type attribute, may_alias, has been added. Accesses to
+       objects with types with this attribute are not subjected to
+       type-based alias analysis, but are instead assumed to be able to
+       alias any other type of objects, just like the char type.
+
+  C++
+
+     * Type based alias analysis has been implemented for C++ aggregate
+       types.
+
+  Objective-C
+
+     * Generate an error if Objective-C objects are passed by value in
+       function and method calls.
+     * When -Wselector is used, check the whole list of selectors at the
+       end of compilation, and emit a warning if a @selector() is not
+       known.
+     * Define __NEXT_RUNTIME__ when compiling for the NeXT runtime.
+     * No longer need to include objc/objc-class.h to compile self calls
+       in class methods (NeXT runtime only).
+     * New -Wundeclared-selector option.
+     * Removed selector bloating which was causing object files to be 10%
+       bigger on average (GNU runtime only).
+     * Using at run time @protocol() objects has been fixed in certain
+       situations (GNU runtime only).
+     * Type checking has been fixed and improved in many situations
+       involving protocols.
+
+  Java
+
+     * The java.sql and javax.sql packages now implement the JDBC 3.0
+       (JDK 1.4) API.
+     * The JDK 1.4 assert facility has been implemented.
+     * The bytecode interpreter is now direct threaded and thus faster.
+
+  Fortran
+
+     * Fortran improvements are listed in [7]the Fortran documentation.
+
+  Ada
+
+     * Ada tasking now works with glibc 2.3.x threading libraries.
+
+New Targets and Target Specific Improvements
+
+     * The following changes have been made to the HP-PA port:
+          + The port now defaults to scheduling for the PA8000 series of
+            processors.
+          + Scheduling support for the PA7300 processor has been added.
+          + The 32-bit port now supports weak symbols under HP-UX 11.
+          + The handling of initializers and finalizers has been improved
+            under HP-UX 11. The 64-bit port no longer uses collect2.
+          + Dwarf2 EH support has been added to the 32-bit linux port.
+          + ABI fixes to correct the passing of small structures by
+            value.
+     * The SPARC, HP-PA, SH4, and x86/pentium ports have been converted
+       to use the DFA processor pipeline description.
+     * The following NetBSD configurations for the SuperH processor
+       family have been added:
+          + SH3, big-endian, sh-*-netbsdelf*
+          + SH3, little-endian, shle-*-netbsdelf*
+          + SH5, SHmedia, big-endian, 32-bit default, sh5-*-netbsd*
+          + SH5, SHmedia, little-endian, 32-bit default, sh5le-*-netbsd*
+          + SH5, SHmedia, big-endian, 64-bit default, sh64-*-netbsd*
+          + SH5, SHmedia, little-endian, 64-bit default, sh64le-*-netbsd*
+     * The following changes have been made to the IA-32/x86-64 port:
+          + SSE2 and 3dNOW! intrinsics are now supported.
+          + Support for thread local storage has been added to the IA-32
+            and x86-64 ports.
+          + The x86-64 port has been significantly improved.
+     * The following changes have been made to the MIPS port:
+          + All configurations now accept the -mabi switch. Note that you
+            will need appropriate multilibs for this option to work
+            properly.
+          + ELF configurations will always pass an ABI flag to the
+            assembler, except when the MIPS EABI is selected.
+          + -mabi=64 no longer selects MIPS IV code.
+          + The -mcpu option, which was deprecated in 3.1 and 3.2, has
+            been removed from this release.
+          + -march now changes the core ISA level. In previous releases,
+            it would change the use of processor-specific extensions, but
+            would leave the core ISA unchanged. For example, mips64-elf
+            -march=r8000 will now generate MIPS IV code.
+          + Under most configurations, -mipsN now acts as a synonym for
+            -march.
+          + There are some new preprocessor macros to describe the -march
+            and -mtune settings. See the documentation of those options
+            for details.
+          + Support for the NEC VR-Series processors has been added. This
+            includes the 54xx, 5500, and 41xx series.
+          + Support for the Sandcraft sr71k processor has been added.
+     * The following changes have been made to the S/390 port:
+          + Support to build the Java runtime libraries has been added.
+            Java is now enabled by default on s390-*-linux* and
+            s390x-*-linux* targets.
+          + Multilib support for the s390x-*-linux* target has been
+            added; this allows to build 31-bit binaries using the -m31
+            option.
+          + Support for thread local storage has been added.
+          + Inline assembler code may now use the 'Q' constraint to
+            specify memory operands without index register.
+          + Various platform-specific performance improvements have been
+            implemented; in particular, the compiler now uses the BRANCH
+            ON COUNT family of instructions and makes more frequent use
+            of the TEST UNDER MASK family of instructions.
+     * The following changes have been made to the PowerPC port:
+          + Support for IBM Power4 processor added.
+          + Support for Motorola e500 SPE added.
+          + Support for AIX 5.2 added.
+          + Function and Data sections now supported on AIX.
+          + Sibcall optimizations added.
+     * The support for H8 Tiny is added to the H8/300 port with -mn.
+
+Obsolete Systems
+
+   Support for a number of older systems has been declared obsolete in
+   GCC 3.3. Unless there is activity to revive them, the next release of
+   GCC will have their sources permanently removed.
+
+   All configurations of the following processor architectures have been
+   declared obsolete:
+     * Matsushita MN10200, mn10200-*-*
+     * Motorola 88000, m88k-*-*
+     * IBM ROMP, romp-*-*
+
+   Also, some individual systems have been obsoleted:
+     * Alpha
+          + Interix, alpha*-*-interix*
+          + Linux libc1, alpha*-*-linux*libc1*
+          + Linux ECOFF, alpha*-*-linux*ecoff*
+     * ARM
+          + Generic a.out, arm*-*-aout*
+          + Conix, arm*-*-conix*
+          + "Old ABI," arm*-*-oabi
+          + StrongARM/COFF, strongarm-*-coff*
+     * HPPA (PA-RISC)
+          + Generic OSF, hppa1.0-*-osf*
+          + Generic BSD, hppa1.0-*-bsd*
+          + HP/UX versions 7, 8, and 9, hppa1.[01]-*-hpux[789]*
+          + HiUX, hppa*-*-hiux*
+          + Mach Lites, hppa*-*-lites*
+     * Intel 386 family
+          + Windows NT 3.x, i?86-*-win32
+     * MC68000 family
+          + HP systems, m68000-hp-bsd* and m68k-hp-bsd*
+          + Sun systems, m68000-sun-sunos*, m68k-sun-sunos*, and
+            m68k-sun-mach*
+          + AT&T systems, m68000-att-sysv*
+          + Atari systems, m68k-atari-sysv*
+          + Motorola systems, m68k-motorola-sysv*
+          + NCR systems, m68k-ncr-sysv*
+          + Plexus systems, m68k-plexus-sysv*
+          + Commodore systems, m68k-cbm-sysv*
+          + Citicorp TTI, m68k-tti-*
+          + Unos, m68k-crds-unos*
+          + Concurrent RTU, m68k-ccur-rtu*
+          + Linux a.out, m68k-*-linux*aout*
+          + Linux libc1, m68k-*-linux*libc1*
+          + pSOS, m68k-*-psos*
+     * MIPS
+          + Generic ECOFF, mips*-*-ecoff*
+          + SINIX, mips-sni-sysv4
+          + Orion RTEMS, mips64orion-*-rtems*
+     * National Semiconductor 32000
+          + OpenBSD, ns32k-*-openbsd*
+     * POWER (aka RS/6000) and PowerPC
+          + AIX versions 1, 2, and 3, rs6000-ibm-aix[123]*
+          + Bull BOSX, rs6000-bull-bosx
+          + Generic Mach, rs6000-*-mach*
+          + Generic SysV, powerpc*-*-sysv*
+          + Linux libc1, powerpc*-*-linux*libc1*
+     * Sun SPARC
+          + Generic a.out, sparc-*-aout*, sparclet-*-aout*,
+            sparclite-*-aout*, and sparc86x-*-aout*
+          + NetBSD a.out, sparc-*-netbsd*aout*
+          + Generic BSD, sparc-*-bsd*
+          + ChorusOS, sparc-*-chorusos*
+          + Linux a.out, sparc-*-linux*aout*
+          + Linux libc1, sparc-*-linux*libc1*
+          + LynxOS, sparc-*-lynxos*
+          + Solaris on HAL hardware, sparc-hal-solaris2*
+          + SunOS versions 3 and 4, sparc-*-sunos[34]*
+     * NEC V850
+          + RTEMS, v850-*-rtems*
+     * VAX
+          + VMS, vax-*-vms*
+
+Documentation improvements
+
+Other significant improvements
+
+     * Almost all front-end dependencies in the compiler have been
+       separated out into a set of language hooks. This should make
+       adding a new front end clearer and easier.
+     * One effect of removing the separate preprocessor is a small
+       increase in the robustness of the compiler in general, and the
+       maintainability of target descriptions. Previously target-specific
+       built-in macros and others, such as __FAST_MATH__, had to be
+       handled with so-called specs that were hard to maintain. Often
+       they would fail to behave properly when conflicting options were
+       supplied on the command line, and define macros in the user's
+       namespace even when strict ISO compliance was requested.
+       Integrating the preprocessor has cleanly solved these issues.
+     * The Makefile suite now supports redirection of make install by
+       means of the variable DESTDIR.
+     _________________________________________________________________
+
+GCC 3.3
+
+   Detailed release notes for the GCC 3.3 release follow.
+
+  Bug Fixes
+
+    bootstrap failures
+
+     * [8]10140 cross compiler build failures: missing __mempcpy (DUP:
+       [9]10198,[10]10338)
+
+    Internal compiler errors (multi-platform)
+
+     * [11]3581 large string causes segmentation fault in cc1
+     * [12]4382 __builtin_{set,long}jmp with -O3 can crash the compiler
+     * [13]5533 (c++) ICE when processing std::accumulate(begin, end,
+       init, invalid_op)
+     * [14]6387 -fpic -gdwarf-2 -g1 combination gives ICE in dwarf2out
+     * [15]6412 (c++) ICE in retrieve_specialization
+     * [16]6620 (c++) partial template specialization causes an ICE
+       (segmentation fault)
+     * [17]6663 (c++) ICE with attribute aligned
+     * [18]7068 ICE with incomplete types
+     * [19]7083 (c++) ICE using -gstabs with dodgy class derivation
+     * [20]7647 (c++) ICE when data member has the name of the enclosing
+       class
+     * [21]7675 ICE in fixup_var_refs_1
+     * [22]7718 'complex' template instantiation causes ICE
+     * [23]8116 (c++) ICE in member template function
+     * [24]8358 (ada) Ada compiler accesses freed memory, crashes
+     * [25]8511 (c++) ICE: (hopefully) reproducible cc1plus segmentation
+       fault
+     * [26]8564 (c++) ICE in find_function_data, in function.c
+     * [27]8660 (c++) template overloading ICE in tsubst_expr, in cp/pt.c
+     * [28]8766 (c++) ICE after failed initialization of static template
+       variable
+     * [29]8803 ICE in instantiate_virtual_regs_1, in function.c
+     * [30]8846 (c++) ICE after diagnostic if fr_FR@euro locale is set
+     * [31]8906 (c++) ICE (Segmentation fault) when parsing nested-class
+       definition
+     * [32]9216 (c++) ICE on missing template parameter
+     * [33]9261 (c++) ICE in arg_assoc, in cp/decl2.c
+     * [34]9263 (fortran) ICE caused by invalid PARAMETER in implied DO
+       loop
+     * [35]9429 (c++) ICE in template instantiation with a pointered new
+       operator
+     * [36]9516 Internal error when using a big array
+     * [37]9600 (c++) ICE with typedefs in template class
+     * [38]9629 (c++) virtual inheritance segfault
+     * [39]9672 (c++) ICE: Error reporting routines re-entered
+     * [40]9749 (c++) ICE in write_expression on invalid function
+       prototype
+     * [41]9794 (fortran) ICE: floating point exception during constant
+       folding
+     * [42]9829 (c++) Missing colon in nested namespace usage causes ICE
+     * [43]9916 (c++) ICE with noreturn function in ?: statement
+     * [44]9936 ICE with local function and variable-length 2d array
+     * [45]10262 (c++) cc1plus crashes with large generated code
+     * [46]10278 (c++) ICE in parser for invalid code
+     * [47]10446 (c++) ICE on definition of nonexistent member function
+       of nested class in a class template
+     * [48]10451 (c++) ICE in grokdeclarator on spurious mutable
+       declaration
+     * [49]10506 (c++) ICE in build_new at cp/init.c with
+       -fkeep-inline-functions and multiple inheritance
+     * [50]10549 (c++) ICE in store_bit_field on bitfields that exceed
+       the precision of the declared type
+
+    Optimization bugs
+
+     * [51]2001 Inordinately long compile times in reload CSE regs
+     * [52]2391 Exponential compilation time explosion in combine
+     * [53]2960 Duplicate loop conditions even with -Os
+     * [54]4046 redundant conditional branch
+     * [55]6405 Loop-unrolling related performance regressions
+     * [56]6798 very long compile time with large case-statement
+     * [57]6871 const objects shouldn't be moved to .bss
+     * [58]6909 problem w/ -Os on modified loop-2c.c test case
+     * [59]7189 gcc -O2 -Wall does not print ``control reaches end of
+       non-void function'' warning
+     * [60]7642 optimization problem with signbit()
+     * [61]8634 incorrect code for inlining of memcpy under -O2
+     * [62]8750 Cygwin prolog generation erroneously emitting __alloca as
+       regular function call
+
+    C front end
+
+     * [63]2161 long if-else cascade overflows parser stack
+     * [64]4319 short accepted on typedef'd char
+     * [65]8602 incorrect line numbers in warning messages when using
+       inline functions
+     * [66]9177 -fdump-translation-unit: C front end deletes
+       function_decl AST nodes and breaks debugging dumps
+     * [67]9853 miscompilation of non-constant structure initializer
+
+    c++ compiler and library
+
+     * [68]45 legal template specialization code is rejected (DUP:
+       [69]3784)
+     * [70]764 lookup failure: friend operator and dereferencing a
+       pointer and templates (DUP: [71]5116)
+     * [72]2862 gcc accepts invalid explicit instantiation syntax (DUP:
+       2863)
+     * [73]3663 G++ doesn't check access control during template
+       instantiation
+     * [74]3797 gcc fails to emit explicit specialization of a template
+       member
+     * [75]3948 Two destructors are called when no copy destructor is
+       defined (ABI change)
+     * [76]4137 Conversion operator within template is not accepted
+     * [77]4361 bogus ambiguity taking the address of a member template
+     * [78]4802 g++ accepts illegal template code (access to private
+       member; DUP: [79]5837)
+     * [80]4803 inline function is used but never defined, and g++ does
+       not object
+     * [81]5094 Partial specialization cannot be friend?
+     * [82]5730 complex<double>::norm() -- huge slowdown from
+       egcs-2.91.66
+     * [83]6713 Regression wrt 3.0.4: g++ -O2 leads to seg fault at run
+       time
+     * [84]7015 certain __asm__ constructs rejected
+     * [85]7086 compile time regression (quadratic behavior in
+       fixup_var_refs)
+     * [86]7099 G++ doesn't set the noreturn attribute on std::exit and
+       std::abort
+     * [87]7247 copy constructor missing when inlining enabled (invalid
+       optimization?)
+     * [88]7441 string array initialization compilation time regression
+       from seconds to minutes
+     * [89]7768 __PRETTY_FUNCTION__ for template destructor is wrong
+     * [90]7804 bad printing of floating point constant in warning
+       message
+     * [91]8099 Friend classes and template specializations
+     * [92]8117 member function pointers and multiple inheritance
+     * [93]8205 using declaration and multiple inheritance
+     * [94]8645 unnecessary non-zero checks in stl_tree.h
+     * [95]8724 explicit destructor call for incomplete class allowed
+     * [96]8805 compile time regression with many member variables
+     * [97]8691 -O3 and -fno-implicit-templates are incompatible
+     * [98]8700 unhelpful error message for binding temp to reference
+     * [99]8724 explicit destructor call for incomplete class allowed
+     * [100]8949 numeric_limits<>::denorm_min() and is_iec559 problems
+     * [101]9016 Failure to consistently constant fold "constant" C++
+       objects
+     * [102]9053 g++ confused about ambiguity of overloaded function
+       templates
+     * [103]9152 undefined virtual thunks
+     * [104]9182 basic_filebuf<> does not report errors in codecvt<>::out
+     * [105]9297 data corruption due to codegen bug (when copying.)
+     * [106]9318 i/ostream::operator>>/<<(streambuf*) broken
+     * [107]9320 Incorrect usage of traits_type::int_type in
+       stdio_filebuf
+     * [108]9400 bogus -Wshadow warning: shadowed declaration of this in
+       local classes
+     * [109]9424 i/ostream::operator>>/<<(streambuf*) drops characters
+     * [110]9425 filebuf::pbackfail broken (DUP: [111]9439)
+     * [112]9474 GCC freezes in compiling a weird code mixing <iostream>
+       and <iostream.h>
+     * [113]9548 Incorrect results from setf(ios::fixed) and
+       precision(-1) [114][DR 231]
+     * [115]9555 ostream inserters fail to set badbit on exception
+     * [116]9561 ostream inserters rethrow exception of wrong type
+     * [117]9563 ostream::sentry returns true after a failed preparation
+     * [118]9582 one-definition rule violation in std::allocator
+     * [119]9622 __PRETTY_FUNCTION__ incorrect in template destructors
+     * [120]9683 bug in initialization chains for static const variables
+       from template classes
+     * [121]9791 -Woverloaded-virtual reports hiding of destructor
+     * [122]9817 collate::compare doesn't handle nul characters
+     * [123]9825 filebuf::sputbackc breaks sbumpc
+     * [124]9826 operator>>(basic_istream, basic_string) fails to compile
+       with custom traits
+     * [125]9924 Multiple using statements for builtin functions not
+       allowed
+     * [126]9946 destructor is not called for temporary object
+     * [127]9964 filebuf::close() sometimes fails to close file
+     * [128]9988 filebuf::overflow writes EOF to file
+     * [129]10033 optimization breaks polymorphic references w/ typeid
+       operator
+     * [130]10097 filebuf::underflow drops characters
+     * [131]10132 filebuf destructor can throw exceptions
+     * [132]10180 gcc fails to warn about non-inlined function
+     * [133]10199 method parametrized by template does not work
+       everywhere
+     * [134]10300 use of array-new (nothrow) in segfaults on NULL return
+     * [135]10427 Stack corruption with variable-length automatic arrays
+       and virtual destructors
+     * [136]10503 Compilation never stops in fixed_type_or_null
+
+    Objective-C
+
+     * [137]5956 selectors aren't matched properly when added to the
+       selector table
+
+    Fortran compiler and library
+
+     * [138]1832 list directed i/o overflow hangs, -fbounds-check doesn't
+       detect
+     * [139]3924 g77 generates code that is rejected by GAS if COFF debug
+       info requested
+     * [140]5634 doc: explain that configure --prefix=~/... does not work
+     * [141]6367 multiple repeat counts confuse namelist read into array
+     * [142]6491 Logical operations error on logicals when using
+       -fugly-logint
+     * [143]6742 Generation of C++ Prototype for FORTRAN and extern "C"
+     * [144]7113 Failure of g77.f-torture/execute/f90-intrinsic-bit.f -Os
+       on irix6.5
+     * [145]7236 OPEN(...,RECL=nnn,...) without ACCESS='DIRECT' should
+       assume a direct access file
+     * [146]7278 g77 "bug"; the executable misbehaves (with -O2
+       -fno-automatic)
+     * [147]7384 DATE_AND_TIME milliseconds field inactive on Windows
+     * [148]7388 Incorrect output with 0-based array of characters
+     * [149]8587 Double complex zero ** double precision number -> NaN
+       instead of zero
+     * [150]9038 -ffixed-line-length-none -x f77-cpp-input gives:
+       Warning: unknown register name line-length-none
+     * [151]10197 Direct access files not unformatted by default
+
+    Java compiler and library
+
+     * [152]6005 gcj fails to build rhug on alpha
+     * [153]6389 System.getProperty("") should always throw an
+       IllegalArgumentException
+     * [154]6576 java.util.ResourceBundle.getResource ignores locale
+     * [155]6652 new java.io.File("").getCanonicalFile() throws exception
+     * [156]7060 getMethod() doesn't search super interface
+     * [157]7073 bytecode interpreter gives wrong answer for interface
+       getSuperclass()
+     * [158]7180 possible bug in
+       javax.naming.spi.NamingManager.getPlusPath()
+     * [159]7416 java.security startup refs "GNU libgcj.security"
+     * [160]7570 Runtime.exec with null envp: child doesn't inherit
+       parent env (DUP: [161]7578)
+     * [162]7611 Internal error while compiling libjava with -O
+     * [163]7709 NullPointerException in _Jv_ResolvePoolEntry
+     * [164]7766 ZipInputStream.available returns 0 immediately after
+       construction
+     * [165]7785 Calendar.getTimeInMillis/setTimeInMillis should be
+       public
+     * [166]7786 TimeZone.getDSTSavings() from JDK1.4 not implemented
+     * [167]8142 '$' in class names vs. dlopen 'dynamic string tokens'
+     * [168]8234 ZipInputStream chokes when InputStream.read() returns
+       small chunks
+     * [169]8415 reflection bug: exception info for Method
+     * [170]8481 java.Random.nextInt(int) may return negative
+     * [171]8593 Error reading GZIPped files with BufferedReader
+     * [172]8759 java.beans.Introspector has no flushCaches() or
+       flushFromCaches() methods
+     * [173]8997 spin() calls Thread.sleep
+     * [174]9253 on win32, java.io.File.listFiles("C:\\") returns pwd
+       instead of the root content of C:
+     * [175]9254 java::lang::Object::wait(), threads-win32.cc returns
+       wrong return codes
+     * [176]9271 Severe bias in java.security.SecureRandom
+
+    Ada compiler and library
+
+     * [177]6767 make gnatlib-shared fails on -laddr2line
+     * [178]9911 gnatmake fails to link when GCC configured with
+       --with-sjlj-exceptions=yes
+     * [179]10020 Can't bootstrap gcc on AIX with Ada enabled
+     * [180]10546 Ada tasking not working on Red Hat 9
+
+    preprocessor
+
+     * [181]7029 preprocessor should ignore #warning with -M
+
+    ARM-specific
+
+     * [182]2903 [arm] Optimization bug with long long arithmetic
+     * [183]7873 arm-linux-gcc fails when assigning address to a bit
+       field
+
+    FreeBSD-specific
+
+     * [184]7680 float functions undefined in math.h/cmath with #define
+       _XOPEN_SOURCE
+
+    HP-UX or HP-PA-specific
+
+     * [185]8705 [HP-PA] ICE in emit_move_insn_1, in expr.c
+     * [186]9986 [HP-UX] Incorrect transformation of fputs_unlocked to
+       fputc_unlocked
+     * [187]10056 [HP-PA] ICE at -O2 when building c++ code from doxygen
+
+    m68hc11-specific
+
+     * [188]6744 Bad assembler code generated: reference to pseudo
+       register z
+     * [189]7361 Internal compiler error in reload_cse_simplify_operands,
+       in reload1.c
+
+    MIPS-specific
+
+     * [190]9496 [mips-linux] bug in optimizer?
+
+    PowerPC-specific
+
+     * [191]7067 -Os with -mcpu=powerpc optimizes for speed (?) instead
+       of space
+     * [192]8480 reload ICEs for LAPACK code on powerpc64-linux
+     * [193]8784 [AIX] Internal compiler error in simplify_gen_subreg
+     * [194]10315 [powerpc] ICE: in extract_insn, in recog.c
+
+    SPARC-specific
+
+     * [195]10267 (documentation) Wrong build instructions for
+       *-*-solaris2*
+
+    x86-specific (Intel/AMD)
+
+     * [196]7916 ICE in instantiate_virtual_register_1
+     * [197]7926 (c++) i486 instructions in header files make c++
+       programs crash on i386
+     * [198]8555 ICE in gen_split_1231
+     * [199]8994 ICE with -O -march=pentium4
+     * [200]9426 ICE with -fssa -funroll-loops -fprofile-arcs
+     * [201]9806 ICE in inline assembly with -fPIC flag
+     * [202]10077 gcc -msse2 generates movd to move dwords between xmm
+       regs
+     * [203]10233 64-bit comparison only comparing bottom 32-bits
+     * [204]10286 type-punning doesn't work with __m64 and -O
+     * [205]10308 [x86] ICE with -O -fgcse or -O2
+     _________________________________________________________________
+
+GCC 3.3.1
+
+  Bug Fixes
+
+   This section lists the problem reports (PRs) from GCC's bug tracking
+   system that are known to be fixed in the 3.3.1 release. This list
+   might not be complete (that is, it is possible that some PRs that have
+   been fixed are not listed here).
+
+    Bootstrap failures
+
+     * [206]11272 [Solaris] make bootstrap fails while building libstdc++
+
+    Internal compiler errors (multi-platform)
+
+     * [207]5754 ICE on invalid nested template class
+     * [208]6597 ICE in set_mem_alias_set compiling Qt with -O2 on ia64
+       and --enable-checking
+     * [209]6949 (c++) ICE in tsubst_decl, in cp/pt.c
+     * [210]7053 (c++) ICE when declaring a function already defined as a
+       friend method of a template class
+     * [211]8164 (c++) ICE when using different const expressions as
+       template parameter
+     * [212]8384 (c++) ICE in is_base_type, in dwarf2out.c
+     * [213]9559 (c++) ICE with invalid initialization of a static const
+     * [214]9649 (c++) ICE in finish_member_declaration, in
+       cp/semantics.c when redeclaring a static member variable
+     * [215]9864 (fortran) ICE in add_abstract_origin_attribute, in
+       dwarfout.c with -g -O -finline-functions
+     * [216]10432 (c++) ICE in poplevel, in cp/decl.c
+     * [217]10475 ICE in subreg_highpart_offset for code with long long
+     * [218]10635 (c++) ICE when dereferencing an incomplete type casted
+       from a void pointer
+     * [219]10661 (c++) ICE in instantiate_decl, in cp/pt.c while
+       instantiating static member variables
+     * [220]10700 ICE in copy_to_mode_reg on 64-bit targets
+     * [221]10712 (c++) ICE in constructor_name_full, in cp/decl2.c
+     * [222]10796 (c++) ICE when defining an enum with two values: -1 and
+       MAX_INT_64BIT
+     * [223]10890 ICE in merge_assigned_reloads building Linux 2.4.2x
+       sched.c
+     * [224]10939 (c++) ICE with template code
+     * [225]10956 (c++) ICE when specializing a template member function
+       of a template class, in tsubst, in cp/pt.c
+     * [226]11041 (c++) ICE: const myclass &x = *x; (when operator*()
+       defined)
+     * [227]11059 (c++) ICE with empty union
+     * [228]11083 (c++) ICE in commit_one_edge_insertion, in cfgrtl.c
+       with -O2 -fnon-call-exceptions
+     * [229]11105 (c++) ICE in mangle_conv_op_name_for_type
+     * [230]11149 (c++) ICE on error when instantiation with call
+       function of a base type
+     * [231]11228 (c++) ICE on new-expression using array operator new
+       and default-initialization
+     * [232]11282 (c++) Infinite memory usage after syntax error
+     * [233]11301 (fortran) ICE with -fno-globals
+     * [234]11308 (c++) ICE when using an enum type name as if it were a
+       class or namespace
+     * [235]11473 (c++) ICE with -gstabs when empty struct inherits from
+       an empty struct
+     * [236]11503 (c++) ICE when instantiating template with ADDR_EXPR
+     * [237]11513 (c++) ICE in push_template_decl_real, in cp/pt.c:
+       template member functions
+
+    Optimization bugs
+
+     * [238]11198 -O2 -frename-registers generates wrong code (aliasing
+       problem)
+     * [239]11304 Wrong code production with -fomit-frame-pointer
+     * [240]11381 volatile memory access optimized away
+     * [241]11536 [strength-reduce] -O2 optimization produces wrong code
+     * [242]11557 constant folding bug generates wrong code
+
+    C front end
+
+     * [243]5897 No warning for statement after return
+     * [244]11279 DWARF-2 output mishandles large enums
+
+    Preprocessor bugs
+
+     * [245]11022 no warning for non-compatible macro redefinition
+
+    C++ compiler and library
+
+     * [246]2330 static_cast<>() to a private base is allowed
+     * [247]5388 Incorrect message "operands to ?: have different types"
+     * [248]5390 Libiberty fails to demangle multi-digit template
+       parameters
+     * [249]7877 Incorrect parameter passing to specializations of member
+       function templates
+     * [250]9393 Anonymous namespaces and compiling the same file twice
+     * [251]10032 -pedantic converts some errors to warnings
+     * [252]10468 const typeof(x) is non-const, but only in templates
+     * [253]10527 confused error message with "new int()" parameter
+       initializer
+     * [254]10679 parameter MIN_INLINE_INSNS is not honored
+     * [255]10682 gcc chokes on a typedef for an enum inside a class
+       template
+     * [256]10689 pow(std::complex(0),1/3) returns (nan, nan) instead of
+       0.
+     * [257]10845 template member function (with nested template as
+       parameter) cannot be called anymore if another unrelated template
+       member function is defined
+     * [258]10849 Cannot define an out-of-class specialization of a
+       private nested template class
+     * [259]10888 Suppress -Winline warnings for system headers
+     * [260]10929 -Winline warns about functions for which no definition
+       is visible
+     * [261]10931 valid conversion static_cast<const unsigned
+       int&>(lvalue-of-type-int) is rejected
+     * [262]10940 Bad code with explicit specialization
+     * [263]10968 If member function implicitly instantiated, explicit
+       instantiation of class fails to instantiate it
+     * [264]10990 Cannot convert with dynamic_cast<> to a private base
+       class from within a member function
+     * [265]11039 Bad interaction between implicit typename deprecation
+       and friendship
+     * [266]11062 (libstdc++) avoid __attribute__ ((unused)); say
+       "__unused__" instead
+     * [267]11095 C++ iostream manipulator causes segfault when called
+       with negative argument
+     * [268]11098 g++ doesn't emit complete debugging information for
+       local variables in destructors
+     * [269]11137 Linux shared library constructors not called unless
+       there's one global object
+     * [270]11154 spurious ambiguity report for template class
+       specialization
+     * [271]11329 Compiler cannot find user defined implicit typecast
+     * [272]11332 Spurious error with casts in ?: expression
+     * [273]11431 static_cast behavior with subclasses when default
+       constructor available
+     * [274]11528 money_get facet does not accept "$.00" as valid
+     * [275]11546 Type lookup problems in out-of-line definition of a
+       class doubly nested from a template class
+     * [276]11567 C++ code containing templated member function with same
+       name as pure virtual member function results in linking failure
+     * [277]11645 Failure to deal with using and private inheritance
+
+    Java compiler and library
+
+     * [278]5179 Qualified static field access doesn't initialize its
+       class
+     * [279]8204 gcj -O2 to native reorders certain instructions
+       improperly
+     * [280]10838 java.io.ObjectInputStream syntax error
+     * [281]10886 The RMI registry that comes with GCJ does not work
+       correctly
+     * [282]11349 JNDI URL context factories not located correctly
+
+    x86-specific (Intel/AMD)
+
+     * [283]4823 ICE on inline assembly code
+     * [284]8878 miscompilation with -O and SSE
+     * [285]9815 (c++ library) atomicity.h - fails to compile with -O3
+       -masm=intel
+     * [286]10402 (inline assembly) [x86] ICE in merge_assigned_reloads,
+       in reload1.c
+     * [287]10504 ICE with SSE2 code and -O3 -mcpu=pentium4 -msse2
+     * [288]10673 ICE for x86-64 on freebsd libc vfprintf.c source
+     * [289]11044 [x86] out of range loop instructions for FP code on K6
+     * [290]11089 ICE: instantiate_virtual_regs_lossage while using SSE
+       built-ins
+     * [291]11420 [x86_64] gcc generates invalid asm code when "-O -fPIC"
+       is used
+
+    SPARC- or Solaris- specific
+
+     * [292]9362 solaris 'as' dies when fed .s and "-gstabs"
+     * [293]10142 [SPARC64] gcc produces wrong code when passing
+       structures by value
+     * [294]10663 New configure check aborts with Sun tools.
+     * [295]10835 combinatorial explosion in scheduler on HyperSPARC
+     * [296]10876 ICE in calculate_giv_inc when building KDE
+     * [297]10955 wrong code at -O3 for structure argument in context of
+       structure return
+     * [298]11018 -mcpu=ultrasparc busts tar-1.13.25
+     * [299]11556 [sparc64] ICE in gen_reg_rtx() while compiling 2.6.x
+       Linux kernel
+
+    ia64 specific
+
+     * [300]10907 gcc violates the ia64 ABI (GP must be preserved)
+     * [301]11320 scheduler bug (in machine depended reorganization pass)
+     * [302]11599 bug with conditional and __builtin_prefetch
+
+    PowerPC specific
+
+     * [303]9745 [powerpc] gcc mis-compiles libmcrypt (alias problem
+       during loop)
+     * [304]10871 error in rs6000_stack_info save_size computation
+     * [305]11440 gcc mis-compiles c++ code (libkhtml) with -O2,
+       -fno-gcse cures it
+
+    m68k-specific
+
+     * [306]7594 [m68k] ICE on legal code associated with simplify-rtx
+     * [307]10557 [m68k] ICE in subreg_offset_representable_p
+     * [308]11054 [m68k] ICE in reg_overlap_mentioned_p
+
+    ARM-specific
+
+     * [309]10834 [arm] GCC 3.3 still generates incorrect instructions
+       for functions with __attribute__ ((interrupt ("IRQ")))
+     * [310]10842 [arm] Clobbered link register is copied to pc under
+       certain circumstances
+     * [311]11052 [arm] noce_process_if_block() can lose REG_INC notes
+     * [312]11183 [arm] ICE in change_address_1 (3.3) / subreg_hard_regno
+       (3.4)
+
+    MIPS-specific
+
+     * [313]11084 ICE in propagate_one_insn, in flow.c
+
+    SH-specific
+
+     * [314]10331 can't compile c++ part of gcc cross compiler for sh-elf
+     * [315]10413 [SH] ICE in reload_cse_simplify_operands, in reload1.c
+     * [316]11096 i686-linux to sh-linux cross compiler fails to compile
+       C++ files
+
+    GNU/Linux (or Hurd?) specific
+
+     * [317]2873 Bogus fixinclude of stdio.h from glibc 2.2.3
+
+    UnixWare specific
+
+     * [318]3163 configure bug: gcc/aclocal.m4 mmap test fails on
+       UnixWare 7.1.1
+
+    Cygwin (or mingw) specific
+
+     * [319]5287 ICE with dllimport attribute
+     * [320]10148 [MingW/CygWin] Compiler dumps core
+
+    DJGPP specific
+
+     * [321]8787 GCC fails to emit .intel_syntax when invoked with
+       -masm=intel on DJGPP
+
+    Darwin (and MacOS X) specific
+
+     * [322]10900 trampolines crash
+
+    Documentation
+
+     * [323]1607 (c++) Format attributes on methods undocumented
+     * [324]4252 Invalid option `-fdump-translation-unit'
+     * [325]4490 Clarify restrictions on -m96bit-long-double,
+       -m128bit-long-double
+     * [326]10355 document an issue with regparm attribute on some
+       systems (e.g. Solaris)
+     * [327]10726 (fortran) Documentation for function "IDate Intrinsic
+       (Unix)" is wrong
+     * [328]10805 document bug in old version of Sun assembler
+     * [329]10815 warn against GNU binutils on AIX
+     * [330]10877 document need for newer binutils on i?86-*-linux-gnu
+     * [331]11280 Manual incorrect with respect to -freorder-blocks
+     * [332]11466 Document -mlittle-endian and its restrictions for the
+       sparc64 port
+
+    Testsuite bugs (compiler itself is not affected)
+
+     * [333]10737 newer bison causes g++.dg/parse/crash2.C to incorrectly
+       report failure
+     * [334]10810 gcc-3.3 fails make check: buffer overrun in
+       test_demangle.c
+     _________________________________________________________________
+
+GCC 3.3.2
+
+  Bug Fixes
+
+   This section lists the problem reports (PRs) from [335]GCC's bug
+   tracking system that are known to be fixed in the 3.3.2 release. This
+   list might not be complete (that is, it is possible that some PRs that
+   have been fixed are not listed here).
+
+    Bootstrap failures and problems
+
+     * [336]8336 [SCO5] bootstrap config still tries to use COFF options
+     * [337]9330 [alpha-osf] Bootstrap failure on Compaq Tru64 with
+       --enable-threads=posix
+     * [338]9631 [hppa64-linux] gcc-3.3 fails to bootstrap
+     * [339]9877 fixincludes makes a bad sys/byteorder.h on svr5
+       (UnixWare 7.1.1)
+     * [340]11687 xstormy16-elf build fails in libf2c
+     * [341]12263 [SGI IRIX] bootstrap fails during compile of
+       libf2c/libI77/backspace.c
+     * [342]12490 buffer overflow in scan-decls.c (during Solaris 9
+       fix-header processing)
+
+    Internal compiler errors (multi-platform)
+
+     * [343]7277 Casting integers to vector types causes ICE
+     * [344]7939 (c++) ICE on invalid function template specialization
+     * [345]11063 (c++) ICE on parsing initialization list of const array
+       member
+     * [346]11207 ICE with negative index in array element designator
+     * [347]11522 (fortran) g77 dwarf-2 ICE in
+       add_abstract_origin_attribute
+     * [348]11595 (c++) ICE on duplicate label definition
+     * [349]11646 (c++) ICE in commit_one_edge_insertion with
+       -fnon-call-exceptions -fgcse -O
+     * [350]11665 ICE in struct initializer when taking address
+     * [351]11852 (c++) ICE with bad struct initializer.
+     * [352]11878 (c++) ICE in cp_expr_size
+     * [353]11883 ICE with any -O on mercury-generated C code
+     * [354]11991 (c++) ICE in cxx_incomplete_type_diagnostic, in
+       cp/typeck2.c when applying typeid operator to template template
+       parameter
+     * [355]12146 ICE in lookup_template_function, in cp/pt.c
+     * [356]12215 ICE in make_label_edge with -fnon-call-exceptions
+       -fno-gcse -O2
+     * [357]12369 (c++) ICE with templates and friends
+     * [358]12446 ICE in emit_move_insn on complicated array reference
+     * [359]12510 ICE in final_scan_insn
+     * [360]12544 ICE with large parameters used in nested functions
+
+    C and optimization bugs
+
+     * [361]9862 spurious warnings with -W -finline-functions
+     * [362]10962 lookup_field is a linear search on a linked list (can
+       be slow if large struct)
+     * [363]11370 -Wunreachable-code gives false complaints
+     * [364]11637 invalid assembly with -fnon-call-exceptions
+     * [365]11885 Problem with bitfields in packed structs
+     * [366]12082 Inappropriate unreachable code warnings
+     * [367]12180 Inline optimization fails for variadic function
+     * [368]12340 loop unroller + gcse produces wrong code
+
+    C++ compiler and library
+
+     * [369]3907 nested template parameter collides with member name
+     * [370]5293 confusing message when binding a temporary to a
+       reference
+     * [371]5296 [DR115] Pointers to functions and to template functions
+       behave differently in deduction
+     * [372]7939 ICE on function template specialization
+     * [373]8656 Unable to assign function with __attribute__ and pointer
+       return type to an appropriate variable
+     * [374]10147 Confusing error message for invalid template function
+       argument
+     * [375]11400 std::search_n() makes assumptions about Size parameter
+     * [376]11409 issues with using declarations, overloading, and
+       built-in functions
+     * [377]11740 ctype<wchar_t>::do_is(mask, wchar_t) doesn't handle
+       multiple bits in mask
+     * [378]11786 operator() call on variable in other namespace not
+       recognized
+     * [379]11867 static_cast ignores ambiguity
+     * [380]11928 bug with conversion operators that are typedefs
+     * [381]12114 Uninitialized memory accessed in dtor
+     * [382]12163 static_cast + explicit constructor regression
+     * [383]12181 Wrong code with comma operator and c++
+     * [384]12236 regparm and fastcall messes up parameters
+     * [385]12266 incorrect instantiation of unneeded template during
+       overload resolution
+     * [386]12296 istream::peek() doesn't set eofbit
+     * [387]12298 [sjlj exceptions] Stack unwind destroys
+       not-yet-constructed object
+     * [388]12369 ICE with templates and friends
+     * [389]12337 apparently infinite loop in g++
+     * [390]12344 stdcall attribute ignored if function returns a pointer
+     * [391]12451 missing(late) class forward declaration in cxxabi.h
+     * [392]12486 g++ accepts invalid use of a qualified name
+
+    x86 specific (Intel/AMD)
+
+     * [393]8869 [x86 MMX] ICE with const variable optimization and MMX
+       builtins
+     * [394]9786 ICE in fixup_abnormal_edges with -fnon-call-exceptions
+       -O2
+     * [395]11689 g++3.3 emits un-assembleable code for k6 architecture
+     * [396]12116 [k6] Invalid assembly output values with X-MAME code
+     * [397]12070 ICE converting between double and long double with
+       -msoft-float
+
+    ia64-specific
+
+     * [398]11184 [ia64 hpux] ICE on __builtin_apply building libobjc
+     * [399]11535 __builtin_return_address may not work on ia64
+     * [400]11693 [ia64] ICE in gen_nop_type
+     * [401]12224 [ia64] Thread-local storage doesn't work
+
+    PowerPC-specific
+
+     * [402]11087 [powerpc64-linux] GCC miscompiles raid1.c from linux
+       kernel
+     * [403]11319 loop miscompiled on ppc32
+     * [404]11949 ICE Compiler segfault with ffmpeg -maltivec code
+
+    SPARC-specific
+
+     * [405]11662 wrong code for expr. with cast to long long and
+       exclusive or
+     * [406]11965 invalid assembler code for a shift < 32 operation
+     * [407]12301 (c++) stack corruption when a returned expression
+       throws an exception
+
+    Alpha-specific
+
+     * [408]11717 [alpha-linux] unrecognizable insn compiling for.c of
+       kernel 2.4.22-pre8
+
+    HPUX-specific
+
+     * [409]11313 problem with #pragma weak and static inline functions
+     * [410]11712 __STDC_EXT__ not defined for C++ by default anymore?
+
+    Solaris specific
+
+     * [411]12166 Profiled programs crash if PROFDIR is set
+
+    Solaris-x86 specific
+
+     * [412]12101 i386 Solaris no longer works with GNU as?
+
+    Miscellaneous embedded target-specific bugs
+
+     * [413]10988 [m32r-elf] wrong blockmove code with -O3
+     * [414]11805 [h8300-unknown-coff] [H8300] ICE for simple code with
+       -O2
+     * [415]11902 [sh4] spec file improperly inserts rpath even when none
+       needed
+     * [416]11903 [sh4] -pthread fails to link due to error in spec file
+       on sh4
+     _________________________________________________________________
+
+GCC 3.3.3
+
+  Minor features
+
+   In addition to the bug fixes documented below, this release contains
+   few minor features such as:
+     * Support for --with-sysroot
+     * Support for automatic detection of executable stacks
+     * Support for SSE3 instructions
+     * Support for thread local storage debugging under GDB on S390
+
+  Bug Fixes
+
+   This section lists the problem reports (PRs) from [417]GCC's bug
+   tracking system that are known to be fixed in the 3.3.3 release. This
+   list might not be complete (that is, it is possible that some PRs that
+   have been fixed are not listed here).
+
+    Bootstrap failures and issues
+
+     * [418]11890 Building cross gcc-3.3.1 for sparc-sun-solaris2.6 fails
+     * [419]12399 boehm-gc fails (when building a cross compiler):
+       libtool unable to infer tagged configuration
+     * [420]13068 mklibgcc.in doesn't handle multi-level multilib
+       subdirectories properly
+
+    Internal compiler errors (multi-platform)
+
+     * [421]10060 ICE (stack overflow) on huge file (300k lines) due to
+       recursive behaviour of copy_rtx_if_shared, in emit_rtl.c
+     * [422]10555 (c++) ICE on undefined template argument
+     * [423]10706 (c++) ICE in mangle_class_name_for_template
+     * [424]11496 (fortran) error in flow_loops_find when -funroll-loops
+       active
+     * [425]11741 ICE in pre_insert_copy_insn, in gcse.c
+     * [426]12440 GCC crashes during compilation of quicktime4linux 2.0.0
+     * [427]12632 (fortran) -fbounds-check ICE
+     * [428]12712 (c++) ICE on short legit C++ code fragment with gcc
+       3.3.2
+     * [429]12726 (c++) ICE (segfault) on trivial code
+     * [430]12890 (c++) ICE on compilation of class with throwing method
+     * [431]12900 (c++) ICE in rtl_verify_flow_info_1
+     * [432]13060 (fortran) ICE in fixup_var_refs_1, in function.c on
+       correct code with -O2 -fno-force-mem
+     * [433]13289 (c++) ICE in regenerate_decl_from_template on recursive
+       template
+     * [434]13318 ICE: floating point exception in the loop optimizer
+     * [435]13392 (c++) ICE in convert_from_eh_region_ranges_1, in
+       except.c
+     * [436]13574 (c++) invalid array default initializer in class lets
+       gcc consume all memory and die
+     * [437]13475 ICE on SIMD variables with partial value initialization
+     * [438]13797 (c++) ICE on invalid template parameter
+     * [439]13824 (java) gcj SEGV with simple .java program
+
+    C and optimization bugs
+
+     * [440]8776 loop invariants are not removed (most likely)
+     * [441]10339 [sparc,ppc,ppc64] Invalid optimization: replacing
+       strncmp by memcmp
+     * [442]11350 undefined labels with -Os -fPIC
+     * [443]12826 Optimizer removes reference through volatile pointer
+     * [444]12500 stabs debug info: void no longer a predefined / builtin
+       type
+     * [445]12941 builtin-bitops-1.c miscompilation (latent bug)
+     * [446]12953 tree inliner bug (in inline_forbidden_p) and fix
+     * [447]13041 linux-2.6/sound/core/oss/rate.c miscompiled
+     * [448]13507 spurious printf format warning
+     * [449]13382 Type information for const pointer disappears during
+       optimization.
+     * [450]13394 noreturn attribute ignored on recursive invokation
+     * [451]13400 Compiled code crashes storing to read-only location
+     * [452]13521 Endless loop in calculate_global_regs_live
+
+    C++ compiler and library
+
+   Some of the bug fixes in this list were made to implement decisions
+   that the ISO C++ standards committee has made concerning several
+   defect reports (DRs). Links in the list below point to detailed
+   discussion of the relevant defect report.
+     * [453]2094 unimplemented: use of `ptrmem_cst' in template type
+       unification
+     * [454]2294 using declaration confusion
+     * [455]5050 template instantiation depth exceeds limit: recursion
+       problem?
+     * [456]9371 Bad exception handling in
+       i/ostream::operator>>/<<(streambuf*)
+     * [457]9546 bad exception handling in ostream members
+     * [458]10081 basic_ios::_M_cache_locale leaves NULL members in the
+       face of unknown locales
+     * [459]10093 [460][DR 61] Setting failbit in exceptions doesn't work
+     * [461]10095 istream::operator>>(int&) sets ios::badbit when
+       ios::failbit is set.
+     * [462]11554 Warning about reordering of initializers doesn't
+       mention location of constructor
+     * [463]12297 istream::sentry::sentry() handles eof() incorrectly.
+     * [464]12352 Exception safety problems in src/localename.cc
+     * [465]12438 Memory leak in locale::combine()
+     * [466]12540 Memory leak in locale::locale(const char*)
+     * [467]12594 DRs [468]60 [TC] and [469]63 [TC] not implemented
+     * [470]12657 Resolution of [471]DR 292 (WP) still unimplemented
+     * [472]12696 memory eating infinite loop in diagnostics (error
+       recovery problem)
+     * [473]12815 Code compiled with optimization behaves unexpectedly
+     * [474]12862 Conflicts between typedefs/enums and namespace member
+       declarations
+     * [475]12926 Wrong value after assignment in initialize list using
+       bit-fields
+     * [476]12967 Resolution of [477]DR 300 [WP] still unimplemented
+     * [478]12971 Resolution of [479]DR 328 [WP] still unimplemented
+     * [480]13007 basic_streambuf::pubimbue, imbue wrong
+     * [481]13009 Implicitly-defined assignment operator writes to wrong
+       memory
+     * [482]13057 regparm attribute not applied to destructor
+     * [483]13070 -Wformat option ignored in g++
+     * [484]13081 forward template declarations in <complex> let inlining
+       fail
+     * [485]13239 Assertion does not seem to work correctly anymore
+     * [486]13262 "xxx is private within this context" when initializing
+       a self-contained template class
+     * [487]13290 simple typo in concept checking for std::generate_n
+     * [488]13323 Template code does not compile in presence of typedef
+     * [489]13369 __verify_grouping (and __add_grouping?) not correct
+     * [490]13371 infinite loop with packed struct and inlining
+     * [491]13445 Template argument replacement "dereferences" a typedef
+     * [492]13461 Fails to access protected-ctor from public constant
+     * [493]13462 Non-standard-conforming type set::pointer
+     * [494]13478 gcc uses wrong constructor to initialize a const
+       reference
+     * [495]13544 "conflicting types" for enums in different scopes
+     * [496]13650 string::compare should not (always) use
+       traits_type::length()
+     * [497]13683 bogus warning about passing non-PODs through ellipsis
+     * [498]13688 Derived class is denied access to protected base class
+       member class
+     * [499]13774 Member variable cleared in virtual multiple inheritance
+       class
+     * [500]13884 Protect sstream.tcc from extern template use
+
+    Java compiler and library
+
+     * [501]10746 [win32] garbage collection crash in GCJ
+
+    Objective-C compiler and library
+
+     * [502]11433 Crash due to dereferencing null pointer when querying
+       protocol
+
+    Fortran compiler and library
+
+     * [503]12633 logical expression gives incorrect result with
+       -fugly-logint option
+     * [504]13037 [gcse-lm] g77 generates incorrect code
+     * [505]13213 Hex constant problem when compiling with -fugly-logint
+       and -ftypeless-boz
+
+    x86-specific (Intel/AMD)
+
+     * [506]4490 ICE with -m128bit-long-double
+     * [507]12292 [x86_64] ICE: RTL check: expected code `const_int',
+       have `reg' in make_field_assignment, in combine.c
+     * [508]12441 ICE: can't find a register to spill
+     * [509]12943 array static-init failure under -fpic, -fPIC
+     * [510]13608 Incorrect code with -O3 -ffast-math
+
+    PowerPC-specific
+
+     * [511]11598 testcase gcc.dg/20020118-1.c fails runtime check of
+       __attribute__((aligned(16)))
+     * [512]11793 ICE in extract_insn, in recog.c (const_vector's)
+     * [513]12467 vmsumubm emitted when vmsummbm appropriate (typo in
+       altivec.md)
+     * [514]12537 g++ generates writeable text sections
+
+    SPARC-specific
+
+     * [515]12496 wrong result for __atomic_add(&value, -1) when using
+       -O0 -m64
+     * [516]12865 mprotect call to make trampoline executable may fail
+     * [517]13354 ICE in sparc_emit_set_const32
+
+    ARM-specific
+
+     * [518]10467 [arm] ICE in pre_insert_copy_insn,
+
+    ia64-specific
+
+     * [519]11226 ICE passing struct arg with two floats
+     * [520]11227 ICE for _Complex float, _Complex long double args
+     * [521]12644 GCC 3.3.2 fails to compile glibc on ia64
+     * [522]13149 build gcc-3.3.2 1305 error:unrecognizable insn
+     * Various fixes for libunwind
+
+    Alpha-specific
+
+     * [523]12654 Incorrect comparison code generated for Alpha
+     * [524]12965 SEGV+ICE in cc1plus on alpha-linux with -O2
+     * [525]13031 ICE (unrecognizable insn) when building
+       gnome-libs-1.4.2
+
+    HPPA-specific
+
+     * [526]11634 [hppa] ICE in verify_local_live_at_start, in flow.c
+     * [527]12158 [hppa] compilation does not terminate at -O1
+
+    S390-specific
+
+     * [528]11992 Wrong built-in code for memcmp with length 1<<24: only
+       (1<<24)-1 possible for CLCL-Instruction
+
+    SH-specific
+
+     * [529]9365 segfault in gen_far_branch (config/sh/sh.c)
+     * [530]10392 optimizer generates faulty array indexing
+     * [531]11322 SH profiler outputs multiple definitions of symbol
+     * [532]13069 gcc/config/sh/rtems.h broken
+     * [533]13302 Putting a va_list in a struct causes seg fault
+     * [534]13585 Incorrect optimization of call to sfunc
+     * Fix inappropriately exported libgcc functions from the shared
+       library
+
+    Other embedded target specific
+
+     * [535]8916 [mcore] unsigned char assign gets hosed.
+     * [536]11576 [h8300] ICE in change_address_1, in emit-rtl.c
+     * [537]13122 [h8300] local variable gets corrupted by function call
+       when -fomit-frame-pointer is given
+     * [538]13256 [cris] strict_low_part mistreated in delay slots
+     * [539]13373 [mcore] optimization with -frerun-cse-after-loop
+       -fexpensive-optimizations produces wrong code on mcore
+
+    GNU HURD-specific
+
+     * [540]12561 gcc/config/t-gnu needs updating to work with
+       --with-sysroot
+
+    Tru64 Unix specific
+
+     * [541]6243 testsuite fails almost all tests due to no libintl in
+       LD_LIBRARY_PATH during test.
+     * [542]11397 weak aliases broken on Tru64 UNIX
+
+    AIX-specific
+
+     * [543]12505 build failure due to defines of uchar in cpphash.h and
+       sys/types.h
+     * [544]13150 WEAK symbols not exported by collect2
+
+    IRIX-specific
+
+     * [545]12666 fixincludes problem on IRIX 6.5.19m
+
+    Solaris-specific
+
+     * [546]12969 Including sys/byteorder.h breaks configure checks
+
+    Testsuite problems (compiler is not affected)
+
+     * [547]10819 testsuite creates CR+LF on compiler version lines in
+       test summary files
+     * [548]11612 abi_check not finding correct libgcc_s.so.1
+
+    Miscellaneous
+
+     * [549]13211 using -###, incorrect warnings about unused linker file
+       are produced
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [550]gnu@gnu.org. There
+   are also [551]other ways to contact the FSF.
+
+   These pages are maintained by [552]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [553]GCC manuals. If that fails, the
+    [554]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [555]gcc@gnu.org or
+    [556]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2004-05-15 [557]Valid XHTML 1.0 
+
+References
+
+   1. http://gcc.gnu.org/gcc-3.3/changes.html#3.3.3
+   2. http://gcc.gnu.org/gcc-3.1/changes.html#obsolete_systems
+   3. http://gcc.gnu.org/gcc-3.3/changes.html#obsolete_systems
+   4. http://gcc.gnu.org/gcc-3.3/changes.html#nonnull_attribute
+   5. http://gcc.gnu.org/news/dfa.html
+   6. http://gcc.gnu.org/gcc-3.3/c99status.html
+   7. http://gcc.gnu.org/onlinedocs/g77/News.html
+   8. http://gcc.gnu.org/PR10140
+   9. http://gcc.gnu.org/PR10198
+  10. http://gcc.gnu.org/PR10338
+  11. http://gcc.gnu.org/PR3581
+  12. http://gcc.gnu.org/PR4382
+  13. http://gcc.gnu.org/PR5533
+  14. http://gcc.gnu.org/PR6387
+  15. http://gcc.gnu.org/PR6412
+  16. http://gcc.gnu.org/PR6620
+  17. http://gcc.gnu.org/PR6663
+  18. http://gcc.gnu.org/PR7068
+  19. http://gcc.gnu.org/PR7083
+  20. http://gcc.gnu.org/PR7647
+  21. http://gcc.gnu.org/PR7675
+  22. http://gcc.gnu.org/PR7718
+  23. http://gcc.gnu.org/PR8116
+  24. http://gcc.gnu.org/PR8358
+  25. http://gcc.gnu.org/PR8511
+  26. http://gcc.gnu.org/PR8564
+  27. http://gcc.gnu.org/PR8660
+  28. http://gcc.gnu.org/PR8766
+  29. http://gcc.gnu.org/PR8803
+  30. http://gcc.gnu.org/PR8846
+  31. http://gcc.gnu.org/PR8906
+  32. http://gcc.gnu.org/PR9216
+  33. http://gcc.gnu.org/PR9261
+  34. http://gcc.gnu.org/PR9263
+  35. http://gcc.gnu.org/PR9429
+  36. http://gcc.gnu.org/PR9516
+  37. http://gcc.gnu.org/PR9600
+  38. http://gcc.gnu.org/PR9629
+  39. http://gcc.gnu.org/PR9672
+  40. http://gcc.gnu.org/PR9749
+  41. http://gcc.gnu.org/PR9794
+  42. http://gcc.gnu.org/PR9829
+  43. http://gcc.gnu.org/PR9916
+  44. http://gcc.gnu.org/PR9936
+  45. http://gcc.gnu.org/PR10262
+  46. http://gcc.gnu.org/PR10278
+  47. http://gcc.gnu.org/PR10446
+  48. http://gcc.gnu.org/PR10451
+  49. http://gcc.gnu.org/PR10506
+  50. http://gcc.gnu.org/PR10549
+  51. http://gcc.gnu.org/PR2001
+  52. http://gcc.gnu.org/PR2391
+  53. http://gcc.gnu.org/PR2960
+  54. http://gcc.gnu.org/PR4046
+  55. http://gcc.gnu.org/PR6405
+  56. http://gcc.gnu.org/PR6798
+  57. http://gcc.gnu.org/PR6871
+  58. http://gcc.gnu.org/PR6909
+  59. http://gcc.gnu.org/PR7189
+  60. http://gcc.gnu.org/PR7642
+  61. http://gcc.gnu.org/PR8634
+  62. http://gcc.gnu.org/PR8750
+  63. http://gcc.gnu.org/PR2161
+  64. http://gcc.gnu.org/PR4319
+  65. http://gcc.gnu.org/PR8602
+  66. http://gcc.gnu.org/PR9177
+  67. http://gcc.gnu.org/PR9853
+  68. http://gcc.gnu.org/PR45
+  69. http://gcc.gnu.org/PR3784
+  70. http://gcc.gnu.org/PR764
+  71. http://gcc.gnu.org/PR5116
+  72. http://gcc.gnu.org/PR2862
+  73. http://gcc.gnu.org/PR3663
+  74. http://gcc.gnu.org/PR3797
+  75. http://gcc.gnu.org/PR3948
+  76. http://gcc.gnu.org/PR4137
+  77. http://gcc.gnu.org/PR4361
+  78. http://gcc.gnu.org/PR4802
+  79. http://gcc.gnu.org/PR5837
+  80. http://gcc.gnu.org/PR4803
+  81. http://gcc.gnu.org/PR5094
+  82. http://gcc.gnu.org/PR5730
+  83. http://gcc.gnu.org/PR6713
+  84. http://gcc.gnu.org/PR7015
+  85. http://gcc.gnu.org/PR7086
+  86. http://gcc.gnu.org/PR7099
+  87. http://gcc.gnu.org/PR7247
+  88. http://gcc.gnu.org/PR7441
+  89. http://gcc.gnu.org/PR7768
+  90. http://gcc.gnu.org/PR7804
+  91. http://gcc.gnu.org/PR8099
+  92. http://gcc.gnu.org/PR8117
+  93. http://gcc.gnu.org/PR8205
+  94. http://gcc.gnu.org/PR8645
+  95. http://gcc.gnu.org/PR8724
+  96. http://gcc.gnu.org/PR8805
+  97. http://gcc.gnu.org/PR8691
+  98. http://gcc.gnu.org/PR8700
+  99. http://gcc.gnu.org/PR8724
+ 100. http://gcc.gnu.org/PR8949
+ 101. http://gcc.gnu.org/PR9016
+ 102. http://gcc.gnu.org/PR9053
+ 103. http://gcc.gnu.org/PR9152
+ 104. http://gcc.gnu.org/PR9182
+ 105. http://gcc.gnu.org/PR9297
+ 106. http://gcc.gnu.org/PR9318
+ 107. http://gcc.gnu.org/PR9320
+ 108. http://gcc.gnu.org/PR9400
+ 109. http://gcc.gnu.org/PR9424
+ 110. http://gcc.gnu.org/PR9425
+ 111. http://gcc.gnu.org/PR9439
+ 112. http://gcc.gnu.org/PR9474
+ 113. http://gcc.gnu.org/PR9548
+ 114. http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#231
+ 115. http://gcc.gnu.org/PR9555
+ 116. http://gcc.gnu.org/PR9561
+ 117. http://gcc.gnu.org/PR9563
+ 118. http://gcc.gnu.org/PR9582
+ 119. http://gcc.gnu.org/PR9622
+ 120. http://gcc.gnu.org/PR9683
+ 121. http://gcc.gnu.org/PR9791
+ 122. http://gcc.gnu.org/PR9817
+ 123. http://gcc.gnu.org/PR9825
+ 124. http://gcc.gnu.org/PR9826
+ 125. http://gcc.gnu.org/PR9924
+ 126. http://gcc.gnu.org/PR9946
+ 127. http://gcc.gnu.org/PR9964
+ 128. http://gcc.gnu.org/PR9988
+ 129. http://gcc.gnu.org/PR10033
+ 130. http://gcc.gnu.org/PR10097
+ 131. http://gcc.gnu.org/PR10132
+ 132. http://gcc.gnu.org/PR10180
+ 133. http://gcc.gnu.org/PR10199
+ 134. http://gcc.gnu.org/PR10300
+ 135. http://gcc.gnu.org/PR10427
+ 136. http://gcc.gnu.org/PR10503
+ 137. http://gcc.gnu.org/PR5956
+ 138. http://gcc.gnu.org/PR1832
+ 139. http://gcc.gnu.org/PR3924
+ 140. http://gcc.gnu.org/PR5634
+ 141. http://gcc.gnu.org/PR6367
+ 142. http://gcc.gnu.org/PR6491
+ 143. http://gcc.gnu.org/PR6742
+ 144. http://gcc.gnu.org/PR7113
+ 145. http://gcc.gnu.org/PR7236
+ 146. http://gcc.gnu.org/PR7278
+ 147. http://gcc.gnu.org/PR7384
+ 148. http://gcc.gnu.org/PR7388
+ 149. http://gcc.gnu.org/PR8587
+ 150. http://gcc.gnu.org/PR9038
+ 151. http://gcc.gnu.org/PR10197
+ 152. http://gcc.gnu.org/PR6005
+ 153. http://gcc.gnu.org/PR6389
+ 154. http://gcc.gnu.org/PR6576
+ 155. http://gcc.gnu.org/PR6652
+ 156. http://gcc.gnu.org/PR7060
+ 157. http://gcc.gnu.org/PR7073
+ 158. http://gcc.gnu.org/PR7180
+ 159. http://gcc.gnu.org/PR7416
+ 160. http://gcc.gnu.org/PR7570
+ 161. http://gcc.gnu.org/PR7578
+ 162. http://gcc.gnu.org/PR7611
+ 163. http://gcc.gnu.org/PR7709
+ 164. http://gcc.gnu.org/PR7766
+ 165. http://gcc.gnu.org/PR7785
+ 166. http://gcc.gnu.org/PR7786
+ 167. http://gcc.gnu.org/PR8142
+ 168. http://gcc.gnu.org/PR8234
+ 169. http://gcc.gnu.org/PR8415
+ 170. http://gcc.gnu.org/PR8481
+ 171. http://gcc.gnu.org/PR8593
+ 172. http://gcc.gnu.org/PR8759
+ 173. http://gcc.gnu.org/PR8997
+ 174. http://gcc.gnu.org/PR9253
+ 175. http://gcc.gnu.org/PR9254
+ 176. http://gcc.gnu.org/PR9271
+ 177. http://gcc.gnu.org/PR6767
+ 178. http://gcc.gnu.org/PR9911
+ 179. http://gcc.gnu.org/PR10020
+ 180. http://gcc.gnu.org/PR10546
+ 181. http://gcc.gnu.org/PR7029
+ 182. http://gcc.gnu.org/PR2903
+ 183. http://gcc.gnu.org/PR7873
+ 184. http://gcc.gnu.org/PR7680
+ 185. http://gcc.gnu.org/PR8705
+ 186. http://gcc.gnu.org/PR9986
+ 187. http://gcc.gnu.org/PR10056
+ 188. http://gcc.gnu.org/PR6744
+ 189. http://gcc.gnu.org/PR7361
+ 190. http://gcc.gnu.org/PR9496
+ 191. http://gcc.gnu.org/PR7067
+ 192. http://gcc.gnu.org/PR8480
+ 193. http://gcc.gnu.org/PR8784
+ 194. http://gcc.gnu.org/PR10315
+ 195. http://gcc.gnu.org/PR10267
+ 196. http://gcc.gnu.org/PR7916
+ 197. http://gcc.gnu.org/PR7926
+ 198. http://gcc.gnu.org/PR8555
+ 199. http://gcc.gnu.org/PR8994
+ 200. http://gcc.gnu.org/PR9426
+ 201. http://gcc.gnu.org/PR9806
+ 202. http://gcc.gnu.org/PR10077
+ 203. http://gcc.gnu.org/PR10233
+ 204. http://gcc.gnu.org/PR10286
+ 205. http://gcc.gnu.org/PR10308
+ 206. http://gcc.gnu.org/PR11272
+ 207. http://gcc.gnu.org/PR5754
+ 208. http://gcc.gnu.org/PR6597
+ 209. http://gcc.gnu.org/PR6949
+ 210. http://gcc.gnu.org/PR7053
+ 211. http://gcc.gnu.org/PR8164
+ 212. http://gcc.gnu.org/PR8384
+ 213. http://gcc.gnu.org/PR9559
+ 214. http://gcc.gnu.org/PR9649
+ 215. http://gcc.gnu.org/PR9864
+ 216. http://gcc.gnu.org/PR10432
+ 217. http://gcc.gnu.org/PR10475
+ 218. http://gcc.gnu.org/PR10635
+ 219. http://gcc.gnu.org/PR10661
+ 220. http://gcc.gnu.org/PR10700
+ 221. http://gcc.gnu.org/PR10712
+ 222. http://gcc.gnu.org/PR10796
+ 223. http://gcc.gnu.org/PR10890
+ 224. http://gcc.gnu.org/PR10939
+ 225. http://gcc.gnu.org/PR10956
+ 226. http://gcc.gnu.org/PR11041
+ 227. http://gcc.gnu.org/PR11059
+ 228. http://gcc.gnu.org/PR11083
+ 229. http://gcc.gnu.org/PR11105
+ 230. http://gcc.gnu.org/PR11149
+ 231. http://gcc.gnu.org/PR11228
+ 232. http://gcc.gnu.org/PR11282
+ 233. http://gcc.gnu.org/PR11301
+ 234. http://gcc.gnu.org/PR11308
+ 235. http://gcc.gnu.org/PR11473
+ 236. http://gcc.gnu.org/PR11503
+ 237. http://gcc.gnu.org/PR11513
+ 238. http://gcc.gnu.org/PR11198
+ 239. http://gcc.gnu.org/PR11304
+ 240. http://gcc.gnu.org/PR11381
+ 241. http://gcc.gnu.org/PR11536
+ 242. http://gcc.gnu.org/PR11557
+ 243. http://gcc.gnu.org/PR5897
+ 244. http://gcc.gnu.org/PR11279
+ 245. http://gcc.gnu.org/PR11022
+ 246. http://gcc.gnu.org/PR2330
+ 247. http://gcc.gnu.org/PR5388
+ 248. http://gcc.gnu.org/PR5390
+ 249. http://gcc.gnu.org/PR7877
+ 250. http://gcc.gnu.org/PR9393
+ 251. http://gcc.gnu.org/PR10032
+ 252. http://gcc.gnu.org/PR10468
+ 253. http://gcc.gnu.org/PR10527
+ 254. http://gcc.gnu.org/PR10679
+ 255. http://gcc.gnu.org/PR10682
+ 256. http://gcc.gnu.org/PR10689
+ 257. http://gcc.gnu.org/PR10845
+ 258. http://gcc.gnu.org/PR10849
+ 259. http://gcc.gnu.org/PR10888
+ 260. http://gcc.gnu.org/PR10929
+ 261. http://gcc.gnu.org/PR10931
+ 262. http://gcc.gnu.org/PR10940
+ 263. http://gcc.gnu.org/PR10968
+ 264. http://gcc.gnu.org/PR10990
+ 265. http://gcc.gnu.org/PR11039
+ 266. http://gcc.gnu.org/PR11062
+ 267. http://gcc.gnu.org/PR11095
+ 268. http://gcc.gnu.org/PR11098
+ 269. http://gcc.gnu.org/PR11137
+ 270. http://gcc.gnu.org/PR11154
+ 271. http://gcc.gnu.org/PR11329
+ 272. http://gcc.gnu.org/PR11332
+ 273. http://gcc.gnu.org/PR11431
+ 274. http://gcc.gnu.org/PR11528
+ 275. http://gcc.gnu.org/PR11546
+ 276. http://gcc.gnu.org/PR11567
+ 277. http://gcc.gnu.org/PR11645
+ 278. http://gcc.gnu.org/PR5179
+ 279. http://gcc.gnu.org/PR8204
+ 280. http://gcc.gnu.org/PR10838
+ 281. http://gcc.gnu.org/PR10886
+ 282. http://gcc.gnu.org/PR11349
+ 283. http://gcc.gnu.org/PR4823
+ 284. http://gcc.gnu.org/PR8878
+ 285. http://gcc.gnu.org/PR9815
+ 286. http://gcc.gnu.org/PR10402
+ 287. http://gcc.gnu.org/PR10504
+ 288. http://gcc.gnu.org/PR10673
+ 289. http://gcc.gnu.org/PR11044
+ 290. http://gcc.gnu.org/PR11089
+ 291. http://gcc.gnu.org/PR11420
+ 292. http://gcc.gnu.org/PR9362
+ 293. http://gcc.gnu.org/PR10142
+ 294. http://gcc.gnu.org/PR10663
+ 295. http://gcc.gnu.org/PR10835
+ 296. http://gcc.gnu.org/PR10876
+ 297. http://gcc.gnu.org/PR10955
+ 298. http://gcc.gnu.org/PR11018
+ 299. http://gcc.gnu.org/PR11556
+ 300. http://gcc.gnu.org/PR10907
+ 301. http://gcc.gnu.org/PR11320
+ 302. http://gcc.gnu.org/PR11599
+ 303. http://gcc.gnu.org/PR9745
+ 304. http://gcc.gnu.org/PR10871
+ 305. http://gcc.gnu.org/PR11440
+ 306. http://gcc.gnu.org/PR7594
+ 307. http://gcc.gnu.org/PR10557
+ 308. http://gcc.gnu.org/PR11054
+ 309. http://gcc.gnu.org/PR10834
+ 310. http://gcc.gnu.org/PR10842
+ 311. http://gcc.gnu.org/PR11052
+ 312. http://gcc.gnu.org/PR11183
+ 313. http://gcc.gnu.org/PR11084
+ 314. http://gcc.gnu.org/PR10331
+ 315. http://gcc.gnu.org/PR10413
+ 316. http://gcc.gnu.org/PR11096
+ 317. http://gcc.gnu.org/PR2873
+ 318. http://gcc.gnu.org/PR3163
+ 319. http://gcc.gnu.org/PR5287
+ 320. http://gcc.gnu.org/PR10148
+ 321. http://gcc.gnu.org/PR8787
+ 322. http://gcc.gnu.org/PR10900
+ 323. http://gcc.gnu.org/PR1607
+ 324. http://gcc.gnu.org/PR4252
+ 325. http://gcc.gnu.org/PR4490
+ 326. http://gcc.gnu.org/PR10355
+ 327. http://gcc.gnu.org/PR10726
+ 328. http://gcc.gnu.org/PR10805
+ 329. http://gcc.gnu.org/PR10815
+ 330. http://gcc.gnu.org/PR10877
+ 331. http://gcc.gnu.org/PR11280
+ 332. http://gcc.gnu.org/PR11466
+ 333. http://gcc.gnu.org/PR10737
+ 334. http://gcc.gnu.org/PR10810
+ 335. http://gcc.gnu.org/bugzilla/
+ 336. http://gcc.gnu.org/PR8336
+ 337. http://gcc.gnu.org/PR9330
+ 338. http://gcc.gnu.org/PR9631
+ 339. http://gcc.gnu.org/PR9877
+ 340. http://gcc.gnu.org/PR11687
+ 341. http://gcc.gnu.org/PR12263
+ 342. http://gcc.gnu.org/PR12490
+ 343. http://gcc.gnu.org/PR7277
+ 344. http://gcc.gnu.org/PR7939
+ 345. http://gcc.gnu.org/PR11063
+ 346. http://gcc.gnu.org/PR11207
+ 347. http://gcc.gnu.org/PR11522
+ 348. http://gcc.gnu.org/PR11595
+ 349. http://gcc.gnu.org/PR11646
+ 350. http://gcc.gnu.org/PR11665
+ 351. http://gcc.gnu.org/PR11852
+ 352. http://gcc.gnu.org/PR11878
+ 353. http://gcc.gnu.org/PR11883
+ 354. http://gcc.gnu.org/PR11991
+ 355. http://gcc.gnu.org/PR12146
+ 356. http://gcc.gnu.org/PR12215
+ 357. http://gcc.gnu.org/PR12369
+ 358. http://gcc.gnu.org/PR12446
+ 359. http://gcc.gnu.org/PR12510
+ 360. http://gcc.gnu.org/PR12544
+ 361. http://gcc.gnu.org/PR9862
+ 362. http://gcc.gnu.org/PR10962
+ 363. http://gcc.gnu.org/PR11370
+ 364. http://gcc.gnu.org/PR11637
+ 365. http://gcc.gnu.org/PR11885
+ 366. http://gcc.gnu.org/PR12082
+ 367. http://gcc.gnu.org/PR12180
+ 368. http://gcc.gnu.org/PR12340
+ 369. http://gcc.gnu.org/PR3907
+ 370. http://gcc.gnu.org/PR5293
+ 371. http://gcc.gnu.org/PR5296
+ 372. http://gcc.gnu.org/PR7939
+ 373. http://gcc.gnu.org/PR8656
+ 374. http://gcc.gnu.org/PR10147
+ 375. http://gcc.gnu.org/PR11400
+ 376. http://gcc.gnu.org/PR11409
+ 377. http://gcc.gnu.org/PR11740
+ 378. http://gcc.gnu.org/PR11786
+ 379. http://gcc.gnu.org/PR11867
+ 380. http://gcc.gnu.org/PR11928
+ 381. http://gcc.gnu.org/PR12114
+ 382. http://gcc.gnu.org/PR12163
+ 383. http://gcc.gnu.org/PR12181
+ 384. http://gcc.gnu.org/PR12236
+ 385. http://gcc.gnu.org/PR12266
+ 386. http://gcc.gnu.org/PR12296
+ 387. http://gcc.gnu.org/PR12298
+ 388. http://gcc.gnu.org/PR12369
+ 389. http://gcc.gnu.org/PR12337
+ 390. http://gcc.gnu.org/PR12344
+ 391. http://gcc.gnu.org/PR12451
+ 392. http://gcc.gnu.org/PR12486
+ 393. http://gcc.gnu.org/PR8869
+ 394. http://gcc.gnu.org/PR9786
+ 395. http://gcc.gnu.org/PR11689
+ 396. http://gcc.gnu.org/PR12116
+ 397. http://gcc.gnu.org/PR12070
+ 398. http://gcc.gnu.org/PR11184
+ 399. http://gcc.gnu.org/PR11535
+ 400. http://gcc.gnu.org/PR11693
+ 401. http://gcc.gnu.org/PR12224
+ 402. http://gcc.gnu.org/PR11087
+ 403. http://gcc.gnu.org/PR11319
+ 404. http://gcc.gnu.org/PR11949
+ 405. http://gcc.gnu.org/PR11662
+ 406. http://gcc.gnu.org/PR11965
+ 407. http://gcc.gnu.org/PR12301
+ 408. http://gcc.gnu.org/PR11717
+ 409. http://gcc.gnu.org/PR11313
+ 410. http://gcc.gnu.org/PR11712
+ 411. http://gcc.gnu.org/PR12166
+ 412. http://gcc.gnu.org/PR12101
+ 413. http://gcc.gnu.org/PR10988
+ 414. http://gcc.gnu.org/PR11805
+ 415. http://gcc.gnu.org/PR11902
+ 416. http://gcc.gnu.org/PR11903
+ 417. http://gcc.gnu.org/bugzilla/
+ 418. http://gcc.gnu.org/PR11890
+ 419. http://gcc.gnu.org/PR12399
+ 420. http://gcc.gnu.org/PR13068
+ 421. http://gcc.gnu.org/PR10060
+ 422. http://gcc.gnu.org/PR10555
+ 423. http://gcc.gnu.org/PR10706
+ 424. http://gcc.gnu.org/PR11496
+ 425. http://gcc.gnu.org/PR11741
+ 426. http://gcc.gnu.org/PR12440
+ 427. http://gcc.gnu.org/PR12632
+ 428. http://gcc.gnu.org/PR12712
+ 429. http://gcc.gnu.org/PR12726
+ 430. http://gcc.gnu.org/PR12890
+ 431. http://gcc.gnu.org/PR12900
+ 432. http://gcc.gnu.org/PR13060
+ 433. http://gcc.gnu.org/PR13289
+ 434. http://gcc.gnu.org/PR13318
+ 435. http://gcc.gnu.org/PR13392
+ 436. http://gcc.gnu.org/PR13574
+ 437. http://gcc.gnu.org/PR13475
+ 438. http://gcc.gnu.org/PR13797
+ 439. http://gcc.gnu.org/PR13824
+ 440. http://gcc.gnu.org/PR8776
+ 441. http://gcc.gnu.org/PR10339
+ 442. http://gcc.gnu.org/PR11350
+ 443. http://gcc.gnu.org/PR12826
+ 444. http://gcc.gnu.org/PR12500
+ 445. http://gcc.gnu.org/PR12941
+ 446. http://gcc.gnu.org/PR12953
+ 447. http://gcc.gnu.org/PR13041
+ 448. http://gcc.gnu.org/PR13507
+ 449. http://gcc.gnu.org/PR13382
+ 450. http://gcc.gnu.org/PR13394
+ 451. http://gcc.gnu.org/PR13400
+ 452. http://gcc.gnu.org/PR13521
+ 453. http://gcc.gnu.org/PR2094
+ 454. http://gcc.gnu.org/PR2294
+ 455. http://gcc.gnu.org/PR5050
+ 456. http://gcc.gnu.org/PR9371
+ 457. http://gcc.gnu.org/PR9546
+ 458. http://gcc.gnu.org/PR10081
+ 459. http://gcc.gnu.org/PR10093
+ 460. http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#61
+ 461. http://gcc.gnu.org/PR10095
+ 462. http://gcc.gnu.org/PR11554
+ 463. http://gcc.gnu.org/PR12297
+ 464. http://gcc.gnu.org/PR12352
+ 465. http://gcc.gnu.org/PR12438
+ 466. http://gcc.gnu.org/PR12540
+ 467. http://gcc.gnu.org/PR12594
+ 468. http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#60
+ 469. http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#63
+ 470. http://gcc.gnu.org/PR12657
+ 471. http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#292
+ 472. http://gcc.gnu.org/PR12696
+ 473. http://gcc.gnu.org/PR12815
+ 474. http://gcc.gnu.org/PR12862
+ 475. http://gcc.gnu.org/PR12926
+ 476. http://gcc.gnu.org/PR12967
+ 477. http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html
+ 478. http://gcc.gnu.org/PR12971
+ 479. http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#328
+ 480. http://gcc.gnu.org/PR13007
+ 481. http://gcc.gnu.org/PR13009
+ 482. http://gcc.gnu.org/PR13057
+ 483. http://gcc.gnu.org/PR13070
+ 484. http://gcc.gnu.org/PR13081
+ 485. http://gcc.gnu.org/PR13239
+ 486. http://gcc.gnu.org/PR13262
+ 487. http://gcc.gnu.org/PR13290
+ 488. http://gcc.gnu.org/PR13323
+ 489. http://gcc.gnu.org/PR13369
+ 490. http://gcc.gnu.org/PR13371
+ 491. http://gcc.gnu.org/PR13445
+ 492. http://gcc.gnu.org/PR13461
+ 493. http://gcc.gnu.org/PR13462
+ 494. http://gcc.gnu.org/PR13478
+ 495. http://gcc.gnu.org/PR13544
+ 496. http://gcc.gnu.org/PR13650
+ 497. http://gcc.gnu.org/PR13683
+ 498. http://gcc.gnu.org/PR13688
+ 499. http://gcc.gnu.org/PR13774
+ 500. http://gcc.gnu.org/PR13884
+ 501. http://gcc.gnu.org/PR10746
+ 502. http://gcc.gnu.org/PR11433
+ 503. http://gcc.gnu.org/PR12633
+ 504. http://gcc.gnu.org/PR13037
+ 505. http://gcc.gnu.org/PR13213
+ 506. http://gcc.gnu.org/PR4490
+ 507. http://gcc.gnu.org/PR12292
+ 508. http://gcc.gnu.org/PR12441
+ 509. http://gcc.gnu.org/PR12943
+ 510. http://gcc.gnu.org/PR13608
+ 511. http://gcc.gnu.org/PR11598
+ 512. http://gcc.gnu.org/PR11793
+ 513. http://gcc.gnu.org/PR12467
+ 514. http://gcc.gnu.org/PR12537
+ 515. http://gcc.gnu.org/PR12496
+ 516. http://gcc.gnu.org/PR12865
+ 517. http://gcc.gnu.org/PR13354
+ 518. http://gcc.gnu.org/PR10467
+ 519. http://gcc.gnu.org/PR11226
+ 520. http://gcc.gnu.org/PR11227
+ 521. http://gcc.gnu.org/PR12644
+ 522. http://gcc.gnu.org/PR13149
+ 523. http://gcc.gnu.org/PR12654
+ 524. http://gcc.gnu.org/PR12965
+ 525. http://gcc.gnu.org/PR13031
+ 526. http://gcc.gnu.org/PR11634
+ 527. http://gcc.gnu.org/PR12158
+ 528. http://gcc.gnu.org/PR11992
+ 529. http://gcc.gnu.org/PR9365
+ 530. http://gcc.gnu.org/PR10392
+ 531. http://gcc.gnu.org/PR11322
+ 532. http://gcc.gnu.org/PR13069
+ 533. http://gcc.gnu.org/PR13302
+ 534. http://gcc.gnu.org/PR13585
+ 535. http://gcc.gnu.org/PR8916
+ 536. http://gcc.gnu.org/PR11576
+ 537. http://gcc.gnu.org/PR13122
+ 538. http://gcc.gnu.org/PR13256
+ 539. http://gcc.gnu.org/PR13373
+ 540. http://gcc.gnu.org/PR12561
+ 541. http://gcc.gnu.org/PR6243
+ 542. http://gcc.gnu.org/PR11397
+ 543. http://gcc.gnu.org/PR12505
+ 544. http://gcc.gnu.org/PR13150
+ 545. http://gcc.gnu.org/PR12666
+ 546. http://gcc.gnu.org/PR12969
+ 547. http://gcc.gnu.org/PR10819
+ 548. http://gcc.gnu.org/PR11612
+ 549. http://gcc.gnu.org/PR13211
+ 550. mailto:gnu@gnu.org
+ 551. http://www.gnu.org/home.html#ContactInfo
+ 552. http://gcc.gnu.org/about.html
+ 553. http://gcc.gnu.org/onlinedocs/
+ 554. mailto:gcc-help@gcc.gnu.org
+ 555. mailto:gcc@gnu.org
+ 556. mailto:gcc@gcc.gnu.org
+ 557. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/gcc-3.2/index.html
+
+                           GCC 3.2 Release Series
+
+   April 25, 2003
+
+   The [1]GNU project and the GCC developers are pleased to announce the
+   release of GCC 3.2.3.
+
+   The purpose of the GCC 3.2 release series is to provide a stable
+   platform for OS distributors to use building their next releases. A
+   primary objective was to stabilize the C++ ABI; we believe that the
+   interface to the compiler and the C++ standard library are now
+   relatively stable.
+
+   Be aware that C++ code compiled by GCC 3.2.x will (in general) not
+   interoperate with code compiled by GCC 3.1.1 or earlier.
+
+   Please refer to our [2]detailed list of news, caveats, and bug-fixes
+   for further information.
+
+Release History
+
+   GCC 3.2.3
+          April 25, 2003 ([3]changes)
+
+   GCC 3.2.2
+          February 5, 2003 ([4]changes)
+
+   GCC 3.2.1
+          November 19, 2002 ([5]changes)
+
+   GCC 3.2
+          August 14, 2002 ([6]changes)
+
+References and Acknowledgements
+
+   GCC used to stand for the GNU C Compiler, but since the compiler
+   supports several other languages aside from C, it now stands for the
+   GNU Compiler Collection.
+
+   A list of [7]successful builds is updated as new information becomes
+   available.
+
+   The GCC developers would like to thank the numerous people that have
+   contributed new features, improvements, bug fixes, and other changes
+   as well as test results to GCC. This [8]amazing group of volunteers is
+   what makes GCC successful.
+
+   For additional information about GCC please refer to the [9]GCC
+   project web site or contact the [10]GCC development mailing list.
+
+   To obtain GCC please use [11]our mirror sites, one of the [12]GNU
+   mirror sites, or [13]our CVS server.
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [14]gnu@gnu.org. There
+   are also [15]other ways to contact the FSF.
+
+   These pages are maintained by [16]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [17]GCC manuals. If that fails, the
+    [18]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [19]gcc@gnu.org or
+    [20]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [21]Valid XHTML 1.0 
+
+References
+
+   1. http://www.gnu.org/
+   2. http://gcc.gnu.org/gcc-3.2/changes.html
+   3. http://gcc.gnu.org/gcc-3.2/changes.html#3.2.3
+   4. http://gcc.gnu.org/gcc-3.2/changes.html#3.2.2
+   5. http://gcc.gnu.org/gcc-3.2/changes.html#3.2.1
+   6. http://gcc.gnu.org/gcc-3.2/changes.html#3.2
+   7. http://gcc.gnu.org/gcc-3.2/buildstat.html
+   8. http://gcc.gnu.org/onlinedocs/gcc/Contributors.html
+   9. http://gcc.gnu.org/index.html
+  10. mailto:gcc@gcc.gnu.org
+  11. http://gcc.gnu.org/mirrors.html
+  12. http://www.gnu.org/order/ftp.html
+  13. http://gcc.gnu.org/cvs.html
+  14. mailto:gnu@gnu.org
+  15. http://www.gnu.org/home.html#ContactInfo
+  16. http://gcc.gnu.org/about.html
+  17. http://gcc.gnu.org/onlinedocs/
+  18. mailto:gcc-help@gcc.gnu.org
+  19. mailto:gcc@gnu.org
+  20. mailto:gcc@gcc.gnu.org
+  21. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/gcc-3.2/changes.html
+
+                           GCC 3.2 Release Series
+                      Changes, New Features, and Fixes
+
+   The latest release in the 3.2 release series is [1]GCC 3.2.3.
+
+Caveats and New Features
+
+  Caveats
+
+     * The C++ compiler does not correctly zero-initialize
+       pointers-to-data members. You must explicitly initialize them. For
+       example: int S::*m(0); will work, but depending on
+       default-initialization to zero will not work. This bug cannot be
+       fixed in GCC 3.2 without inducing unacceptable risks. It will be
+       fixed in GCC 3.3.
+     * This GCC release is based on the GCC 3.1 sourcebase, and thus has
+       all the [2]changes in the GCC 3.1 series. In addition, GCC 3.2 has
+       a number of C++ ABI fixes which make its C++ compiler generate
+       binary code which is incompatible with the C++ compilers found in
+       earlier GCC releases, including GCC 3.1 and GCC 3.1.1.
+
+  Frontend Enhancements
+
+    C/C++/Objective-C
+
+     * The method of constructing the list of directories to be searched
+       for header files has been revised. If a directory named by a -I
+       option is a standard system include directory, the option is
+       ignored to ensure that the default search order for system
+       directories and the special treatment of system header files are
+       not defeated.
+     * The C and Objective-C compilers no longer accept the "Naming
+       Types" extension (typedef foo = bar); it was already unavailable
+       in C++. Code which uses it will need to be changed to use the
+       "typeof" extension instead: typedef typeof(bar) foo. (We have
+       removed this extension without a period of deprecation because it
+       has caused the compiler to crash since version 3.0 and no one
+       noticed until very recently. Thus we conclude it is not in
+       widespread use.)
+
+    C++
+
+     * There are now no known differences between the C++ ABI implemented
+       in GCC and the multi-vendor standard. We believe that the ABI for
+       the C++ standard library is now stable and will not change in
+       future versions of the compiler. However, hard experience has
+       taught us to be cautious; it is possible that more problems will
+       be found. It is our intention to make changes to the ABI only if
+       they are necessary for correct compilation of C++, as opposed to
+       conformance to the ABI documents.
+     * For details on how to build an ABI compliant compiler for
+       GNU/Linux systems, check the [3]common C++ ABI page.
+
+  New Targets and Target Specific Improvements
+
+    IA-32
+
+     * Fixed a number of bugs in SSE and MMX intrinsics.
+     * Fixed common compiler crashes with SSE instruction set enabled
+       (implied by -march=pentium3, pentium4, athlon-xp)
+     * __m128 and __m128i is not 128bit aligned when used in structures.
+
+    x86-64
+
+     * A bug whereby the compiler could generate bad code for bzero has
+       been fixed.
+     * ABI fixes (implying ABI incompatibilities with previous version in
+       some corner cases)
+     * Fixed prefetch code generation
+     _________________________________________________________________
+
+GCC 3.2.3
+
+   3.2.3 is a bug fix release only; there are no new features that were
+   not present in GCC 3.2.2.
+
+  Bug Fixes
+
+   This section lists the problem reports (PRs) from GCC's bug tracking
+   system that are known to be fixed in the 3.2.3 release. This list
+   might not be complete (that is, it is possible that some PRs that have
+   been fixed are not listed here), and some of the titles have been
+   changed to make them more clear.
+
+    Internal Compiler Errors (multi-platform)
+
+     * [4]3782: (c++) -quiet -fstats produces a segmentation fault in
+       cc1plus
+     * [5]6440: (c++) template specializations cause ICE
+     * [6]7050: (c++) ICE on: (i ? get_string() : throw)
+     * [7]7741: ICE on conflicting types (make_decl_rtl in varasm.c)
+     * [8]7982: (c++) ICE due to infinite recursion (using STL set)
+     * [9]8068: exceedingly high (infinite) memory usage
+     * [10]8178: ICE with __builtin_ffs
+     * [11]8396: ICE in copy_to_mode_reg, in explow.c
+     * [12]8674: (c++) ICE in cp_expr_size, in cp/cp-lang.c
+     * [13]9768: ICE when optimizing inline code at -O2
+     * [14]9798: (c++) Infinite recursion (segfault) in
+       cp/decl.c:push_using_directive with recursive using directives
+     * [15]9799: mismatching structure initializer with nested flexible
+       array member: ICE
+     * [16]9928: ICE on duplicate enum declaration
+     * [17]10114: ICE in mem_loc_descriptor, in dwarf2out.c (affects
+       sparc, alpha)
+     * [18]10352: ICE in find_reloads_toplev
+     * [19]10336: ICE with -Wunreachable-code
+
+    C/optimizer bugs:
+
+     * [20]8224: Incorrect joining of signed and unsigned division
+     * [21]8613: -O2 produces wrong code with builtin strlen and
+       postincrements
+     * [22]8828: gcc reports some code is unreachable when it is not
+     * [23]9226: GCSE breaking argument passing
+     * [24]9853: miscompilation of non-constant structure initializer
+     * [25]9797: C99-style struct initializers are miscompiled
+     * [26]9967: Some standard C function calls should not be replaced
+       when optimizing for size
+     * [27]10116: ce2: invalid merge of join_bb in the context of switch
+       statements
+     * [28]10171: wrong code for inlined function
+     * [29]10175: -Wunreachable-code doesn't work for single lines
+
+    C++ compiler and library:
+
+     * [30]8316: Confusing diagnostic for code that misuses conversion
+       operators
+     * [31]9169: filebuf output fails if codecvt<>::out returns noconv
+     * [32]9420: incomplete type incorrectly reported
+     * [33]9459: typeof in return type specification of template not
+       supported
+     * [34]9507: filebuf::open handles ios_base::ate incorrectly
+     * [35]9538: Out-of-bounds memory access in streambuf::sputbackc
+     * [36]9602: Total confusion about template/friend/virtual/abstract
+     * [37]9993: destructor not called for local object created within
+       and returned from infinite loop
+     * [38]10167: ieee_1003.1-2001 locale specialisations on a
+       glibc-2.3.2 system
+
+    Java compiler and library:
+
+     * [39]9652: libgcj build fails on irix6.5.1[78]
+     * [40]10144: gas on solaris complains about bad .stabs lines for
+       java, native as unaffected
+
+    x86-specific (Intel/AMD):
+
+     * [41]8746: gcc miscompiles Linux kernel ppa driver on x86
+     * [42]9888: -mcpu=k6 -Os produces out of range loop instructions
+     * [43]9638: Cross-build for target i386-elf and i586-pc-linux-gnu
+       failed
+     * [44]9954: Cross-build for target i586-pc-linux-gnu (--with-newlib)
+       failed
+
+    Sparc-specific:
+
+     * [45]7784: [Sparc] ICE in extract_insn, in recog.c
+     * [46]7796: sparc extra failure with -m64 on execute/930921-1.c in
+       unroll.c
+     * [47]8281: ICE when compiling with -O2 -fPIC for Ultrasparc
+     * [48]8366: [Sparc] C testsuite failure with -m64 -fpic -O in
+       execute/loop-2d.c
+     * [49]8726: gcc -O2 miscompiles Samba 2.2.7 on 32-bit sparc
+     * [50]9414: Scheduling bug on Ultrasparc
+     * [51]10067: GCC-3.2.2 outputs invalid asm on sparc64
+
+    m68k-specific:
+
+     * [52]7248: broken "inclusive or" code
+     * [53]8343: m68k-elf/rtems ICE at instantiate_virtual_regs_1
+
+    PowerPC-specific:
+
+     * [54]9732: Wrong code with -O2 -fPIC
+     * [55]10073: ICE: powerpc cannot split insn
+
+    Alpha-specific:
+
+     * [56]7702: optimization problem on a DEC alpha under OSF1
+     * [57]9671: gcc.3.2.2 does not build on a HP Tru64 Unix v5.1B system
+
+    HP-specific:
+
+     * [58]8694: <string> breaks <ctype.h> on HP-UX 10.20 (DUP: 9275)
+     * [59]9953: (ada) gcc 3.2.x can't build 3.3-branch ada on HP-UX 10
+       (missing symbol)
+     * [60]10271: Floating point args don't get reloaded across function
+       calls with -O2
+
+    MIPS specific:
+
+     * [61]6362: mips-irix6 gcc-3.1 C testsuite failure with -mips4 in
+       compile/920501-4.c
+
+    CRIS specific:
+
+     * [62]10377: gcc-3.2.2 creates bad assembler code for cris
+
+    Miscellaneous and minor bugs:
+
+     * [63]6955: collect2 says "core dumped" when there is no core
+     _________________________________________________________________
+
+GCC 3.2.2
+
+   Beginning with 3.2.2, GCC's Makefile suite supports redirection of
+   make install by means of the DESTDIR variable. Parts of the GCC tree
+   have featured that support long before, but now it is available even
+   from the top level.
+
+   Other than that, GCC 3.2.2 is a bug fix release only; there are no new
+   features that were not present in GCC 3.2.1.
+
+  Bug Fixes
+
+   On the following i386-based systems GCC 3.2.1 broke the C ABI wrt.
+   functions returning structures: Cygwin, FreeBSD (GCC 3.2.1 as shipped
+   with FreeBSD 5.0 does not have this problem), Interix, a.out-based
+   Linux and NetBSD, OpenBSD, and Darwin. GCC 3.2.2 reverts this ABI
+   change, and thus restores ABI-compatibility with previous releases
+   (except GCC 3.2.1) on these platforms.
+
+   This section lists the problem reports (PRs) from GCC's bug tracking
+   system that are known to be fixed in the 3.2.2 release. This list
+   might not be complete (that is, it is possible that some PRs that have
+   been fixed are not listed here) and some of the titles have been
+   changed to make them more clear.
+
+    Internal Compiler Errors (multi-platform)
+
+     * [64]5919: (c++) ICE when passing variable array to template
+       function
+     * [65]7129: (c++) ICE with min/max assignment operators (<?= and
+       >?=)
+     * [66]7507: ICE with -O2 when address of called function is a
+       complicated expression
+     * [67]7622: ICE with nested inline functions if function's address
+       is taken
+     * [68]7681: (fortran) ICE in compensate_edge, in reg-stack.c (also
+       PR [69]9258)
+     * [70]8031: (c++) ICE in code comparing typeids and casting from
+       virtual base
+     * [71]8275: ICE in simplify_subreg
+     * [72]8332: (c++) builtin strlen/template interaction causes ICE
+     * [73]8372: (c++) ICE on explicit call of destructor
+     * [74]8439: (c, not c++) empty struct causes ICE
+     * [75]8442: (c++) ICE with nested template classes
+     * [76]8518: ICE when compiling mplayer ("extern inline" issue)
+     * [77]8615: (c++) ICE with out-of-range character constant template
+       argument
+     * [78]8663: (c++) ICE in cp_expr_size, at cp-lang.c:307
+     * [79]8799: (c++) ICE: error reporting routines re-entered
+     * [80]9328: (c++) ICE with typeof(X) for overloaded X
+     * [81]9465: (preprocessor) cpp -traditional ICE on null bytes
+
+    C++ (compiler and library) bugs
+
+     * [82]47: scoping in nested classes is broken
+     * [83]6745: problems with iostream rdbuf() member function
+     * [84]8214: conversion from const char* const to char* sometimes
+       accepted illegally
+     * [85]8493: builtin strlen and overload resolution (same bug as
+       [86]8332)
+     * [87]8503: strange behaviour of function types
+     * [88]8727: compiler confused by inheritance from an anonymous
+       struct
+     * [89]7445: poor performance of std::locale::classic() in
+       multi-threaded applications
+     * [90]8230: mishandling of overflow in vector<T>::resize
+     * [91]8399: sync_with_stdio(false) breaks unformatted input
+     * [92]8662: illegal access of private member of unnamed class is
+       accepted
+     * [93]8707: "make distclean" fails in libstdc++-v3 directory
+     * [94]8708: __USE_MALLOC doesn't work
+     * [95]8790: Use of non-thread-safe strtok in src/localename.cc
+     * [96]8887: Bug in date formats with --enable-clocale=generic
+     * [97]9076: Call Frame Instructions are not handled correctly during
+       unwind operation
+     * [98]9151: std::setprecision limited to 16 digits when outputting a
+       double to a stream
+     * [99]9168: codecvt<char, char, mbstate_t> overwrites output buffers
+     * [100]9269: libstdc++ headers: explicit specialization of function
+       must precede its first use
+     * [101]9322: return value of basic_streambuf<>::getloc affected by
+       locale::global
+     * [102]9433: segfault in runtime support for dynamic_cast
+
+    C and optimizer bugs
+
+     * [103]8032: GCC incorrectly initializes static structs that have
+       flexible arrays
+     * [104]8639: simple arithmetic expression broken
+     * [105]8794: optimization improperly eliminates certain expressions
+     * [106]8832: traditional "asm volatile" code is illegally optimized
+     * [107]8988: loop optimizer bug: with -O2, code is generated that
+       segfaults (found on i386, bug present for all platforms)
+     * [108]9492: structure copy clobbers subsequent stores to structure
+
+    Objective-C bugs
+
+     * [109]9267: Objective-C parser won't build with newer bison
+       versions (e.g. 1.875)
+
+    Ada bugs
+
+     * [110]8344: Ada build problem due to conflict between gcc/final.o,
+       gcc/ada/final.o
+
+    Preprocessor bugs
+
+     * [111]8524: _Pragma within macros is improperly expanded
+     * [112]8880: __WCHAR_TYPE__ macro incorrectly set to "long int" with
+       -fshort-wchar
+
+    ARM-specific
+
+     * [113]9090: arm ICE with >= -O2; regression from gcc-2.95
+
+    x86-specific (Intel/AMD)
+
+     * [114]8588: ICE in extract_insn, at recog.c:NNNN (shift
+       instruction)
+     * [115]8599: loop unroll bug with -march=k6-3
+     * [116]9506: ABI breakage in structure return (affects BSD and
+       Cygwin, but not GNU/Linux)
+
+    FreeBSD 5.0 specific
+
+     * [117]9484: GCC 3.2.1 Bootstrap failure on FreeBSD 5.0
+
+    RTEMS-specific
+
+     * [118]9292: hppa1.1-rtems configurery problems
+     * [119]9293: [m68k-elf/rtems] config/m68k/t-crtstuff bug
+     * [120]9295: [mips-rtems] config/mips/rtems.h init/fini issue
+     * [121]9296: gthr-rtems regression
+     * [122]9316: powerpc-rtems: extending multilibs
+
+    HP-PA specific
+
+     * [123]9493: ICE with -O2 when building a simple function
+
+    Documentation
+
+     * [124]7341: hyperlink to gcov in GCC documentation doesn't work
+     * [125]8947: Please add a warning about "-malign-double" in docs
+     * [126]7448, [127]8882: typo cleanups
+     _________________________________________________________________
+
+GCC 3.2.1
+
+   3.2.1 adds a new warning, -Wabi. This option warns when GNU C++
+   generates code that is known not to be binary-compatible with the
+   vendor-neutral ia32/ia64 ABI. Please consult the GCC manual, included
+   in the distribution, for details.
+
+   This release also removes an old GCC extension, "naming types", and
+   the documentation now directs users to use a different GCC extension,
+   __typeof__, instead. The feature had evidently been broken for a
+   while.
+
+   Otherwise, 3.2.1 is a bug fix release only; other than bug fixes and
+   the new warning there are no new features that were not present in GCC
+   3.2.
+
+   In addition, the previous fix for [128]PR 7445 (poor performance of
+   std::locale::classic() in multi-threaded applications) was reverted
+   ("unfixed"), because the "fix" was not thread-safe.
+
+  Bug Fixes
+
+   This section lists the problem reports (PRs) from GCC's bug tracking
+   system that are known to be fixed in the 3.2.1 release. This list
+   might not be complete (that is, it is possible that some PRs that have
+   been fixed are not listed here). As you can see, the number of bug
+   fixes is quite large, so it is strongly recommended that users of
+   earlier GCC 3.x releases upgrade to GCC 3.2.1.
+
+    Internal Compiler Errors (multi-platform)
+
+     * [129]2521: (c++) ICE in build_ptrmemfunc, in cp/typeck.c
+     * [130]5661: (c++) ICE instantiating template on array of unknown
+       size (bad code)
+     * [131]6419: (c++) ICE in make_decl_rtl for "longest" attribute on
+       64-bit platforms
+     * [132]6994: (c++) ICE in find_function_data
+     * [133]7150: preprocessor: GCC -dM -E gives an ICE
+     * [134]7160: ICE when optimizing branches without a return value
+     * [135]7228: (c++) ICE when using member template and template
+       function
+     * [136]7266: (c++) ICE with -pedantic on missing typename
+     * [137]7353: ICE from use of "Naming Types" extension, see above
+     * [138]7411: ICE in instantiate_virtual_regs_1, in function.c
+     * [139]7478: (c++) ICE on static_cast inside template
+     * [140]7526: preprocessor core dump when _Pragma implies #pragma
+       dependency
+     * [141]7721: (c++) ICE on simple (but incorrect) template ([142]7803
+       is a duplicate)
+     * [143]7754: (c++) ICE on union with template parameter
+     * [144]7788: (c++) redeclaring a definition as an incomplete class
+       causes ICE
+     * [145]8031: (c++) ICE in comptypes, in cp/typeck.c
+     * [146]8055: preprocessor dies with SIG11 when building FreeBSD
+       kernel
+     * [147]8067: (c++) ICE due to mishandling of __FUNCTION__ and
+       related variables
+     * [148]8134: (c++) ICE in force_store_init_value on legal code
+     * [149]8149: (c++) ICE on incomplete type
+     * [150]8160: (c++) ICE in build_modify_expr, in cp/typeck.c: array
+       initialization
+
+    C++ (compiler and library) bugs
+
+     * [151]5607: No pointer adjustment in covariant return types
+     * [152]6579: Infinite loop with statement expressions in member
+       initialization
+     * [153]6803: Default copy constructor bug in GCC 3.1
+     * [154]7176: g++ confused by friend and static member with same name
+     * [155]7188: Segfault with template class and recursive (incorrect)
+       initializer list
+     * [156]7306: Regression: GCC 3.x fails to compile code with virtual
+       inheritance if a method has a variable number of arguments
+     * [157]7461: ctype<char>::classic_table() returns offset array on
+       Cygwin
+     * [158]7524: f(const float arg[3]) fails
+     * [159]7584: Erroneous ambiguous base error on using declaration
+     * [160]7676: Member template overloading problem
+     * [161]7679: infinite loop when a right parenthesis is missing
+     * [162]7811: default locale not taken from environment
+     * [163]7961: compare( char *) implemented incorrectly in
+       basic_string<>
+     * [164]8071: basic_ostream::operator<<(streambuf*) loops forever if
+       streambuf::underflow() leaves gptr() NULL (dups: [165]8127,
+       [166]6745)
+     * [167]8096: deque::at() throws std::range_error instead of
+       std::out_of_range
+     * [168]8127: cout << cin.rdbuf() infinite loop
+     * [169]8218: Excessively large memory consumed for classes with
+       large array members
+     * [170]8287: GCC 3.2: Destructor called for non-constructed local
+       object
+     * [171]8347: empty vector range used in string construction causes
+       core dump
+     * [172]8348: fail() flag is set in istringstream when eof() flag is
+       set
+     * [173]8391: regression: infinite loop in cp/decl2.c(finish_file)
+
+    C and optimizer bugs
+
+     * [174]6627: -fno-align-functions doesn't seem to disable function
+       alignment
+     * [175]6631: life_analysis misoptimizes code to initialize fields of
+       a structure
+     * [176]7102: unsigned char division results in floating exception
+     * [177]7120: Run once loop should *always* be unrolled
+       (pessimization)
+     * [178]7209: Bug involving array referencing and ?: operator
+     * [179]7515: invalid inlining of global function with -O3
+     * [180]7814: incorrect scheduling for glibc-2.2.92 strcpy test
+     * [181]8467: bug in sibling call optimization
+
+    Preprocessor bugs
+
+     * [182]4890: incorrect line markers from the traditional
+       preprocessor
+     * [183]7357: -M option omits system headers files (making it the
+       same as -MM)
+     * [184]7358: Changes to Sun's make Dependencies
+     * [185]7602: C++ header files found in CPLUS_INCLUDE_PATH treated as
+       C headers
+     * [186]7862: Interrupting GCC -MD removes .d file but not .o
+     * [187]8190: Failed compilation deletes -MD dependency file
+     * [188]8524: _Pragma within macro is improperly expanded
+
+    x86 specific (Intel/AMD)
+
+     * [189]5351: (i686-only) function pass-by-value structure copy
+       corrupts stack ([190]7591 is a duplicate)
+     * [191]6845, [192]7034, [193]7124, [194]7174: ICE's with
+       -march=pentium3/pentium2/athlon (these are all the same underlying
+       bug, in MMX register use)
+     * [195]7134, [196]7375, [197]7390: ICE with -march=athlon (maybe
+       same as above?)
+     * [198]6890: xmmintrin.h, _MM_TRANSPOSE4_PS is broken
+     * [199]6981: wrong code in 64-bit manipulation on x86
+     * [200]7242: GCC -mcpu=pentium[23] doesn't define
+       __tune_pentiumpro__ macro
+     * [201]7396: ix86: cmpgt_ss, cmpge_ss, cmpngt_ss, and cmpnge_ss SSE
+       intrinsics are broken
+     * [202]7630: GCC 3.2 breaks on Mozilla 1.0's JS sources with
+       -march=pentium4
+     * [203]7693: Typo in i386 mmintrin.h header
+     * [204]7723: ICE - Pentium3 sse - GCC 3.2
+     * [205]7951: ICE on -march=pentium4 -O2 -mfpmath=sse
+     * [206]8146: (i686 only) gcc 3.2 miscompiles gcc 2.95.3
+
+    PowerPC specific
+
+     * [207]5967: GCC bug when profiling nested functions on powerpc
+     * [208]6984: wrong code generated with -O2, -O3, -Os for do-while
+       loop on PowerPC
+     * [209]7114: PowerPC: ICE building strcoll.op from glibc-2.2.5
+     * [210]7130: miscompiled code for GCC-3.1 in powerpc linux with
+       -funroll-all-loops
+     * [211]7133: PowerPC ICE: unrecognizable insn
+     * [212]7380: ICE in extract_insn, at recog.c:2148
+     * [213]8252: ICE on Altivec code with optimization turned on
+     * [214]8451: Altivec ICE in GCC 3.2
+
+    HP/PA specific
+
+     * [215]7250: __ashrdi3 returns wrong value on 32 bit hppa
+
+    SPARC specific
+
+     * [216]6668: when using --disable-multilib, libgcc_s.so is installed
+       in the wrong place on sparc-solaris
+     * [217]7151: ICE when compiling for UltraSPARC
+     * [218]7335: SPARC: ICE in verify_wide_reg (flow.c:557) with long
+       double and -O1
+     * [219]7842: [REGRESSION] SPARC code gen bug
+
+    ARM specific
+
+     * [220]7856: [arm] invalid offset in constant pool reference
+     * [221]7967: optimization produces wrong code (ARM)
+
+    Alpha specific
+
+     * [222]7374: __builtin_fabsl broken on alpha
+
+    IBM s390 specific
+
+     * [223]7370: ICE in fixup_var_refs_1 on s390x
+     * [224]7409: loop optimization bug on s390x-linux-gnu
+     * [225]8232: s390x: ICE when using bcmp with int length argument
+
+    SCO specific
+
+     * [226]7623: SCO OpenServer build fails with machmode.def: undefined
+       symbol: BITS_PER_UNIT
+
+    m68k/Coldfire specific
+
+     * [227]8314: crtbegin, crtend need to be multilib'ed for this
+       platform
+
+    Documentation
+
+     * [228]761: Document some undocumented options
+     * [229]5610: Fix documentation about invoking SSE instructions
+       (-mfpmath=sse)
+     * [230]7484: List -Wmissing-declarations as C-only option
+     * [231]7531: -mcmodel not documented for x86-64
+     * [232]8120: Update documentation of bad use of ##
+     _________________________________________________________________
+
+GCC 3.2
+
+   3.2 is a small bug fix release, but there is a change to the
+   application binary interface (ABI), hence the change to the second
+   part of the version number.
+
+   The main purpose of the 3.2 release is to correct a couple of problems
+   in the C++ ABI, with the intention of providing a stable interface
+   going forward.  Accordingly, 3.2 is only a small change to 3.1.1.
+
+  Bug Fixes
+
+    C++
+
+     * [233]7320: g++ 3.2 relocation problem
+     * [234]7470: vtable: virtual function pointers not in declaration
+       order
+
+    libstdc++
+
+     * [235]6410: Trouble with non-ASCII monetary symbols and wchar_t
+     * [236]6503, [237]6642, [238]7186: Problems with comparing or
+       subtracting various types of const and non-const iterators
+     * [239]7216: ambiguity with basic_iostream::traits_type
+     * [240]7220: problem with basic_istream::ignore(0,delimiter)
+     * [241]7222: locale::operator==() doesn't work on std::locale("")
+     * [242]7286: placement operator delete issue
+     * [243]7442: cxxabi.h does not match the C++ ABI
+     * [244]7445: poor performance of std::locale::classic() in
+       multi-threaded applications
+
+    x86-64 specific
+
+     * [245]7291: off-by-one in generated inline bzero code for x86-64
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [246]gnu@gnu.org. There
+   are also [247]other ways to contact the FSF.
+
+   These pages are maintained by [248]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [249]GCC manuals. If that fails, the
+    [250]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [251]gcc@gnu.org or
+    [252]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [253]Valid XHTML 1.0 
+
+References
+
+   1. http://gcc.gnu.org/gcc-3.2/changes.html#3.2.3
+   2. http://gcc.gnu.org/gcc-3.1/changes.html
+   3. http://gcc.gnu.org/gcc-3.2/c++-abi.html
+   4. http://gcc.gnu.org/PR3782
+   5. http://gcc.gnu.org/PR6440
+   6. http://gcc.gnu.org/PR7050
+   7. http://gcc.gnu.org/PR7741
+   8. http://gcc.gnu.org/PR7982
+   9. http://gcc.gnu.org/PR8068
+  10. http://gcc.gnu.org/PR8178
+  11. http://gcc.gnu.org/PR8396
+  12. http://gcc.gnu.org/PR8674
+  13. http://gcc.gnu.org/PR9768
+  14. http://gcc.gnu.org/PR9798
+  15. http://gcc.gnu.org/PR9799
+  16. http://gcc.gnu.org/PR9928
+  17. http://gcc.gnu.org/PR10114
+  18. http://gcc.gnu.org/PR10352
+  19. http://gcc.gnu.org/PR10336
+  20. http://gcc.gnu.org/PR8224
+  21. http://gcc.gnu.org/PR8613
+  22. http://gcc.gnu.org/PR8828
+  23. http://gcc.gnu.org/PR9226
+  24. http://gcc.gnu.org/PR9853
+  25. http://gcc.gnu.org/PR9797
+  26. http://gcc.gnu.org/PR9967
+  27. http://gcc.gnu.org/PR10116
+  28. http://gcc.gnu.org/PR10171
+  29. http://gcc.gnu.org/PR10175
+  30. http://gcc.gnu.org/PR8316
+  31. http://gcc.gnu.org/PR9169
+  32. http://gcc.gnu.org/PR9420
+  33. http://gcc.gnu.org/PR9459
+  34. http://gcc.gnu.org/PR9507
+  35. http://gcc.gnu.org/PR9538
+  36. http://gcc.gnu.org/PR9602
+  37. http://gcc.gnu.org/PR9993
+  38. http://gcc.gnu.org/PR10167
+  39. http://gcc.gnu.org/PR9652
+  40. http://gcc.gnu.org/PR10144
+  41. http://gcc.gnu.org/PR8746
+  42. http://gcc.gnu.org/PR9888
+  43. http://gcc.gnu.org/PR9638
+  44. http://gcc.gnu.org/PR9954
+  45. http://gcc.gnu.org/PR7784
+  46. http://gcc.gnu.org/PR7796
+  47. http://gcc.gnu.org/PR8281
+  48. http://gcc.gnu.org/PR8366
+  49. http://gcc.gnu.org/PR8726
+  50. http://gcc.gnu.org/PR9414
+  51. http://gcc.gnu.org/PR10067
+  52. http://gcc.gnu.org/PR7248
+  53. http://gcc.gnu.org/PR8343
+  54. http://gcc.gnu.org/PR9732
+  55. http://gcc.gnu.org/PR10073
+  56. http://gcc.gnu.org/PR7702
+  57. http://gcc.gnu.org/PR9671
+  58. http://gcc.gnu.org/PR8694
+  59. http://gcc.gnu.org/PR9953
+  60. http://gcc.gnu.org/PR10271
+  61. http://gcc.gnu.org/PR6362
+  62. http://gcc.gnu.org/PR10377
+  63. http://gcc.gnu.org/PR6955
+  64. http://gcc.gnu.org/PR5919
+  65. http://gcc.gnu.org/PR7129
+  66. http://gcc.gnu.org/PR7507
+  67. http://gcc.gnu.org/PR7622
+  68. http://gcc.gnu.org/PR7681
+  69. http://gcc.gnu.org/PR9528
+  70. http://gcc.gnu.org/PR8031
+  71. http://gcc.gnu.org/PR8275
+  72. http://gcc.gnu.org/PR8332
+  73. http://gcc.gnu.org/PR8372
+  74. http://gcc.gnu.org/PR8439
+  75. http://gcc.gnu.org/PR8442
+  76. http://gcc.gnu.org/PR8518
+  77. http://gcc.gnu.org/PR8615
+  78. http://gcc.gnu.org/PR8663
+  79. http://gcc.gnu.org/PR8799
+  80. http://gcc.gnu.org/PR9328
+  81. http://gcc.gnu.org/PR9465
+  82. http://gcc.gnu.org/PR47
+  83. http://gcc.gnu.org/PR6745
+  84. http://gcc.gnu.org/PR8214
+  85. http://gcc.gnu.org/PR8493
+  86. http://gcc.gnu.org/PR8332
+  87. http://gcc.gnu.org/PR8503
+  88. http://gcc.gnu.org/PR8727
+  89. http://gcc.gnu.org/PR7445
+  90. http://gcc.gnu.org/PR8230
+  91. http://gcc.gnu.org/PR8399
+  92. http://gcc.gnu.org/PR8662
+  93. http://gcc.gnu.org/PR8707
+  94. http://gcc.gnu.org/PR8708
+  95. http://gcc.gnu.org/PR8790
+  96. http://gcc.gnu.org/PR8887
+  97. http://gcc.gnu.org/PR9076
+  98. http://gcc.gnu.org/PR9151
+  99. http://gcc.gnu.org/PR9168
+ 100. http://gcc.gnu.org/PR9269
+ 101. http://gcc.gnu.org/PR9322
+ 102. http://gcc.gnu.org/PR9433
+ 103. http://gcc.gnu.org/PR8032
+ 104. http://gcc.gnu.org/PR8639
+ 105. http://gcc.gnu.org/PR8794
+ 106. http://gcc.gnu.org/PR8832
+ 107. http://gcc.gnu.org/PR8988
+ 108. http://gcc.gnu.org/PR9492
+ 109. http://gcc.gnu.org/PR9267
+ 110. http://gcc.gnu.org/PR8344
+ 111. http://gcc.gnu.org/PR8524
+ 112. http://gcc.gnu.org/PR8880
+ 113. http://gcc.gnu.org/PR9090
+ 114. http://gcc.gnu.org/PR8588
+ 115. http://gcc.gnu.org/PR8599
+ 116. http://gcc.gnu.org/PR9506
+ 117. http://gcc.gnu.org/PR9484
+ 118. http://gcc.gnu.org/PR9292
+ 119. http://gcc.gnu.org/PR9293
+ 120. http://gcc.gnu.org/PR9295
+ 121. http://gcc.gnu.org/PR9296
+ 122. http://gcc.gnu.org/PR9316
+ 123. http://gcc.gnu.org/PR9493
+ 124. http://gcc.gnu.org/PR7341
+ 125. http://gcc.gnu.org/PR8947
+ 126. http://gcc.gnu.org/PR7448
+ 127. http://gcc.gnu.org/PR8882
+ 128. http://gcc.gnu.org/PR7445
+ 129. http://gcc.gnu.org/PR2521
+ 130. http://gcc.gnu.org/PR5661
+ 131. http://gcc.gnu.org/PR6419
+ 132. http://gcc.gnu.org/PR6994
+ 133. http://gcc.gnu.org/PR7150
+ 134. http://gcc.gnu.org/PR7160
+ 135. http://gcc.gnu.org/PR7228
+ 136. http://gcc.gnu.org/PR7266
+ 137. http://gcc.gnu.org/PR7353
+ 138. http://gcc.gnu.org/PR7411
+ 139. http://gcc.gnu.org/PR7478
+ 140. http://gcc.gnu.org/PR7526
+ 141. http://gcc.gnu.org/PR7721
+ 142. http://gcc.gnu.org/PR7803
+ 143. http://gcc.gnu.org/PR7754
+ 144. http://gcc.gnu.org/PR7788
+ 145. http://gcc.gnu.org/PR8031
+ 146. http://gcc.gnu.org/PR8055
+ 147. http://gcc.gnu.org/PR8067
+ 148. http://gcc.gnu.org/PR8134
+ 149. http://gcc.gnu.org/PR8149
+ 150. http://gcc.gnu.org/PR8160
+ 151. http://gcc.gnu.org/PR5607
+ 152. http://gcc.gnu.org/PR6579
+ 153. http://gcc.gnu.org/PR6803
+ 154. http://gcc.gnu.org/PR7176
+ 155. http://gcc.gnu.org/PR7188
+ 156. http://gcc.gnu.org/PR7306
+ 157. http://gcc.gnu.org/PR7461
+ 158. http://gcc.gnu.org/PR7524
+ 159. http://gcc.gnu.org/PR7584
+ 160. http://gcc.gnu.org/PR7676
+ 161. http://gcc.gnu.org/PR7679
+ 162. http://gcc.gnu.org/PR7811
+ 163. http://gcc.gnu.org/PR7961
+ 164. http://gcc.gnu.org/PR8071
+ 165. http://gcc.gnu.org/PR8127
+ 166. http://gcc.gnu.org/PR6745
+ 167. http://gcc.gnu.org/PR8096
+ 168. http://gcc.gnu.org/PR8127
+ 169. http://gcc.gnu.org/PR8218
+ 170. http://gcc.gnu.org/PR8287
+ 171. http://gcc.gnu.org/PR8347
+ 172. http://gcc.gnu.org/PR8348
+ 173. http://gcc.gnu.org/PR8391
+ 174. http://gcc.gnu.org/PR6627
+ 175. http://gcc.gnu.org/PR6631
+ 176. http://gcc.gnu.org/PR7102
+ 177. http://gcc.gnu.org/PR7120
+ 178. http://gcc.gnu.org/PR7209
+ 179. http://gcc.gnu.org/PR7515
+ 180. http://gcc.gnu.org/PR7814
+ 181. http://gcc.gnu.org/PR8467
+ 182. http://gcc.gnu.org/PR4890
+ 183. http://gcc.gnu.org/PR7357
+ 184. http://gcc.gnu.org/PR7358
+ 185. http://gcc.gnu.org/PR7602
+ 186. http://gcc.gnu.org/PR7862
+ 187. http://gcc.gnu.org/PR8190
+ 188. http://gcc.gnu.org/PR8524
+ 189. http://gcc.gnu.org/PR5351
+ 190. http://gcc.gnu.org/PR7591
+ 191. http://gcc.gnu.org/PR6845
+ 192. http://gcc.gnu.org/PR7034
+ 193. http://gcc.gnu.org/PR7124
+ 194. http://gcc.gnu.org/PR7174
+ 195. http://gcc.gnu.org/PR7134
+ 196. http://gcc.gnu.org/PR7375
+ 197. http://gcc.gnu.org/PR7390
+ 198. http://gcc.gnu.org/PR6890
+ 199. http://gcc.gnu.org/PR6981
+ 200. http://gcc.gnu.org/PR7242
+ 201. http://gcc.gnu.org/PR7396
+ 202. http://gcc.gnu.org/PR7630
+ 203. http://gcc.gnu.org/PR7693
+ 204. http://gcc.gnu.org/PR7723
+ 205. http://gcc.gnu.org/PR7951
+ 206. http://gcc.gnu.org/PR8146
+ 207. http://gcc.gnu.org/PR5967
+ 208. http://gcc.gnu.org/PR6984
+ 209. http://gcc.gnu.org/PR7114
+ 210. http://gcc.gnu.org/PR7130
+ 211. http://gcc.gnu.org/PR7133
+ 212. http://gcc.gnu.org/PR7380
+ 213. http://gcc.gnu.org/PR8252
+ 214. http://gcc.gnu.org/PR8451
+ 215. http://gcc.gnu.org/PR7250
+ 216. http://gcc.gnu.org/PR6668
+ 217. http://gcc.gnu.org/PR7151
+ 218. http://gcc.gnu.org/PR7335
+ 219. http://gcc.gnu.org/PR7842
+ 220. http://gcc.gnu.org/PR7856
+ 221. http://gcc.gnu.org/PR7967
+ 222. http://gcc.gnu.org/PR7374
+ 223. http://gcc.gnu.org/PR7370
+ 224. http://gcc.gnu.org/PR7409
+ 225. http://gcc.gnu.org/PR8232
+ 226. http://gcc.gnu.org/PR7623
+ 227. http://gcc.gnu.org/PR8314
+ 228. http://gcc.gnu.org/PR761
+ 229. http://gcc.gnu.org/PR5610
+ 230. http://gcc.gnu.org/PR7484
+ 231. http://gcc.gnu.org/PR7531
+ 232. http://gcc.gnu.org/PR8120
+ 233. http://gcc.gnu.org/PR7320
+ 234. http://gcc.gnu.org/PR7470
+ 235. http://gcc.gnu.org/PR6410
+ 236. http://gcc.gnu.org/PR6503
+ 237. http://gcc.gnu.org/PR6642
+ 238. http://gcc.gnu.org/PR7186
+ 239. http://gcc.gnu.org/PR7216
+ 240. http://gcc.gnu.org/PR7220
+ 241. http://gcc.gnu.org/PR7222
+ 242. http://gcc.gnu.org/PR7286
+ 243. http://gcc.gnu.org/PR7442
+ 244. http://gcc.gnu.org/PR7445
+ 245. http://gcc.gnu.org/PR7291
+ 246. mailto:gnu@gnu.org
+ 247. http://www.gnu.org/home.html#ContactInfo
+ 248. http://gcc.gnu.org/about.html
+ 249. http://gcc.gnu.org/onlinedocs/
+ 250. mailto:gcc-help@gcc.gnu.org
+ 251. mailto:gcc@gnu.org
+ 252. mailto:gcc@gcc.gnu.org
+ 253. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/gcc-3.1/index.html
+
+                                  GCC 3.1
+
+   July 27, 2002
+
+   The [1]GNU project and the GCC developers are pleased to announce the
+   release of GCC 3.1.1.
+
+   The links below still apply to GCC 3.1.1.
+
+   May 15, 2002
+
+   The [2]GNU project and the GCC developers are pleased to announce the
+   release of GCC 3.1.
+
+   GCC used to stand for the GNU C Compiler, but since the compiler
+   supports several other languages aside from C, it now stands for the
+   GNU Compiler Collection.
+
+   A list of [3]successful builds is updated as new information becomes
+   available.
+
+   The GCC developers would like to thank the numerous people that have
+   contributed [4]new features, improvements, bug fixes, and other
+   changes as well as test results to GCC. This [5]amazing group of
+   volunteers is what makes GCC successful.
+
+   For additional information about GCC please refer to the [6]GCC
+   project web site or contact the [7]GCC development mailing list.
+
+   To obtain GCC please use [8]our mirror sites, one of the [9]GNU mirror
+   sites, or [10]our CVS server.
+     _________________________________________________________________
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [11]gnu@gnu.org. There
+   are also [12]other ways to contact the FSF.
+
+   These pages are maintained by [13]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [14]GCC manuals. If that fails, the
+    [15]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [16]gcc@gnu.org or
+    [17]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [18]Valid XHTML 1.0 
+
+References
+
+   1. http://www.gnu.org/
+   2. http://www.gnu.org/
+   3. http://gcc.gnu.org/gcc-3.1/buildstat.html
+   4. http://gcc.gnu.org/gcc-3.1/changes.html
+   5. http://gcc.gnu.org/onlinedocs/gcc/Contributors.html
+   6. http://gcc.gnu.org/index.html
+   7. mailto:gcc@gcc.gnu.org
+   8. http://gcc.gnu.org/mirrors.html
+   9. http://www.gnu.org/order/ftp.html
+  10. http://gcc.gnu.org/cvs.html
+  11. mailto:gnu@gnu.org
+  12. http://www.gnu.org/home.html#ContactInfo
+  13. http://gcc.gnu.org/about.html
+  14. http://gcc.gnu.org/onlinedocs/
+  15. mailto:gcc-help@gcc.gnu.org
+  16. mailto:gcc@gnu.org
+  17. mailto:gcc@gcc.gnu.org
+  18. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/gcc-3.1/changes.html
+
+                           GCC 3.1 Release Series
+                      Changes, New Features, and Fixes
+
+Additional changes in GCC 3.1.1
+
+     * A bug related to how structures and unions are returned has been
+       fixed for powerpc-*-netbsd*.
+     * An important bug in the implementation of -fprefetch-loop-arrays
+       has been fixed. Previously the optimization prefetched random
+       blocks of memory for most targets except for i386.
+     * The Java compiler now compiles Java programs much faster and also
+       works with parallel make.
+     * Nested functions have been fixed for mips*-*-netbsd*.
+     * Some missing floating point support routines have beed added for
+       mips*-*-netbsd*.
+     * This [1]message gives additional information about the bugs fixed
+       in this release.
+
+Caveats
+
+     * The -traditional C compiler option has been deprecated and will be
+       removed in GCC 3.3. (It remains possible to preprocess non-C code
+       with the traditional preprocessor.)
+     * The default debugging format for most ELF platforms (including
+       GNU/Linux and FreeBSD; notable exception is Solaris) has changed
+       from stabs to DWARF2. This requires GDB 5.1.1 or later.
+
+General Optimizer Improvements
+
+     * Jan Hubicka, SuSE Labs, together with Richard Henderson, Red Hat,
+       and Andreas Jaeger, SuSE Labs, has contributed [2]infrastructure
+       for profile driven optimizations.
+       Options -fprofile-arcs and -fbranch-probabilities can now be used
+       to improve speed of the generated code by profiling the actual
+       program behaviour on typical runs. In the absence of profile info
+       the compiler attempts to guess the profile statically.
+     * [3]SPEC2000 and SPEC95 benchmark suites are now used daily to
+       monitor performance of the generated code.
+       According to the SPECInt2000 results on an AMD Athlon CPU, the
+       code generated by GCC 3.1 is 6% faster on the average (8.2% faster
+       with profile feedback) compared to GCC 3.0. The code produced by
+       GCC 3.0 is about 2.1% faster compared to 2.95.3. Tests were done
+       using the -O2 -march=athlon command-line options.
+     * Alexandre Oliva, of Red Hat, has generalized the tree inlining
+       infrastructure developed by CodeSourcery, LLC for the C++ front
+       end, so that it is now used in the C front end too. Inlining
+       functions as trees exposes them earlier to the compiler, giving it
+       more opportunities for optimization.
+     * Support for data prefetching instructions has been added to the
+       GCC back end and several targets. A new __builtin_prefetch
+       intrinsic is available to explicitly insert prefetch instructions
+       and experimental support for loop array prefetching has been added
+       (see -fprefetch-loop-array documentation).
+     * Support for emitting debugging information for macros has been
+       added for DWARF2. It is activated using -g3.
+
+New Languages and Language specific improvements
+
+  C/C++
+
+     * A few more [4]ISO C99 features.
+     * The preprocessor is 10-50% faster than the preprocessor in GCC
+       3.0.
+     * The preprocessor's symbol table has been merged with the symbol
+       table of the C, C++ and Objective-C front ends.
+     * The preprocessor consumes less memory than the preprocessor in GCC
+       3.0, often significantly so. On normal input files, it typically
+       consumes less memory than pre-3.0 cccp-based GCC, too.
+
+  C++
+
+     * -fhonor-std and -fno-honor-std have been removed. -fno-honor-std
+       was a workaround to allow std compliant code to work with the
+       non-std compliant libstdc++-v2. libstdc++-v3 is std compliant.
+     * The C++ ABI has been fixed so that void (A::*)() const is mangled
+       as "M1AKFvvE", rather than "MK1AFvvE" as before. This change only
+       affects pointer to cv-qualified member function types.
+     * The C++ ABI has been changed to correctly handle this code:
+    struct A {
+      void operator delete[] (void *, size_t);
+    };
+
+    struct B : public A {
+    };
+
+    new B[10];
+
+       The amount of storage allocated for the array will be greater than
+       it was in 3.0, in order to store the number of elements in the
+       array, so that the correct size can be passed to operator delete[]
+       when the array is deleted. Previously, the value passed to
+       operator delete[] was unpredictable.
+       This change will only affect code that declares a two-argument
+       operator delete[] with a second parameter of type size_t in a base
+       class, and does not override that definition in a derived class.
+     * The C++ ABI has been changed so that:
+    struct A {
+      void operator delete[] (void *, size_t);
+      void operator delete[] (void *);
+    };
+
+       does not cause unnecessary storage to be allocated when an array
+       of A objects is allocated.
+       This change will only affect code that declares both of these
+       forms of operator delete[], and declared the two-argument form
+       before the one-argument form.
+     * The C++ ABI has been changed so that when a parameter is passed by
+       value, any cleanup for that parameter is performed in the caller,
+       as specified by the ia64 C++ ABI, rather than the called function
+       as before. As a result, classes with a non-trivial destructor but
+       a trivial copy constructor will be passed and returned by
+       invisible reference, rather than by bitwise copy as before.
+     * G++ now supports the "named return value optimization": for code
+       like
+    A f () {
+      A a;
+      ...
+      return a;
+    }
+
+       G++ will allocate a in the return value slot, so that the return
+       becomes a no-op. For this to work, all return statements in the
+       function must return the same variable.
+     * Improvements to the C++ library are listed in [5]the libstdc++-v3
+       FAQ.
+
+  Objective-C
+
+     * Annoying linker warnings (due to incorrect code being generated)
+       have been fixed.
+     * If a class method cannot be found, the compiler no longer issues a
+       warning if a corresponding instance method exists in the root
+       class.
+     * Forward @protocol declarations have been fixed.
+     * Loading of categories has been fixed in certain situations (GNU
+       run time only).
+     * The class lookup in the run-time library has been rewritten so
+       that class method dispatch is more than twice as fast as it used
+       to be (GNU run time only).
+
+  Java
+
+     * libgcj now includes RMI, java.lang.ref.*, javax.naming, and
+       javax.transaction.
+     * Property files and other system resources can be compiled into
+       executables which use libgcj using the new gcj --resource feature.
+     * libgcj has been ported to more platforms. In particular there is
+       now a mostly-functional mingw32 (Windows) target port.
+     * JNI and CNI invocation interfaces were implemented, so
+       gcj-compiled Java code can now be called from a C/C++ application.
+     * gcj can now use builtin functions for certain known methods, for
+       instance Math.cos.
+     * gcj can now automatically remove redundant array-store checks in
+       some common cases.
+     * The --no-store-checks optimization option was added. This can be
+       used to omit runtime store checks for code which is known not to
+       throw ArrayStoreException
+     * The following third party interface standards were added to
+       libgcj: org.w3c.dom and org.xml.sax.
+     * java.security has been merged with GNU Classpath. The new package
+       is now JDK 1.2 compliant, and much more complete.
+     * A bytecode verifier was added to the libgcj interpreter.
+     * java.lang.Character was rewritten to comply with the Unicode 3.0
+       standard, and improve performance.
+     * Partial support for many more locales was added to libgcj.
+     * Socket timeouts have been implemented.
+     * libgcj has been merged into a single shared library. There are no
+       longer separate shared libraries for the garbage collector and
+       zlib.
+     * Several performance improvements were made to gcj and libgcj:
+          + Hash synchronization (thin locks)
+          + A special allocation path for finalizer-free objects
+          + Thread-local allocation
+          + Parallel GC, and other GC tweaks
+
+  Fortran
+
+   Fortran improvements are listed in [6]the Fortran documentation.
+
+  Ada
+
+   [7]Ada Core Technologies, Inc, has contributed its GNAT Ada 95 front
+   end and associated tools. The GNAT compiler fully implements the Ada
+   language as defined by the ISO/IEC 8652 standard.
+
+   Please note that the integration of the Ada front end is still work in
+   progress.
+
+New Targets and Target Specific Improvements
+
+     * Hans-Peter Nilsson has contributed a port to [8]MMIX, the CPU
+       architecture used in new editions of Donald E. Knuth's The Art of
+       Computer Programming.
+     * [9]Axis Communications has contributed its port to the CRIS CPU
+       architecture, used in the ETRAX system-on-a-chip series. See
+       [10]Axis' developer site for technical information.
+     * Alexandre Oliva, of Red Hat, has contributed a port to the
+       [11]SuperH SH5 64-bit RISC microprocessor architecture, extending
+       the existing SH port.
+     * UltraSPARC is fully supported in 64-bit mode. The option -m64
+       enables it.
+     * For compatibility with the Sun compiler #pragma redefine_extname
+       has been implemented on Solaris.
+     * The x86 back end has had some noticeable work done to it.
+          + SuSE Labs developers Jan Hubicka, Bo Thorsen and Andreas
+            Jaeger have contributed a port to the AMD x86-64
+            architecture. For more information on x86-64 see
+            [12]http://www.x86-64.org.
+          + The compiler now supports MMX, 3DNow!, SSE, and SSE2
+            instructions. Options -mmmx, -m3dnow, -msse, and -msse2 will
+            enable the respective instruction sets. Intel C++ compatible
+            MMX/3DNow!/SSE intrinsics are implemented. SSE2 intrinsics
+            will be added in next major release.
+          + Following those improvements, targets for Pentium MMX, K6-2,
+            K6-3, Pentium III, Pentium 4, and Athlon 4 Mobile/XP/MP were
+            added. Refer to the documentation on -march= and -mcpu=
+            options for details.
+          + For those targets that support it, -mfpmath=sse will cause
+            the compiler to generate SSE/SSE2 instructions for floating
+            point math instead of x87 instructions. Usually, this will
+            lead to quicker code -- especially on the Pentium 4. Note
+            that only scalar floating point instructions are used and GCC
+            does not exploit SIMD features yet.
+          + Prefetch support has been added to the Pentium III, Pentium
+            4, K6-2, K6-3, and Athlon series.
+          + Code generated for floating point to integer conversions has
+            been improved leading to better performance of many 3D
+            applications.
+     * The PowerPC back end has added 64-bit PowerPC GNU/Linux support.
+     * C++ support for AIX has been improved.
+     * Aldy Hernandez, of Red Hat, Inc, has contributed extensions to the
+       PowerPC port supporting the AltiVec programming model (SIMD). The
+       support, though presently useful, is experimental and is expected
+       to stabilize for 3.2. The support is written to conform to
+       Motorola's AltiVec specs. See -maltivec.
+
+Obsolete Systems
+
+   Support for a number of older systems has been declared obsolete in
+   GCC 3.1. Unless there is activity to revive them, the next release of
+   GCC will have their sources permanently removed.
+
+   All configurations of the following processor architectures have been
+   declared obsolete:
+     * MIL-STD-1750A, 1750a-*-*
+     * AMD A29k, a29k-*-*
+     * Convex, c*-convex-*
+     * Clipper, clipper-*-*
+     * Elxsi, elxsi-*-*
+     * Intel i860, i860-*-*
+     * Sun picoJava, pj-*-* and pjl-*-*
+     * Western Electric 32000, we32k-*-*
+
+   Most configurations of the following processor architectures have been
+   declared obsolete, but we are preserving a few systems which may have
+   active developers. It is unlikely that the remaining systems will
+   survive much longer unless we see definite signs of port activity.
+     * Motorola 88000 except
+          + Generic a.out, m88k-*-aout*
+          + Generic SVR4, m88k-*-sysv4
+          + OpenBSD, m88k-*-openbsd*
+     * NS32k except
+          + NetBSD, ns32k-*-netbsd*
+          + OpenBSD, ns32k-*-openbsd*.
+     * ROMP except
+          + OpenBSD, romp-*-openbsd*.
+
+   Finally, only some configurations of these processor architectures are
+   being obsoleted.
+     * Alpha:
+          + OSF/1, alpha*-*-osf[123]*. (Digital Unix and Tru64 Unix, aka
+            alpha*-*-osf[45], are still supported.)
+     * ARM:
+          + RISCiX, arm-*-riscix*.
+     * i386:
+          + 386BSD, i?86-*-bsd*
+          + Chorus, i?86-*-chorusos*
+          + DG/UX, i?86-*-dgux*
+          + FreeBSD 1.x, i?86-*-freebsd1.*
+          + IBM AIX, i?86-*-aix*
+          + ISC UNIX, i?86-*-isc*
+          + Linux with pre-BFD linker, i?86-*-linux*oldld*
+          + NEXTstep, i?86-next-*
+          + OSF UNIX, i?86-*-osf1* and i?86-*-osfrose*
+          + RTEMS/coff, i?86-*-rtemscoff*
+          + RTEMS/go32, i?86-go32-rtems*
+          + Sequent/BSD, i?86-sequent-bsd*
+          + Sequent/ptx before version 3, i?86-sequent-ptx[12]* and
+            i?86-sequent-sysv3*
+          + SunOS, i?86-*-sunos*
+     * Motorola 68000:
+          + Altos, m68[k0]*-altos-*
+          + Apollo, m68[k0]*-apollo-*
+          + Apple A/UX, m68[k0]*-apple-*
+          + Bull, m68[k0]*-bull-*
+          + Convergent, m68[k0]*-convergent-*
+          + Generic SVR3, m68[k0]*-*-sysv3*
+          + ISI, m68[k0]*-isi-*
+          + LynxOS, m68[k0]*-*-lynxos*
+          + NEXT, m68[k0]*-next-*
+          + RTEMS/coff, m68[k0]*-*-rtemscoff*
+          + Sony, m68[k0]*-sony-*
+     * MIPS:
+          + DEC Ultrix, mips-*-ultrix* and mips-dec-*
+          + Generic BSD, mips-*-bsd*
+          + Generic System V, mips-*-sysv*
+          + IRIX before version 5, mips-sgi-irix[1234]*
+          + RiscOS, mips-*-riscos*
+          + Sony, mips-sony-*
+          + Tandem, mips-tandem-*
+     * SPARC:
+          + RTEMS/a.out, sparc-*-rtemsaout*.
+
+Documentation improvements
+
+     * The old manual ("Using and Porting the GNU Compiler Collection")
+       has been replaced by a users manual ("Using the GNU Compiler
+       Collection") and a separate internals reference manual ("GNU
+       Compiler Collection Internals").
+     * More complete and much improved documentation about GCC's internal
+       representation used by the C and C++ front ends.
+     * Many cleanups and improvements in general.
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [13]gnu@gnu.org. There
+   are also [14]other ways to contact the FSF.
+
+   These pages are maintained by [15]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [16]GCC manuals. If that fails, the
+    [17]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [18]gcc@gnu.org or
+    [19]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [20]Valid XHTML 1.0 
+
+References
+
+   1. http://gcc.gnu.org/ml/gcc/2002-07/msg01208.html
+   2. http://gcc.gnu.org/news/profiledriven.html
+   3. http://gcc.gnu.org/benchmarks/
+   4. http://gcc.gnu.org/gcc-3.1/c99status.html
+   5. http://gcc.gnu.org/onlinedocs/libstdc++/faq/index.html#4_1
+   6. http://gcc.gnu.org/onlinedocs/g77/News.html
+   7. http://www.gnat.com/
+   8. http://www-cs-faculty.stanford.edu/~knuth/mmix.html
+   9. http://www.axis.com/
+  10. http://developer.axis.com/
+  11. http://www.superh.com/
+  12. http://www.x86-64.org/
+  13. mailto:gnu@gnu.org
+  14. http://www.gnu.org/home.html#ContactInfo
+  15. http://gcc.gnu.org/about.html
+  16. http://gcc.gnu.org/onlinedocs/
+  17. mailto:gcc-help@gcc.gnu.org
+  18. mailto:gcc@gnu.org
+  19. mailto:gcc@gcc.gnu.org
+  20. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/gcc-3.0/gcc-3.0.html
+
+                                 GCC 3.0.4
+
+   February 20, 2002
+
+   The [1]GNU project and the GCC developers are pleased to announce the
+   release of GCC 3.0.4, which is a bug-fix release for the GCC 3.0
+   series.
+
+   GCC used to stand for the GNU C Compiler, but since the compiler
+   supports several other languages aside from C, it now stands for the
+   GNU Compiler Collection.
+
+   GCC 3.0.x has several new optimizations, new targets, new languages
+   and many other new features, relative to GCC 2.95.x. See the [2]new
+   features page for a more complete list.
+
+   A list of [3]successful builds is updated as new information becomes
+   available.
+
+   The GCC developers would like to thank the numerous people that have
+   contributed new features, test results, bugfixes, etc to GCC. This
+   [4]amazing group of volunteers is what makes GCC successful.
+
+   And finally, we can't in good conscience fail to mention some
+   [5]caveats to using GCC 3.0.x.
+
+   For additional information about GCC please refer to the [6]GCC
+   project web site or contact the [7]GCC development mailing list.
+
+   To obtain GCC please use [8]our mirror sites, one of the [9]GNU mirror
+   sites, or [10]our CVS server.
+     _________________________________________________________________
+
+Previous 3.0.x Releases
+
+   December 20, 2001: GCC 3.0.3 has been released.
+   October 25, 2001: GCC 3.0.2 has been released.
+   August 20, 2001: GCC 3.0.1 has been released.
+   June 18, 2001: GCC 3.0 has been released.
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [11]gnu@gnu.org. There
+   are also [12]other ways to contact the FSF.
+
+   These pages are maintained by [13]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [14]GCC manuals. If that fails, the
+    [15]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [16]gcc@gnu.org or
+    [17]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [18]Valid XHTML 1.0 
+
+References
+
+   1. http://www.gnu.org/
+   2. http://gcc.gnu.org/gcc-3.0/features.html
+   3. http://gcc.gnu.org/gcc-3.0/buildstat.html
+   4. http://gcc.gnu.org/onlinedocs/gcc/Contributors.html
+   5. http://gcc.gnu.org/gcc-3.0/caveats.html
+   6. http://gcc.gnu.org/index.html
+   7. mailto:gcc@gcc.gnu.org
+   8. http://gcc.gnu.org/mirrors.html
+   9. http://www.gnu.org/order/ftp.html
+  10. http://gcc.gnu.org/cvs.html
+  11. mailto:gnu@gnu.org
+  12. http://www.gnu.org/home.html#ContactInfo
+  13. http://gcc.gnu.org/about.html
+  14. http://gcc.gnu.org/onlinedocs/
+  15. mailto:gcc-help@gcc.gnu.org
+  16. mailto:gcc@gnu.org
+  17. mailto:gcc@gcc.gnu.org
+  18. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/gcc-3.0/features.html
+
+                            GCC 3.0 New Features
+
+Additional changes in GCC 3.0.4
+
+     * GCC 3.0 now supports newer versions of the [1]NetBSD operating
+       system, which use the ELF object file format, on x86 processors.
+     * Correct debugging information is generated from functions that
+       have lines from multiple files (e.g. yacc output).
+     * A fix for whitespace handling in the -traditional preprocessor,
+       which can affect Fortran.
+     * Fixes to the exception handling runtime.
+     * More fixes for bad code generation in C++.
+     * A fix for shared library generation under AIX 4.3.
+     * Documentation updates.
+     * Port of GCC to Tensilica's Xtensa processor contributed.
+     * A fix for compiling the PPC Linux kernel (FAT fs wouldn't link).
+
+Additional changes in GCC 3.0.3
+
+     * A fix to correct an accidental change to the PowerPC ABI.
+     * Fixes for bad code generation on a variety of architectures.
+     * Improvements to the debugging information generated for C++
+       classes.
+     * Fixes for bad code generation in C++.
+     * A fix to avoid crashes in the C++ demangler.
+     * A fix to the C++ standard library to avoid buffer overflows.
+     * Miscellaneous improvements for a variety of architectures.
+
+Additional changes in GCC 3.0.2
+
+     * Fixes for bad code generation during loop unrolling.
+     * Fixes for bad code generation by the sibling call optimization.
+     * Minor improvements to x86 code generation.
+     * Implementation of function descriptors in C++ vtables for IA64.
+     * Numerous minor bug-fixes.
+
+Additional changes in GCC 3.0.1
+
+     * C++ fixes for incorrect code-generation.
+     * Improved cross-compiling support for the C++ standard library.
+     * Fixes for some embedded targets that worked in GCC 2.95.3, but not
+       in GCC 3.0.
+     * Fixes for various exception-handling bugs.
+     * A port to the S/390 architecture.
+
+General Optimizer Improvements
+
+     * [2]Basic block reordering pass.
+     * New if-conversion pass with support for conditional (predicated)
+       execution.
+     * New tail call and sibling call elimination optimizations.
+     * New register renaming pass.
+     * New (experimental) [3]static single assignment (SSA)
+       representation support.
+     * New dead-code elimination pass implemented using the SSA
+       representation.
+     * [4]Global null pointer test elimination.
+     * [5]Global code hoisting/unification.
+     * More builtins and optimizations for stdio.h, string.h and old BSD
+       functions, as well as for ISO C99 functions.
+     * New builtin __builtin_expect for giving hints to the branch
+       predictor.
+
+New Languages and Language specific improvements
+
+     * The GNU Compiler for the Java(TM) language (GCJ) is now integrated
+       and supported, including the run-time library containing most
+       common non-GUI Java classes, a bytecode interpreter, and the Boehm
+       conservative garbage collector. Many bugs have been fixed. GCJ can
+       compile Java source or Java bytecodes to either native code or
+       Java class files, and supports native methods written in either
+       the standard JNI or the more efficient and convenient CNI.
+     * Here is a [6]partial list of C++ improvements, both new features
+       and those no longer supported.
+     * New C++ ABI. On the IA-64 platform GCC is capable of
+       inter-operating with other IA-64 compilers.
+     * The new ABI also significantly reduces the size of symbol and
+       debug information.
+     * New [7]C++ support library and many C++ bug fixes, vastly
+       improving our conformance to the ISO C++ standard.
+     * New [8]inliner for C++.
+     * Rewritten C preprocessor, integrated into the C, C++ and Objective
+       C compilers, with very many improvements including ISO C99 support
+       and [9]improvements to dependency generation.
+     * Support for more [10]ISO C99 features.
+     * Many improvements to support for checking calls to format
+       functions such as printf and scanf, including support for ISO C99
+       format features, extensions from the Single Unix Specification and
+       GNU libc 2.2, checking of strfmon formats and features to assist
+       in auditing for format string security bugs.
+     * New warnings for C code that may have undefined semantics because
+       of violations of sequence point rules in the C standard (such as a
+       = a++;, a[n] = b[n++]; and a[i++] = i;), included in -Wall.
+     * Additional warning option -Wfloat-equal.
+     * Improvements to -Wtraditional.
+     * Fortran improvements are listed in [11]the Fortran documentation.
+
+New Targets and Target Specific Improvements
+
+     * New x86 back-end, generating much improved code.
+     * Support for a generic i386-elf target contributed.
+     * New option to emit x86 assembly code using Intel style syntax
+       (-mintel-syntax).
+     * HPUX 11 support contributed.
+     * Improved PowerPC code generation, including scheduled prologue and
+       epilogue.
+     * Port of GCC to Intel's IA-64 processor contributed.
+     * Port of GCC to Motorola's MCore 210 and 340 contributed.
+     * New unified back-end for Arm, Thumb and StrongArm contributed.
+     * Port of GCC to Intel's XScale processor contributed.
+     * Port of GCC to Atmel's AVR microcontrollers contributed.
+     * Port of GCC to Mitsubishi's D30V processor contributed.
+     * Port of GCC to Matsushita's AM33 processor (a member of the
+       MN10300 processor family) contributed.
+     * Port of GCC to Fujitsu's FR30 processor contributed.
+     * Port of GCC to Motorola's 68HC11 and 68HC12 processors
+       contributed.
+     * Port of GCC to Sun's picoJava processor core contributed.
+
+Documentation improvements
+
+     * Substantially rewritten and improved C preprocessor manual.
+     * Many improvements to other documentation.
+     * Manpages for gcc, cpp and gcov are now generated automatically
+       from the master Texinfo manual, eliminating the problem of
+       manpages being out of date. (The generated manpages are only
+       extracts from the full manual, which is provided in Texinfo form,
+       from which info, HTML, other formats and a printed manual can be
+       generated.)
+     * Generated info files are included in the release tarballs
+       alongside their Texinfo sources, avoiding problems on some
+       platforms with building makeinfo as part of the GCC distribution.
+
+Other significant improvements
+
+     * Garbage collection used internally by the compiler for most memory
+       allocation instead of obstacks.
+     * Lengauer and Tarjan algorithm used for computing dominators in the
+       CFG. This algorithm can be significantly faster and more space
+       efficient than our older algorithm.
+     * gccbug script provided to assist in submitting bug reports to our
+       bug tracking system. (Bug reports previously submitted directly to
+       our mailing lists, for which you received no bug tracking number,
+       should be submitted again using gccbug if you can reproduce the
+       problem with GCC 3.0.)
+     * The internal libgcc library is [12]built as a shared library on
+       systems that support it.
+     * Extensive testsuite included with GCC, with many new tests. In
+       addition to tests for GCC bugs that have been fixed, many tests
+       have been added for language features, compiler warnings and
+       builtin functions.
+     * Additional language-independent warning options -Wpacked,
+       -Wpadded, -Wunreachable-code and -Wdisabled-optimization.
+     * Target-independent options -falign-functions, -falign-loops and
+       -falign-jumps.
+
+   Plus a great many bugfixes and almost all the [13]features found in
+   GCC 2.95.
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [14]gnu@gnu.org. There
+   are also [15]other ways to contact the FSF.
+
+   These pages are maintained by [16]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [17]GCC manuals. If that fails, the
+    [18]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [19]gcc@gnu.org or
+    [20]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [21]Valid XHTML 1.0 
+
+References
+
+   1. http://www.netbsd.org/
+   2. http://gcc.gnu.org/news/reorder.html
+   3. http://gcc.gnu.org/news/ssa.html
+   4. http://gcc.gnu.org/news/null.html
+   5. http://gcc.gnu.org/news/unify.html
+   6. http://gcc.gnu.org/gcc-3.0/c++features.html
+   7. http://gcc.gnu.org/libstdc++/
+   8. http://gcc.gnu.org/news/inlining.html
+   9. http://gcc.gnu.org/news/dependencies.html
+  10. http://gcc.gnu.org/gcc-3.0/c99status.html
+  11. http://gcc.gnu.org/onlinedocs/g77/News.html
+  12. http://gcc.gnu.org/gcc-3.0/libgcc.html
+  13. http://gcc.gnu.org/gcc-2.95/features.html
+  14. mailto:gnu@gnu.org
+  15. http://www.gnu.org/home.html#ContactInfo
+  16. http://gcc.gnu.org/about.html
+  17. http://gcc.gnu.org/onlinedocs/
+  18. mailto:gcc-help@gcc.gnu.org
+  19. mailto:gcc@gnu.org
+  20. mailto:gcc@gcc.gnu.org
+  21. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/gcc-3.0/caveats.html
+
+                              GCC 3.0 Caveats
+
+     * -fstrict-aliasing is now part of -O2 and higher optimization
+       levels. This allows the compiler to assume the strictest aliasing
+       rules applicable to the language being compiled. For C and C++,
+       this activates optimizations based on the type of expressions.
+       This optimization may thus break old, non-compliant code.
+     * Enumerations are now properly promoted to int in function
+       parameters and function returns. Normally this change is not
+       visible, but when using -fshort-enums this is an ABI change.
+     * The undocumented extension that allowed C programs to have a label
+       at the end of a compound statement has been deprecated and may be
+       removed in a future version. Programs that now generate a warning
+       about this may be fixed by adding a null statement (a single
+       semicolon) after the label.
+     * The poorly documented extension that allowed string constants in
+       C, C++ and Objective C to contain unescaped newlines has been
+       deprecated and may be removed in a future version. Programs using
+       this extension may be fixed in several ways: the bare newline may
+       be replaced by \n, or preceded by \n\, or string concatenation may
+       be used with the bare newline preceded by \n" and " placed at the
+       start of the next line.
+     * The Chill compiler is not included in GCC 3.0, because of the lack
+       of a volunteer to convert it to use garbage collection.
+     * Certain non-standard iostream methods from earlier versions of
+       libstdc++ are not included in libstdc++ v3, i.e. filebuf::attach,
+       ostream::form, and istream::gets. Here are workaround hints for:
+       [1]ostream::form, [2]filebuf::attach.
+     * The new C++ ABI is not yet fully supported by current (as of
+       2001-07-01) releases and development versions of GDB, or any
+       earlier versions. There is a problem setting breakpoints by line
+       number, and other related issues that have been fixed in GCC 3.0
+       but not yet handled in GDB:
+       [3]http://gcc.gnu.org/ml/gcc-bugs/2001-06/msg00421.html
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [4]gnu@gnu.org. There
+   are also [5]other ways to contact the FSF.
+
+   These pages are maintained by [6]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [7]GCC manuals. If that fails, the
+    [8]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [9]gcc@gnu.org or
+    [10]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [11]Valid XHTML 1.0 
+
+References
+
+   1. http://gcc.gnu.org/onlinedocs/libstdc++/21_strings/howto.html
+   2. http://gcc.gnu.org/onlinedocs/libstdc++/ext/howto.html
+   3. http://gcc.gnu.org/ml/gcc-bugs/2001-06/msg00421.html
+   4. mailto:gnu@gnu.org
+   5. http://www.gnu.org/home.html#ContactInfo
+   6. http://gcc.gnu.org/about.html
+   7. http://gcc.gnu.org/onlinedocs/
+   8. mailto:gcc-help@gcc.gnu.org
+   9. mailto:gcc@gnu.org
+  10. mailto:gcc@gcc.gnu.org
+  11. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/gcc-2.95/index.html
+
+                                  GCC 2.95
+
+   July 31, 1999: The GNU project and the GCC/EGCS developers are pleased
+   to announce the release of GCC version 2.95. This is the first release
+   of GCC since the April 1999 GCC/EGCS reunification and includes nearly
+   a year's worth of new development and bugfixes.
+
+   August 19, 1999: GCC version 2.95.1 has been released.
+
+   October 27, 1999: GCC version 2.95.2 has been released.
+
+   March 16, 2001: GCC version 2.95.3 has been released.
+
+   GCC used to stand for the GNU C Compiler, but since the compiler
+   supports several other languages aside from C, it now stands for the
+   GNU Compiler Collection.
+
+   The whole suite has been extensively [1]regression tested and
+   [2]package tested. It should be reliable and suitable for widespread
+   use.
+
+   The compiler has several new optimizations, new targets, new languages
+   and other new features. See the [3]new features page for a more
+   complete list of new features found in the GCC 2.95 releases.
+
+   The sources include installation instructions in both HTML and
+   plaintext forms in the install directory in the distribution. However,
+   the most up to date [4]installation instructions and [5]build/test
+   status are on the web pages. We will update those pages as new
+   information becomes available.
+
+   The GCC developers would like to thank the numerous people that have
+   contributed new features, test results, bugfixes, etc to GCC. This
+   [6]amazing group of volunteers is what makes GCC successful.
+
+   And finally, we can't in good conscience fail to mention some
+   [7]caveats to using GCC 2.95.
+
+   Download GCC 2.95 from the [8]GNU FTP server (ftp://ftp.gnu.org)
+   [9]Find a GNU mirror site
+   [10]Find a GCC mirror site
+
+   For additional information about GCC please see the [11]GCC project
+   web server or contact the [12]GCC development mailing list.
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [13]gnu@gnu.org. There
+   are also [14]other ways to contact the FSF.
+
+   These pages are maintained by [15]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [16]GCC manuals. If that fails, the
+    [17]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [18]gcc@gnu.org or
+    [19]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [20]Valid XHTML 1.0 
+
+References
+
+   1. http://gcc.gnu.org/gcc-2.95/regress.html
+   2. http://gcc.gnu.org/gcc-2.95/othertest.html
+   3. http://gcc.gnu.org/gcc-2.95/features.html
+   4. http://gcc.gnu.org/install/
+   5. http://gcc.gnu.org/gcc-2.95/buildstat.html
+   6. http://gcc.gnu.org/onlinedocs/gcc/Contributors.html
+   7. http://gcc.gnu.org/gcc-2.95/caveats.html
+   8. ftp://ftp.gnu.org/pub/gnu/gcc/
+   9. http://www.gnu.org/order/ftp.html
+  10. http://gcc.gnu.org/mirrors.html
+  11. http://gcc.gnu.org/index.html
+  12. mailto:gcc@gcc.gnu.org
+  13. mailto:gnu@gnu.org
+  14. http://www.gnu.org/home.html#ContactInfo
+  15. http://gcc.gnu.org/about.html
+  16. http://gcc.gnu.org/onlinedocs/
+  17. mailto:gcc-help@gcc.gnu.org
+  18. mailto:gcc@gnu.org
+  19. mailto:gcc@gcc.gnu.org
+  20. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/gcc-2.95/features.html
+
+                           GCC 2.95 New Features
+
+     * General Optimizer Improvements:
+          + [1]Localized register spilling to improve speed and code
+            density especially on small register class machines.
+          + [2]Global CSE using lazy code motion algorithms.
+          + [3]Improved global constant/copy propagation.
+          + [4]Improved control flow graph analysis and manipulation.
+          + [5]Local dead store elimination.
+          + [6]Memory Load hoisting/store sinking in loops.
+          + [7]Type based alias analysis is enabled by default. Note this
+            feature will expose bugs in the Linux kernel. Please refer to
+            the FAQ (as shipped with GCC 2.95) for additional information
+            on this issue.
+          + Major revamp of GIV detection, combination and simplification
+            to improve loop performance.
+          + Major improvements to register allocation and reloading.
+     * New Languages and Language specific improvements
+          + [8]Many C++ improvements.
+          + [9]Many Fortran improvements.
+          + [10]Java front-end has been integrated. [11]runtime library
+            is available separately.
+          + [12]ISO C99 support
+          + [13]Chill front-end and runtime has been integrated.
+          + Boehm garbage collector support in libobjc.
+          + More support for various pragmas which appear in vendor
+            include files
+     * New Targets and Target Specific Improvements
+          + [14]Sparc backend rewrite.
+          + -mschedule=8000 will optimize code for PA8000 class
+            processors; -mpa-risc-2-0 will generate code for PA2.0
+            processors
+          + Various micro-optimizations for the ia32 port. K6
+            optimizations
+          + Compiler will attempt to align doubles in the stack on the
+            ia32 port
+          + Alpha EV6 support
+          + PowerPC 750
+          + RS6000/PowerPC: -mcpu=401 was added as an alias for
+            -mcpu=403. -mcpu=e603e was added to do -mcpu=603e and
+            -msoft-float.
+          + c3x, c4x
+          + HyperSparc
+          + SparcLite86x
+          + sh4
+          + Support for new systems (OpenBSD, FreeBSD, UWIN, Interix,
+            arm-linux)
+          + vxWorks targets include support for vxWorks threads
+          + StrongARM 110 and ARM9 support added. ARM Scheduling
+            parameters rewritten.
+          + Various changes to the MIPS port to avoid assembler macros,
+            which in turn improves performance
+          + Various performance improvements to the i960 port.
+          + Major rewrite of ns32k port
+     * Other significant improvements
+          + [15]Ability to dump cfg information and display it using vcg.
+          + The new faster scheme for fixing vendor header files is
+            enabled by default.
+          + Experimental internationalization support.
+          + multibyte character support
+          + Some compile-time speedups for pathological problems
+          + Better support for complex types
+     * Plus the usual mountain of bugfixes
+     * Core compiler is based on the gcc2 development tree from Sept 30,
+       1998, so we have all of the [16]features found in GCC 2.8.
+
+Additional Changes in GCC 2.95.1
+
+     * Generic bugfixes and improvements
+          + Various documentation fixes related to the GCC/EGCS merger.
+          + Fix memory management bug which could lead to spurious
+            aborts, core dumps or random parsing errors in the compiler.
+          + Fix a couple bugs in the dwarf1 and dwarf2 debug record
+            support.
+          + Fix infinite loop in the CSE optimizer.
+          + Avoid undefined behavior in compiler FP emulation code
+          + Fix install problem when prefix is overridden on the make
+            install command.
+          + Fix problem with unwanted installation of assert.h on some
+            systems.
+          + Fix problem with finding the wrong assembler in a single tree
+            build.
+          + Avoid increasing the known alignment of a register that is
+            already known to be a pointer.
+     * Platform specific bugfixes and improvements
+          + Codegen bugfix for prologue/epilogue for cpu32 target.
+          + Fix long long code generation bug for the Coldfire target.
+          + Fix various aborts in the SH compiler.
+          + Fix bugs in libgcc support library for the SH.
+          + Fix alpha ev6 code generation bug.
+          + Fix problems with EXIT_SUCCESS/EXIT_FAILURE redefinitions on
+            AIX platforms.
+          + Fix -fpic code generation bug for rs6000/ppc svr4 targets.
+          + Fix varargs/stdarg code generation bug for rs6000/ppc svr4
+            targets.
+          + Fix weak symbol handling for rs6000/ppc svr4 targets.
+          + Fix various problems with 64bit code generation for the
+            rs6000/ppc port.
+          + Fix codegen bug which caused tetex to be mis-compiled on the
+            x86.
+          + Fix compiler abort in new cfg code exposed by x86 port.
+          + Fix out of range array reference in code convert flat
+            registers to the x87 stacked FP register file.
+          + Fix minor vxworks configuration bug.
+          + Fix return type of bsearch for SunOS 4.x.
+     * Language & Runtime specific fixes.
+          + The G++ signature extension has been deprecated. It will be
+            removed in the next major release of G++. Use of signatures
+            will result in a warning from the compiler.
+          + Several bugs relating to templates and namespaces were fixed.
+          + A bug that caused crashes when combining templates with -g on
+            DWARF1 platforms was fixed.
+          + Pointers-to-members, virtual functions, and multiple
+            inheritance should now work together correctly.
+          + Some code-generation bugs relating to function try blocks
+            were fixed.
+          + G++ is a little bit more lenient with certain archaic
+            constructs than in GCC 2.95.
+          + Fix to prevent shared library version #s from bring truncated
+            to 1 digit
+          + Fix missing std:: in the libstdc++ library.
+          + Fix stream locking problems in libio.
+          + Fix problem in java compiler driver.
+
+Additional Changes in GCC 2.95.2
+
+   The -fstrict-aliasing is not enabled by default for GCC 2.95.2. While
+   the optimizations performed by -fstrict-aliasing are valid according
+   to the C and C++ standards, the optimization have caused some
+   problems, particularly with old non-conforming code.
+
+   The GCC developers are experimenting with ways to warn users about
+   code 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.
+
+   We strongly encourage developers to find and fix code which violates
+   the C/C++ standards as -fstrict-aliasing may be enabled by default in
+   future releases. Use the option -fstrict-aliasing to re-enable these
+   optimizations.
+     * Generic bugfixes and improvements
+          + Fix incorrectly optimized memory reference in global common
+            subexpression elimination (GCSE) optimization pass.
+          + Fix code generation bug in regmove.c in which it could
+            incorrectly change a "const" value.
+          + Fix bug in optimization of conditionals involving volatile
+            memory references.
+          + Avoid over-allocation of stack space for some procedures.
+          + Fixed bug in the compiler which caused incorrect optimization
+            of an obscure series of bit manipulations, shifts and
+            arithmetic.
+          + Fixed register allocator bug which caused teTeX to be
+            mis-compiled on Sparc targets.
+          + Avoid incorrect optimization of degenerate case statements
+            for certain targets such as the ARM.
+          + Fix out of range memory reference in the jump optimizer.
+          + Avoid dereferencing null pointer in fix-header.
+          + Fix test for GCC specific features so that it is possible to
+            bootstrap with gcc-2.6.2 and older versions of GCC.
+          + Fix typo in scheduler which could potentially cause out of
+            range memory accesses.
+          + Avoid incorrect loop reversal which caused incorrect code for
+            certain loops on PowerPC targets.
+          + Avoid incorrect optimization of switch statements on certain
+            targets (for example the ARM).
+     * Platform specific bugfixes and improvements
+          + Work around bug in Sun V5.0 compilers which caused bootstrap
+            comparison failures on Sparc targets.
+          + Fix Sparc backend bug which caused aborts in final.c.
+          + Fix sparc-hal-solaris2* configuration fragments.
+          + Fix bug in sparc block profiling.
+          + Fix obscure code generation bug for the PARISC targets.
+          + Define __STDC_EXT__ for HPUX configurations.
+          + Various POWERPC64 code generation bugfixes.
+          + Fix abort for PPC targets using ELF (ex GNU/Linux).
+          + Fix collect2 problems for AIX targets.
+          + Correct handling of .file directive for PPC targets.
+          + Fix bug in fix_trunc x86 patterns.
+          + Fix x86 port to correctly pop the FP stack for functions that
+            return structures in memory.
+          + Fix minor bug in strlen x86 pattern.
+          + Use stabs debugging instead of dwarf1 for x86-solaris
+            targets.
+          + Fix template repository code to handle leading underscore in
+            mangled names.
+          + Fix weak/weak alias support for OpenBSD.
+          + GNU/Linux for the ARM has C++ compatible include files.
+     * Language & Runtime specific fixes.
+          + Fix handling of constructor attribute in the C front-end
+            which caused problems building the Chill runtime library on
+            some targets.
+          + Fix minor problem merging type qualifiers in the C front-end.
+          + Fix aliasing bug for pointers and references (C/C++).
+          + Fix incorrect "non-constant initializer bug" when
+            -traditional or -fwritable-strings is enabled.
+          + Fix build error for Chill front-end on SunOS.
+          + Do not complain about duplicate instantiations when using
+            -frepo (C++).
+          + Fix array bounds handling in C++ front-end which caused
+            problems with dwarf debugging information in some
+            circumstances.
+          + Fix minor namespace problem.
+          + Fix problem linking java programs.
+
+Additional Changes in GCC 2.95.3
+
+     * Generic bugfixes and improvements
+          + Fix numerous problems that caused incorrect optimization in
+            the register reloading code.
+          + Fix numerous problems that caused incorrect optimization in
+            the loop optimizer.
+          + Fix aborts in the functions build_insn_chain and scan_loops
+            under some circumstances.
+          + Fix an alias analysis bug.
+          + Fix an infinite compilation bug in the combiner.
+          + A few problems with complex number support have been fixed.
+          + It is no longer possible for gcc to act as a fork bomb when
+            installed incorrectly.
+          + The -fpack-struct option should be recognized now.
+          + Fixed a bug that caused incorrect code to be generated due to
+            a lost stack adjustment.
+     * Platform specific bugfixes and improvements
+          + Support building ARM toolchains hosted on Windows.
+          + Fix attribute calculations in ARM toolchains.
+          + arm-linux support has been improved.
+          + Fix a PIC failure on sparc targets.
+          + On ix86 targets, the regparm attribute should now work
+            reliably.
+          + Several updates for the h8300 port.
+          + Fix problem building libio with glibc 2.2.
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [17]gnu@gnu.org. There
+   are also [18]other ways to contact the FSF.
+
+   These pages are maintained by [19]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [20]GCC manuals. If that fails, the
+    [21]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [22]gcc@gnu.org or
+    [23]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [24]Valid XHTML 1.0 
+
+References
+
+   1. http://gcc.gnu.org/news/spill.html
+   2. http://gcc.gnu.org/news/lcm.html
+   3. http://gcc.gnu.org/news/cprop.html
+   4. http://gcc.gnu.org/news/cfg.html
+   5. http://gcc.gnu.org/news/dse.html
+   6. http://gcc.gnu.org/news/hoist.html
+   7. http://gcc.gnu.org/news/alias.html
+   8. http://gcc.gnu.org/gcc-2.95/c++features.html
+   9. http://gcc.gnu.org/onlinedocs/g77/News.html
+  10. http://gcc.gnu.org/java/gcj-announce.txt
+  11. http://gcc.gnu.org/news/javaannounce.html
+  12. http://gcc.gnu.org/c99status.html
+  13. http://gcc.gnu.org/news/chill.html
+  14. http://gcc.gnu.org/news/sparc.html
+  15. http://gcc.gnu.org/news/egcs-vcg.html
+  16. http://gcc.gnu.org/egcs-1.0/features-2.8.html
+  17. mailto:gnu@gnu.org
+  18. http://www.gnu.org/home.html#ContactInfo
+  19. http://gcc.gnu.org/about.html
+  20. http://gcc.gnu.org/onlinedocs/
+  21. mailto:gcc-help@gcc.gnu.org
+  22. mailto:gcc@gnu.org
+  23. mailto:gcc@gcc.gnu.org
+  24. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/gcc-2.95/caveats.html
+
+                              GCC 2.95 Caveats
+
+     * 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 FAQ (as shipped with
+       GCC 2.95) for more information on this issue.
+     * GCC 2.95 implements type based alias analysis to disambiguate
+       memory references. Some programs, particularly the Linux kernel
+       violate ANSI/ISO aliasing rules and therefore may not operate
+       correctly when compiled with GCC 2.95. Please refer to the FAQ (as
+       shipped with GCC 2.95) for more information on this issue.
+     * GCC 2.95 has a known bug in its handling of complex variables for
+       64bit targets. Instead of silently generating incorrect code, GCC
+       2.95 will issue a fatal error for situations it can not handle.
+       This primarily affects the Fortran community as Fortran makes more
+       use of complex variables than C or C++.
+     * GCC 2.95 has an integrated libstdc++, but does not have an
+       integrated libg++. Furthermore old libg++ releases will not work
+       with GCC 2.95. You can retrieve a recent copy of libg++ from the
+       [1]GCC ftp server.
+       Note most C++ programs only need libstdc++.
+     * Exception handling may not work with shared libraries,
+       particularly on alphas, hppas, rs6000/powerpc and mips based
+       platforms. Exception handling is known to work on x86 GNU/Linux
+       platforms with shared libraries.
+     * In general, GCC 2.95 is more rigorous about rejecting invalid C++
+       code or deprecated C++ constructs than G++ 2.7, G++ 2.8, EGCS 1.0,
+       or EGCS 1.1. As a result it may be necessary to fix C++ code
+       before it will compile with GCC 2.95.
+     * G++ is also converting toward the ISO C++ standard; as a result
+       code which was previously valid (and thus accepted by other
+       compilers and older versions of g++) may no longer be accepted.
+       The flag -fpermissive may allow some non-conforming code to
+       compile with GCC 2.95.
+     * GCC 2.95 compiled C++ code is not binary compatible with EGCS
+       1.1.x, EGCS 1.0.x or GCC 2.8.x.
+     * GCC 2.95 does not have changes from the GCC 2.8 tree that were
+       made between Sept 30, 1998 and April 30, 1999 (the official end of
+       the GCC 2.8 project). Future GCC releases will include all the
+       changes from the defunct GCC 2.8 sources.
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [2]gnu@gnu.org. There
+   are also [3]other ways to contact the FSF.
+
+   These pages are maintained by [4]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [5]GCC manuals. If that fails, the
+    [6]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [7]gcc@gnu.org or
+    [8]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [9]Valid XHTML 1.0 
+
+References
+
+   1. ftp://gcc.gnu.org/pub/gcc/infrastructure/libg++-2.8.1.3.tar.gz
+   2. mailto:gnu@gnu.org
+   3. http://www.gnu.org/home.html#ContactInfo
+   4. http://gcc.gnu.org/about.html
+   5. http://gcc.gnu.org/onlinedocs/
+   6. mailto:gcc-help@gcc.gnu.org
+   7. mailto:gcc@gnu.org
+   8. mailto:gcc@gcc.gnu.org
+   9. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/egcs-1.1/index.html
+
+                                  EGCS 1.1
+
+   September 3, 1998: We are pleased to announce the release of EGCS 1.1.
+   December 1, 1998: We are pleased to announce the release of EGCS
+   1.1.1.
+   March 15, 1999: We are pleased to announce the release of EGCS 1.1.2.
+
+   EGCS is a free software project to further the development of the GNU
+   compilers using an open development environment.
+
+   EGCS 1.1 is a major new release of the EGCS compiler system. It has
+   been [1]extensively tested and is believed to be stable and suitable
+   for widespread use.
+
+   EGCS 1.1 is based on an June 6, 1998 snapshot of the GCC 2.8
+   development sources; it contains all of the new features found in GCC
+   2.8.1 as well as all new development from GCC up to June 6, 1998.
+
+   EGCS 1.1 also contains many improvements and features not found in GCC
+   or in older versions of EGCS:
+     * Global common subexpression elimination and global constant/copy
+       propagation (aka [2]gcse)
+     * Ongoing improvements to the [3]alias analysis support to allow for
+       better optimizations throughout the compiler.
+     * Vastly improved [4]C++ compiler and integrated C++ runtime
+       libraries.
+     * Fixes for the /tmp symlink race security problems.
+     * New targets including mips16, arm-thumb and 64 bit PowerPC.
+     * Improvements to GNU Fortran (g77) compiler and runtime library
+       made since g77 version 0.5.23.
+
+   See the [5]new features page for a more complete list of new features
+   found in EGCS 1.1 releases.
+
+   EGCS 1.1.1 is a minor update to fix several serious problems in EGCS
+   1.1:
+     * General improvements and fixes
+          + Avoid some stack overflows when compiling large functions.
+          + Avoid incorrect loop invariant code motions.
+          + Fix some core dumps on Linux kernel code.
+          + Bring back the imake -Di386 and friends fix from EGCS 1.0.2.
+          + Fix code generation problem in gcse.
+          + Various documentation related fixes.
+     * g++/libstdc++ improvements and fixes
+          + MT safe EH fix for setjmp/longjmp based exception handling.
+          + Fix a few bad interactions between optimization and exception
+            handling.
+          + Fixes for demangling of template names starting with "__".
+          + Fix a bug that would fail to run destructors in some cases
+            with -O2.
+          + Fix 'new' of classes with virtual bases.
+          + Fix crash building Qt on the Alpha.
+          + Fix failure compiling WIFEXITED macro on GNU/Linux.
+          + Fix some -frepo failures.
+     * g77 and libf2c improvements and fixes
+          + Various documentation fixes.
+          + Avoid compiler crash on RAND intrinsic.
+          + Fix minor bugs in makefiles exposed by BSD make programs.
+          + Define _XOPEN_SOURCE for libI77 build to avoid potential
+            problems on some 64-bit systems.
+          + Fix problem with implicit endfile on rewind.
+          + Fix spurious recursive I/O errors.
+     * platform specific improvements and fixes
+          + Match all versions of UnixWare7.
+          + Do not assume x86 SVR4 or UnixWare targets can handle stabs.
+          + Fix PPC/RS6000 LEGITIMIZE_ADDRESS macro and bug in conversion
+            from unsigned ints to double precision floats.
+          + Fix ARM ABI issue with NetBSD.
+          + Fix a few arm code generation bugs.
+          + Fixincludes will fix additional broken SCO OpenServer header
+            files.
+          + Fix a m68k backend bug which caused invalid offsets in reg+d
+            addresses.
+          + Fix problems with 64bit AIX 4.3 support.
+          + Fix handling of long longs for varargs/stdarg functions on
+            the ppc.
+          + Minor fixes to CPP predefines for Windows.
+          + Fix code generation problems with gpr<->fpr copies for 64bit
+            ppc.
+          + Fix a few coldfire code generation bugs.
+          + Fix some more header file problems on SunOS 4.x.
+          + Fix assert.h handling for RTEMS.
+          + Fix Windows handling of TREE_SYMBOL_REFERENCED.
+          + Fix x86 compiler abort in reg-stack pass.
+          + Fix cygwin/windows problem with section attributes.
+          + Fix Alpha code generation problem exposed by SMP Linux
+            kernels.
+          + Fix typo in m68k 32->64bit integer conversion.
+          + Make sure target libraries build with -fPIC for PPC & Alpha
+            targets.
+
+   EGCS 1.1.2 is a minor update to fix several serious problems in EGCS
+   1.1.1:
+     * General improvements and fixes
+          + Fix bug in loop optimizer which caused the SPARC (and
+            potentially other) ports to segfault.
+          + Fix infinite recursion in alias analysis and combiner code.
+          + Fix bug in regclass preferencing.
+          + Fix incorrect loop reversal which caused incorrect code to be
+            generated for several targets.
+          + Fix return value for builtin memcpy.
+          + Reduce compile time for certain loops which exposed quadratic
+            behavior in the loop optimizer.
+          + Fix bug which caused volatile memory to be written multiple
+            times when only one write was needed/desired.
+          + Fix compiler abort in caller-save.c
+          + Fix combiner bug which caused incorrect code generation for
+            certain division by constant operations.
+          + Fix incorrect code generation due to a bug in range check
+            optimizations.
+          + Fix incorrect code generation due to mis-handling of
+            clobbered values in CSE.
+          + Fix compiler abort/segfault due to incorrect register
+            splitting when unrolling loops.
+          + Fix code generation involving autoincremented addresses with
+            ternary operators.
+          + Work around bug in the scheduler which caused qt to be
+            mis-compiled on some platforms.
+          + Fix code generation problems with -fshort-enums.
+          + Tighten security for temporary files.
+          + Improve compile time for codes which make heavy use of
+            overloaded functions.
+          + Fix multiply defined constructor/destructor symbol problems.
+          + Avoid setting bogus RPATH environment variable during
+            bootstrap.
+          + Avoid GNU-make dependencies in the texinfo subdir.
+          + Install CPP wrapper script in $(prefix)/bin if --enable-cpp.
+            --enable-cpp=<dirname> can be used to specify an additional
+            install directory for the cpp wrapper script.
+          + Fix CSE bug which caused incorrect label-label refs to appear
+            on some platforms.
+          + Avoid linking in EH routines from libgcc if they are not
+            needed.
+          + Avoid obscure bug in aliasing code.
+          + Fix bug in weak symbol handling.
+     * Platform-specific improvements and fixes
+          + Fix detection of PPro/PII on Unixware 7.
+          + Fix compiler segfault when building spec99 and other programs
+            for SPARC targets.
+          + Fix code-generation bugs for integer and floating point
+            conditional move instructions on the PPro/PII.
+          + Use fixincludes to fix byteorder problems on i?86-*-sysv.
+          + Fix build failure for the arc port.
+          + Fix floating point format configuration for i?86-gnu port.
+          + Fix problems with hppa1.0-hp-hpux10.20 configuration when
+            threads are enabled.
+          + Fix coldfire code generation bugs.
+          + Fix "unrecognized insn" problems for Alpha and PPC ports.
+          + Fix h8/300 code generation problem with floating point values
+            in memory.
+          + Fix unrecognized insn problems for the m68k port.
+          + Fix namespace-pollution problem for the x86 port.
+          + Fix problems with old assembler on x86 NeXT systems.
+          + Fix PIC code-generation problems for the SPARC port.
+          + Fix minor bug with LONG_CALLS in PowerPC SVR4 support.
+          + Fix minor ISO namespace violation in Alpha varargs/stdarg
+            support.
+          + Fix incorrect "braf" instruction usage for the SH port.
+          + Fix minor bug in va-sh which prevented its use with -ansi.
+          + Fix problems recognizing and supporting FreeBSD.
+          + Handle OpenBSD systems correctly.
+          + Minor fixincludes fix for Digital UNIX 4.0B.
+          + Fix problems with ctors/dtors in SCO shared libraries.
+          + Abort instead of generating incorrect code for PPro/PII
+            floating point conditional moves.
+          + Avoid multiply defined symbols on Linux/GNU systems using
+            libc-5.4.xx.
+          + Fix abort in alpha compiler.
+     * Fortran-specific fixes
+          + Fix the IDate intrinsic (VXT) (in libg2c) so the returned
+            year is in the documented, non-Y2K-compliant range of 0-99,
+            instead of being returned as 100 in the year 2000.
+          + Fix the `Date_and_Time' intrinsic (in libg2c) to return the
+            milliseconds value properly in Values(8).
+          + Fix the `LStat' intrinsic (in libg2c) to return device-ID
+            information properly in SArray(7).
+
+   Each release includes installation instructions in both HTML and
+   plaintext forms (see the INSTALL directory in the toplevel directory
+   of the distribution). However, we also keep the most up to date
+   [6]installation instructions and [7]build/test status on our web page.
+   We will update those pages as new information becomes available.
+
+   The EGCS project would like to thank the numerous people that have
+   contributed new features, test results, bugfixes, etc. This [8]amazing
+   group of volunteers is what makes EGCS successful.
+
+   And finally, we can't in good conscience fail to mention some
+   [9]caveats to using EGCS 1.1.
+
+   Download EGCS from egcs.cygnus.com (USA California).
+
+   The EGCS 1.1 release is also available on many mirror sites.
+   [10]Goto mirror list to find a closer site.
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [11]gnu@gnu.org. There
+   are also [12]other ways to contact the FSF.
+
+   These pages are maintained by [13]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [14]GCC manuals. If that fails, the
+    [15]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [16]gcc@gnu.org or
+    [17]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [18]Valid XHTML 1.0 
+
+References
+
+   1. http://gcc.gnu.org/egcs-1.1/egcs-1.1-test.html
+   2. http://gcc.gnu.org/news/gcse.html
+   3. http://gcc.gnu.org/news/alias.html
+   4. http://gcc.gnu.org/egcs-1.1/c++features.html
+   5. http://gcc.gnu.org/egcs-1.1/features.html
+   6. http://gcc.gnu.org/install/
+   7. http://gcc.gnu.org/egcs-1.1/buildstat.html
+   8. http://gcc.gnu.org/onlinedocs/gcc/Contributors.html
+   9. http://gcc.gnu.org/egcs-1.1/caveats.html
+  10. http://gcc.gnu.org/mirrors.html
+  11. mailto:gnu@gnu.org
+  12. http://www.gnu.org/home.html#ContactInfo
+  13. http://gcc.gnu.org/about.html
+  14. http://gcc.gnu.org/onlinedocs/
+  15. mailto:gcc-help@gcc.gnu.org
+  16. mailto:gcc@gnu.org
+  17. mailto:gcc@gcc.gnu.org
+  18. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/egcs-1.1/features.html
+
+                           EGCS 1.1 new features
+
+     * Integrated GNU Fortran (g77) compiler and runtime library with
+       improvements, based on [1]g77 version 0.5.23.
+     * Vast improvements in the C++ compiler; so many they have [2]page
+       of their own!
+     * Compiler implements [3]global common subexpression elimination and
+       global copy/constant propagation.
+     * More major improvements in the [4]alias analysis code.
+     * More major improvements in the exception handling code to improve
+       performance, lower static overhead and provide the infrastructure
+       for future improvements.
+     * The infamous /tmp symlink race security problems have been fixed.
+     * The regmove optimization pass has been nearly completely rewritten
+       to improve performance of generated code.
+     * The compiler now recomputes register usage information before
+       local register allocation. By providing more accurate information
+       to the priority based allocator, we get better register
+       allocation.
+     * The register reloading phase of the compiler optimizes spill code
+       much better than in previous releases.
+     * Some bad interactions between the register allocator and
+       instruction scheduler have been fixed, resulting in much better
+       code for certain programs. Additionally, we have tuned the
+       scheduler in various ways to improve performance of generated code
+       for some architectures.
+     * The compiler's branch shortening algorithms have been
+       significantly improved to work better on targets which align jump
+       targets.
+     * The compiler now supports -Os to prefer optimizing for code space
+       over optimizing for code speed.
+     * The compiler will now totally eliminate library calls which
+       compute constant values. This primarily helps targets with no
+       integer div/mul support and targets without floating point
+       support.
+     * The compiler now supports an extensive "--help" option.
+     * cpplib has been greatly improved and may be suitable for limited
+       use.
+     * Memory footprint for the compiler has been significantly reduced
+       for some pathological cases.
+     * The time to build EGCS has been improved for certain targets
+       (particularly the alpha and mips platforms).
+     * Many infrastructure improvements throughout the compiler, plus the
+       usual mountain of bugfixes and minor improvements.
+     * Target dependent improvements:
+          + SPARC port now includes V8 plus and V9 support as well as
+            performance tuning for Ultra class machines. The SPARC port
+            now uses the Haifa scheduler.
+          + 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.
+          + RS6000/PowerPC: support for the Power64 architecture and AIX
+            4.3. The RS6000/PowerPC port now uses the Haifa scheduler.
+          + x86: Alignment of static store data and jump targets is per
+            Intel recommendations now. Various improvements throughout
+            the x86 port to improve performance on Pentium processors
+            (including improved epilogue sequences for Pentium chips and
+            backend improvements which should help register allocation on
+            all x86 variants. Conditional move support has been fixed and
+            enabled for PPro processors. The x86 port also better
+            supports 64bit operations now. Unixware 7, a System V Release
+            5 target, is now supported and SCO OpenServer targets can
+            support GAS.
+          + MIPS has improved multiply/multiply-add support and now
+            includes mips16 ISA support.
+          + M68k has many micro-optimizations and Coldfire fixes.
+     * Core compiler is based on the GCC development tree from June 9,
+       1998, so we have all of the [5]features found in GCC 2.8.
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [6]gnu@gnu.org. There
+   are also [7]other ways to contact the FSF.
+
+   These pages are maintained by [8]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [9]GCC manuals. If that fails, the
+    [10]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [11]gcc@gnu.org or
+    [12]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [13]Valid XHTML 1.0 
+
+References
+
+   1. http://gcc.gnu.org/onlinedocs/g77/News.html
+   2. http://gcc.gnu.org/egcs-1.1/c++features.html
+   3. http://gcc.gnu.org/news/gcse.html
+   4. http://gcc.gnu.org/news/alias.html
+   5. http://gcc.gnu.org/egcs-1.0/features-2.8.html
+   6. mailto:gnu@gnu.org
+   7. http://www.gnu.org/home.html#ContactInfo
+   8. http://gcc.gnu.org/about.html
+   9. http://gcc.gnu.org/onlinedocs/
+  10. mailto:gcc-help@gcc.gnu.org
+  11. mailto:gcc@gnu.org
+  12. mailto:gcc@gcc.gnu.org
+  13. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/egcs-1.1/caveats.html
+
+                              EGCS 1.1 Caveats
+
+     * EGCS has an integrated libstdc++, but does not have an integrated
+       libg++. Furthermore old libg++ releases will not work with EGCS;
+       HJ Lu has made a libg++-2.8.1.2 snapshot available which may work
+       with EGCS.
+       Note most C++ programs only need libstdc++.
+     * Exception handling may not work with shared libraries,
+       particularly on alphas, hppas, rs6000/powerpc and mips based
+       platforms. Exception handling is known to work on x86-linux
+       platforms with shared libraries.
+     * Some versions of the Linux kernel have bugs which prevent them
+       from being compiled or from running when compiled by EGCS. See the
+       FAQ (as shipped with EGCS 1.1) for additional information.
+     * In general, EGCS is more rigorous about rejecting invalid C++ code
+       or deprecated C++ constructs than g++-2.7, g++-2.8 or EGCS 1.0. As
+       a result it may be necessary to fix C++ code before it will
+       compile with EGCS.
+     * G++ is also converting toward the ISO C++ standard; as a result
+       code which was previously valid (and thus accepted by other
+       compilers and older versions of g++) may no longer be accepted.
+     * EGCS 1.1 compiled C++ code is not binary compatible with EGCS
+       1.0.x or GCC 2.8.x due to changes necessary to support thread safe
+       exception handling.
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [1]gnu@gnu.org. There
+   are also [2]other ways to contact the FSF.
+
+   These pages are maintained by [3]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [4]GCC manuals. If that fails, the
+    [5]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [6]gcc@gnu.org or
+    [7]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [8]Valid XHTML 1.0 
+
+References
+
+   1. mailto:gnu@gnu.org
+   2. http://www.gnu.org/home.html#ContactInfo
+   3. http://gcc.gnu.org/about.html
+   4. http://gcc.gnu.org/onlinedocs/
+   5. mailto:gcc-help@gcc.gnu.org
+   6. mailto:gcc@gnu.org
+   7. mailto:gcc@gcc.gnu.org
+   8. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/egcs-1.0/egcs-1.0.3.html
+
+                                 EGCS 1.0.3
+
+   May 15, 1998
+
+   We are pleased to announce the release of EGCS 1.0.3.
+
+   EGCS is a collaborative effort involving several groups of hackers
+   using an open development model to accelerate development and testing
+   of GNU compilers and runtime libraries.
+
+   EGCS 1.0.3 is a minor update to the EGCS 1.0.2 compiler to fix a few
+   problems reported by Red Hat for builds of Red Hat 5.1.
+     * Generic bugfixes:
+          + Fix a typo in the libio library which resulted in incorrect
+            behavior of istream::get.
+          + Fix the Fortran negative array index problem.
+          + Fix a major problem with the ObjC runtime thread support
+            exposed by glibc2.
+          + Reduce memory consumption of the Haifa scheduler.
+     * Target specific bugfixes:
+          + Fix one x86 floating point code generation bug exposed by
+            glibc2 builds.
+          + Fix one x86 internal compiler error exposed by glibc2 builds.
+          + Fix profiling bugs on the Alpha.
+          + Fix ImageMagick & emacs 20.2 build problems on the Alpha.
+          + Fix rs6000/ppc bug when converting values from integer types
+            to floating point types.
+
+   An important goal of EGCS is to allow wide scale testing of new
+   features and optimizations which are still under development. However,
+   EGCS has been carefully tested and should be comparable in quality to
+   most GCC releases.
+
+   EGCS 1.0.3 is based on an August 2, 1997 snapshot of the GCC 2.8
+   development sources; it contains nearly all of the new features found
+   in GCC 2.8.
+
+   EGCS also contains many improvements and features not found in GCC 2.7
+   or GCC 2.8.
+     * Integrated C++ runtime libraries, including support for most major
+       GNU/Linux systems!
+     * The integrated libstdc++ library includes a verbatim copy of SGI's
+       STL release instead of a modified copy.
+     * Integrated GNU Fortran compiler.
+     * New instruction scheduler.
+     * New alias analysis code.
+
+   See the [1]new features page for a more complete list of new features
+   found in EGCS 1.0.x releases.
+
+   The EGCS 1.0.3 release includes installation instructions in both HTML
+   and plaintext forms (see the INSTALL directory in the toplevel
+   directory of the EGCS 1.0.3 distribution). However, we also keep the
+   most up to date [2]installation instructions and [3]build/test status
+   on our web page. We will update those pages as new information becomes
+   available.
+
+   And, we can't in good conscience fail to mention some [4]caveats to
+   using EGCS.
+
+   Update: Big thanks to Stanford for providing a high speed link for
+   downloading EGCS (go.cygnus.com)!
+
+   Download EGCS from ftp.cygnus.com (USA California) or go.cygnus.com
+   (USA California -- High speed link provided by Stanford).
+
+   The EGCS 1.0.3 release is also available on many mirror sites.
+   [5]Goto mirror list to find a closer site
+
+   We'd like to thank the numerous people that have contributed new
+   features, test results, bugfixes, etc. Unfortunately, they're far too
+   numerous to mention by name.
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [6]gnu@gnu.org. There
+   are also [7]other ways to contact the FSF.
+
+   These pages are maintained by [8]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [9]GCC manuals. If that fails, the
+    [10]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [11]gcc@gnu.org or
+    [12]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [13]Valid XHTML 1.0 
+
+References
+
+   1. http://gcc.gnu.org/egcs-1.0/features.html
+   2. http://gcc.gnu.org/install/
+   3. http://gcc.gnu.org/egcs-1.0/buildstat.html
+   4. http://gcc.gnu.org/egcs-1.0/caveats.html
+   5. http://gcc.gnu.org/mirrors.html
+   6. mailto:gnu@gnu.org
+   7. http://www.gnu.org/home.html#ContactInfo
+   8. http://gcc.gnu.org/about.html
+   9. http://gcc.gnu.org/onlinedocs/
+  10. mailto:gcc-help@gcc.gnu.org
+  11. mailto:gcc@gnu.org
+  12. mailto:gcc@gcc.gnu.org
+  13. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/egcs-1.0/egcs-1.0.2.html
+
+                                 EGCS 1.0.2
+
+   March 16, 1998
+
+   We are pleased to announce the release of EGCS 1.0.2.
+
+   EGCS is a collaborative effort involving several groups of hackers
+   using an open development model to accelerate development and testing
+   of GNU compilers and runtime libraries.
+
+   EGCS 1.0.2 is a minor update to the EGCS 1.0.1 compiler to fix several
+   serious problems in EGCS 1.0.1.
+     * General improvements and fixes
+          + Memory consumption significantly reduced, especially for
+            templates and inline functions.
+          + Fix various problems with glibc2.1.
+          + Fix loop optimization bug exposed by rs6000/ppc port.
+          + Fix to avoid potential code generation problems in jump.c.
+          + Fix some undefined symbol problems in dwarf1 debug support.
+     * g++/libstdc++ improvements and fixes
+          + libstdc++ in the EGCS release has been updated and should be
+            link compatible with libstdc++-2.8.
+          + Various fixes in libio/libstdc++ to work better on Linux
+            systems.
+          + Fix problems with duplicate symbols on systems that do not
+            support weak symbols.
+          + Memory corruption bug and undefined symbols in bastring have
+            been fixed.
+          + Various exception handling fixes.
+          + Fix compiler abort for very long thunk names.
+     * g77 improvements and fixes
+          + Fix compiler crash for omitted bound in Fortran CASE
+            statement.
+          + Add missing entries to g77 lang-options.
+          + Fix problem with -fpedantic in the g77 compiler.
+          + Fix "backspace" problem with g77 on alphas.
+          + Fix x86 backend problem with Fortran literals and -fpic.
+          + Fix some of the problems with negative subscripts for g77 on
+            alphas.
+          + Fixes for Fortran builds on cygwin32/mingw32.
+     * platform specific improvements and fixes
+          + Fix long double problems on x86 (exposed by glibc).
+          + x86 ports define i386 again to keep imake happy.
+          + Fix exception handling support on NetBSD ports.
+          + Several changes to collect2 to fix many problems with AIX.
+          + Define __ELF__ for rs6000/linux.
+          + Fix -mcall-linux problem on rs6000/linux.
+          + Fix stdarg/vararg problem for rs6000/linux.
+          + Allow autoconf to select a proper install problem on AIX 3.1.
+          + m68k port support includes -mcpu32 option as well as cpu32
+            multilibs.
+          + Fix stdarg bug for irix6.
+          + Allow EGCS to build on irix5 without the gnu assembler.
+          + Fix problem with static linking on sco5.
+          + Fix bootstrap on sco5 with native compiler.
+          + Fix for abort building newlib on H8 target.
+          + Fix fixincludes handling of math.h on SunOS.
+          + Minor fix for Motorola 3300 m68k systems.
+
+   An important goal of EGCS is to allow wide scale testing of new
+   features and optimizations which are still under development. However,
+   EGCS has been carefully tested and should be comparable in quality to
+   most GCC releases.
+
+   EGCS 1.0.2 is based on an August 2, 1997 snapshot of the GCC 2.8
+   development sources; it contains nearly all of the new features found
+   in GCC 2.8.
+
+   EGCS also contains many improvements and features not found in GCC 2.7
+   or GCC 2.8.
+     * Integrated C++ runtime libraries, including support for most major
+       linux systems!
+     * The integrated libstdc++ library includes a verbatim copy of SGI's
+       STL release.
+     * Integrated GNU Fortran compiler.
+     * New instruction scheduler.
+     * New alias analysis code.
+
+   See the [1]new features page for a more complete list of new features
+   found in EGCS 1.0.x releases.
+
+   The EGCS 1.0.2 release includes installation instructions in both HTML
+   and plaintext forms (see the INSTALL directory in the toplevel
+   directory of the EGCS 1.0.2 distribution). However, we also keep the
+   most up to date [2]installation instructions and [3]build/test status
+   on our web page. We will update those pages as new information becomes
+   available.
+
+   And, we can't in good conscience fail to mention some [4]caveats to
+   using EGCS.
+
+   Update: Big thanks to Stanford for providing a high speed link for
+   downloading EGCS (go.cygnus.com)!
+
+   Download EGCS from ftp.cygnus.com (USA California) or go.cygnus.com
+   (USA California -- High speed link provided by Stanford).
+
+   The EGCS 1.0.2 release is also available on many mirror sites.
+   [5]Goto mirror list to find a closer site
+
+   We'd like to thank the numerous people that have contributed new
+   features, test results, bugfixes, etc. Unfortunately, they're far too
+   numerous to mention by name.
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [6]gnu@gnu.org. There
+   are also [7]other ways to contact the FSF.
+
+   These pages are maintained by [8]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [9]GCC manuals. If that fails, the
+    [10]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [11]gcc@gnu.org or
+    [12]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [13]Valid XHTML 1.0 
+
+References
+
+   1. http://gcc.gnu.org/egcs-1.0/features.html
+   2. http://gcc.gnu.org/install/index.html
+   3. http://gcc.gnu.org/egcs-1.0/buildstat.html
+   4. http://gcc.gnu.org/egcs-1.0/caveats.html
+   5. http://gcc.gnu.org/mirrors.html
+   6. mailto:gnu@gnu.org
+   7. http://www.gnu.org/home.html#ContactInfo
+   8. http://gcc.gnu.org/about.html
+   9. http://gcc.gnu.org/onlinedocs/
+  10. mailto:gcc-help@gcc.gnu.org
+  11. mailto:gcc@gnu.org
+  12. mailto:gcc@gcc.gnu.org
+  13. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/egcs-1.0/egcs-1.0.1.html
+
+                                 EGCS 1.0.1
+
+   January 6, 1998
+
+   We are pleased to announce the release of EGCS 1.0.1.
+
+   EGCS is a collaborative effort involving several groups of hackers
+   using an open development model to accelerate development and testing
+   of GNU compilers and runtime libraries.
+
+   EGCS 1.0.1 is a minor update to the EGCS 1.0 compiler to fix a few
+   critical bugs and add support for Red Hat 5.0 Linux. Changes since the
+   EGCS 1.0 release:
+     * Add support for Red Hat 5.0 Linux and better support for Linux
+       systems using glibc2.
+       Many programs failed to link when compiled with EGCS 1.0 on Red
+       Hat 5.0 or on systems with newer versions of glibc2. EGCS 1.0.1
+       should fix these problems.
+     * Compatibility with both EGCS 1.0 and GCC 2.8 libgcc exception
+       handling interfaces.
+       To avoid future compatibility problems, we strongly urge anyone
+       who is planning on distributing shared libraries that contain C++
+       code to upgrade to EGCS 1.0.1 first.
+       Soon after EGCS 1.0 was released, the GCC developers made some
+       incompatible changes in libgcc's exception handling interfaces.
+       These changes were needed to solve problems on some platforms.
+       This means that GCC 2.8.0, when released, will not be seamlessly
+       compatible with shared libraries built by EGCS 1.0. The reason is
+       that the libgcc.a in GCC 2.8.0 will not contain a function needed
+       by the old interface.
+       The result of this is that there may be compatibility problems
+       with shared libraries built by EGCS 1.0 when used with GCC 2.8.0.
+       With EGCS 1.0.1, generated code uses the new (GCC 2.8.0)
+       interface, and libgcc.a has the support routines for both the old
+       and the new interfaces (so EGCS 1.0.1 and EGCS 1.0 code can be
+       freely mixed, and EGCS 1.0.1 and GCC 2.8.0 code can be freely
+       mixed).
+       The maintainers of GCC 2.x have decided against including seamless
+       support for the old interface in 2.8.0, since it was never
+       "official", so to avoid future compatibility problems we recommend
+       against distributing any shared libraries built by EGCS 1.0 that
+       contain C++ code (upgrade to 1.0.1 and use that).
+     * Various bugfixes in the x86, hppa, mips, and rs6000/ppc backends.
+       The x86 changes fix code generation errors exposed when building
+       glibc2 and the Linux dynamic linker (ld.so).
+       The hppa change fixes a compiler abort when configured for use
+       with RTEMS.
+       The MIPS changes fix problems with the definition of LONG_MAX on
+       newer systems, allow for command line selection of the target ABI,
+       and fix one code generation problem.
+       The rs6000/ppc change fixes some problems with passing structures
+       to varargs/stdarg functions.
+     * A few machine independent bugfixes, mostly to fix code generation
+       errors when building Linux kernels or glibc.
+     * Fix a few critical exception handling and template bugs in the C++
+       compiler.
+     * Fix Fortran namelist bug on alphas.
+     * Fix build problems on x86-solaris systems.
+
+   An important goal of EGCS is to allow wide scale testing of new
+   features and optimizations which are still under development. However,
+   EGCS has been carefully tested and should be comparable in quality to
+   most GCC releases.
+
+   EGCS 1.0.1 is based on an August 2, 1997 snapshot of the GCC 2.8
+   development sources; it contains nearly all of the new features found
+   in GCC 2.8.
+
+   EGCS also contains many improvements and features not found in GCC 2.7
+   and even the soon to be released GCC 2.8 compilers.
+     * Integrated C++ runtime libraries, including support for most major
+       linux systems!
+     * The integrated libstdc++ library includes a verbatim copy of SGI's
+       STL release.
+     * Integrated GNU Fortran compiler
+     * New instruction scheduler
+     * New alias analysis code
+
+   See the [1]new features page for a more complete list of new features
+   found in EGCS 1.0.x releases.
+
+   The EGCS 1.0.1 release includes installation instructions in both HTML
+   and plaintext forms (see the INSTALL directory in the toplevel
+   directory of the EGCS 1.0.1 distribution). However, we also keep the
+   most up to date [2]installation instructions and [3]build/test status
+   on our web page. We will update those pages as new information becomes
+   available.
+
+   And, we can't in good conscience fail to mention some [4]caveats to
+   using EGCS.
+
+   Update: Big thanks to Stanford for providing a high speed link for
+   downloading EGCS (go.cygnus.com)!
+
+   Download EGCS from ftp.cygnus.com (USA California) or go.cygnus.com
+   (USA California -- High speed link provided by Stanford).
+
+   The EGCS 1.0.1 release is also available on many mirror sites.
+   [5]Goto mirror list to find a closer site
+
+   We'd like to thank the numerous people that have contributed new
+   features, test results, bugfixes, etc. Unfortunately, they're far too
+   numerous to mention by name.
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [6]gnu@gnu.org. There
+   are also [7]other ways to contact the FSF.
+
+   These pages are maintained by [8]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [9]GCC manuals. If that fails, the
+    [10]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [11]gcc@gnu.org or
+    [12]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [13]Valid XHTML 1.0 
+
+References
+
+   1. http://gcc.gnu.org/egcs-1.0/features.html
+   2. http://gcc.gnu.org/install/index.html
+   3. http://gcc.gnu.org/egcs-1.0/buildstat.html
+   4. http://gcc.gnu.org/egcs-1.0/caveats.html
+   5. http://gcc.gnu.org/mirrors.html
+   6. mailto:gnu@gnu.org
+   7. http://www.gnu.org/home.html#ContactInfo
+   8. http://gcc.gnu.org/about.html
+   9. http://gcc.gnu.org/onlinedocs/
+  10. mailto:gcc-help@gcc.gnu.org
+  11. mailto:gcc@gnu.org
+  12. mailto:gcc@gcc.gnu.org
+  13. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/egcs-1.0/egcs-1.0.html
+
+                                  EGCS 1.0
+
+   December 3, 1997
+
+   We are pleased to announce the release of EGCS 1.0.
+
+   EGCS is a collaborative effort involving several groups of hackers
+   using an open development model to accelerate development and testing
+   of GNU compilers and runtime libraries.
+
+   An important goal of EGCS is to allow wide scale testing of
+   experimental features and optimizations; therefore, EGCS contains some
+   features and optimizations which are still under development. However,
+   EGCS has been carefully tested and should be comparable in quality to
+   most GCC releases.
+
+   EGCS 1.0 is based on an August 2, 1997 snapshot of the GCC 2.8
+   development sources; it contains nearly all of the new features found
+   in GCC 2.8.
+
+   EGCS 1.0 also contains many improvements and features not found in GCC
+   2.7 and even the soon to be released GCC 2.8 compilers.
+     * Integrated C++ runtime libraries, including support for most major
+       linux systems!
+     * The integrated libstdc++ library includes a verbatim copy of SGI's
+       STL release.
+     * Integrated GNU Fortran compiler.
+     * New instruction scheduler.
+     * New alias analysis code.
+
+   See the [1]new features page for a more complete list of new features.
+
+   The EGCS 1.0 release includes installation instructions in both HTML
+   and plaintext forms (see the INSTALL directory in the toplevel
+   directory of the EGCS 1.0 distribution). However, we also keep the
+   most up to date [2]installation instructions and [3]build/test status
+   on our web page. We will update those pages as new information becomes
+   available.
+
+   And, we can't in good conscience fail to mention some [4]caveats to
+   using EGCS.
+
+   Update: The T1 into our main California offices has been 100%
+   saturated since shortly after the release. We've added an EGCS 1.0
+   mirror at our Massachusetts office to help share the load. We also
+   encourage folks to use the many mirrors available throughout the
+   world.
+
+   Update: Big thanks to Stanford for providing a high speed link for
+   downloading EGCS (go.cygnus.com)!
+
+   Download EGCS from ftp.cygnus.com (USA California) or go.cygnus.com
+   (USA California -- High speed link provided by Stanford).
+
+   The EGCS 1.0 release should be available on most mirror sites by now.
+   [5]Goto mirror list to find a closer site
+
+   We'd like to thank the numerous people that have contributed new
+   features, test results, bugfixes, etc. Unfortunately, they're far too
+   numerous to mention by name.
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [6]gnu@gnu.org. There
+   are also [7]other ways to contact the FSF.
+
+   These pages are maintained by [8]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [9]GCC manuals. If that fails, the
+    [10]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [11]gcc@gnu.org or
+    [12]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [13]Valid XHTML 1.0 
+
+References
+
+   1. http://gcc.gnu.org/egcs-1.0/features.html
+   2. http://gcc.gnu.org/install/index.html
+   3. http://gcc.gnu.org/egcs-1.0/buildstat.html
+   4. http://gcc.gnu.org/egcs-1.0/caveats.html
+   5. http://gcc.gnu.org/mirrors.html
+   6. mailto:gnu@gnu.org
+   7. http://www.gnu.org/home.html#ContactInfo
+   8. http://gcc.gnu.org/about.html
+   9. http://gcc.gnu.org/onlinedocs/
+  10. mailto:gcc-help@gcc.gnu.org
+  11. mailto:gcc@gnu.org
+  12. mailto:gcc@gcc.gnu.org
+  13. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/egcs-1.0/features.html
+
+                             EGCS 1.0 features
+
+     * Core compiler is based on the gcc2 development tree from Aug 2,
+       1997, so we have most of the [1]features found in GCC 2.8.
+     * Integrated GNU Fortran compiler based on g77-0.5.22-19970929.
+     * Vast improvements in the C++ compiler; so many they have [2]page
+       of their own!
+     * Integrated C++ runtime libraries, including support for most major
+       linux systems!
+     * New instruction scheduler from IBM Haifa which includes support
+       for function wide instruction scheduling as well as superscalar
+       scheduling.
+     * Significantly improved alias analysis code.
+     * Improved register allocation for two address machines.
+     * Significant code generation improvements for Fortran code on
+       Alphas.
+     * Various optimizations from the g77 project as well as improved
+       loop optimizations.
+     * Dwarf2 debug format support for some targets.
+     * egcs libstdc++ includes the SGI STL implementation without
+       changes.
+     * As a result of these and other changes, egcs libstc++ is not
+       binary compatible with previous releases of libstdc++.
+     * Various new ports -- UltraSPARC, Irix6.2 & Irix6.3 support, The
+       SCO Openserver 5 family (5.0.{0,2,4} and Internet FastStart 1.0
+       and 1.1), Support for RTEMS on several embedded targets, Support
+       for arm-linux, Mitsubishi M32R, Hitachi H8/S, Matsushita MN102 and
+       MN103, NEC V850, Sparclet, Solaris & Linux on PowerPCs, etc.
+     * Integrated testsuites for gcc, g++, g77, libstdc++ and libio.
+     * RS6000/PowerPC ports generate code which can run on all
+       RS6000/PowerPC variants by default.
+     * -mcpu= and -march= switches for the x86 port to allow better
+       control over how the x86 port generates code.
+     * Includes the template repository patch (aka repo patch); note the
+       new template code makes repo obsolete for ELF systems using gnu-ld
+       such as Linux.
+     * Plus the usual assortment of bugfixes and improvements.
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [3]gnu@gnu.org. There
+   are also [4]other ways to contact the FSF.
+
+   These pages are maintained by [5]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [6]GCC manuals. If that fails, the
+    [7]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [8]gcc@gnu.org or
+    [9]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [10]Valid XHTML 1.0 
+
+References
+
+   1. http://gcc.gnu.org/egcs-1.0/features-2.8.html
+   2. http://gcc.gnu.org/egcs-1.0/c++features.html
+   3. mailto:gnu@gnu.org
+   4. http://www.gnu.org/home.html#ContactInfo
+   5. http://gcc.gnu.org/about.html
+   6. http://gcc.gnu.org/onlinedocs/
+   7. mailto:gcc-help@gcc.gnu.org
+   8. mailto:gcc@gnu.org
+   9. mailto:gcc@gcc.gnu.org
+  10. http://validator.w3.org/check/referer
+======================================================================
+http://gcc.gnu.org/egcs-1.0/caveats.html
+
+                              EGCS 1.0 Caveats
+
+     * EGCS has an integrated libstdc++, but does not have an integrated
+       libg++. Furthermore old libg++ releases will not work with egc; HJ
+       Lu has made a libg++-2.8.1.2 available which may work with EGCS.
+       Note most C++ programs only need libstdc++.
+     * Note that using -pedantic or -Wreturn-type can cause an explosion
+       in the amount of memory needed for template-heavy C++ code, such
+       as code that uses STL. Also note that -Wall includes
+       -Wreturn-type, so if you use -Wall you will need to specify
+       -Wno-return-type to turn it off.
+     * Exception handling may not work with shared libraries,
+       particularly on alphas, hppas, and mips based platforms. Exception
+       handling is known to work on x86-linux platforms with shared
+       libraries.
+     * Some versions of the Linux kernel have bugs which prevent them
+       from being compiled or from running when compiled by EGCS. See the
+       FAQ (as shipped with EGCS 1.0) for additional information.
+     * In general, EGCS is more rigorous about rejecting invalid C++ code
+       or deprecated C++ constructs than G++ 2.7. As a result it may be
+       necessary to fix C++ code before it will compile with EGCS.
+     * G++ is also aggressively tracking the C++ standard; as a result
+       code which was previously valid (and thus accepted by other
+       compilers and older versions of G++) may no longer be accepted.
+     * EGCS 1.0 may not work with Red Hat Linux 5.0 on all targets. EGCS
+       1.0.x and later releases should work with Red Hat Linux 5.0.
+     _________________________________________________________________
+
+   Please send FSF & GNU inquiries & questions to [1]gnu@gnu.org. There
+   are also [2]other ways to contact the FSF.
+
+   These pages are maintained by [3]the GCC team.
+
+
+    For questions related to the use of GCC, please consult these web
+    pages and the [4]GCC manuals. If that fails, the
+    [5]gcc-help@gcc.gnu.org mailing list might help.
+    Please send comments on these web pages and the development of GCC
+    to our public developer mailing list at [6]gcc@gnu.org or
+    [7]gcc@gcc.gnu.org.
+
+   Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite
+   330, Boston, MA 02111, USA.
+
+   Verbatim copying and distribution of this entire article is permitted
+   in any medium, provided this notice is preserved.
+
+   Last modified 2003-08-28 [8]Valid XHTML 1.0 
+
+References
+
+   1. mailto:gnu@gnu.org
+   2. http://www.gnu.org/home.html#ContactInfo
+   3. http://gcc.gnu.org/about.html
+   4. http://gcc.gnu.org/onlinedocs/
+   5. mailto:gcc-help@gcc.gnu.org
+   6. mailto:gcc@gnu.org
+   7. mailto:gcc@gcc.gnu.org
+   8. http://validator.w3.org/check/referer
+======================================================================
