changeset 65:65488c3d617d

remove unnecessary filese
author ryoma <e075725@ie.u-ryukyu.ac.jp>
date Tue, 25 May 2010 18:58:51 +0900
parents d9bee9007a48
children f6334be47118
files INSTALL/binaries.html INSTALL/build.html INSTALL/configure.html INSTALL/download.html INSTALL/finalinstall.html INSTALL/gfdl.html INSTALL/index.html INSTALL/old.html INSTALL/prerequisites.html INSTALL/specific.html INSTALL/test.html NEWS fixincludes/tests/base/sys/limits.h fixincludes/tests/base/wchar.h gcc/config/alpha/osf.h gcc/config/alpha/t-osf4 gcc/config/alpha/t-vms64 gcc/config/alpha/vms-cc.c gcc/config/alpha/vms-crt0-64.c gcc/config/alpha/vms-crt0.c gcc/config/alpha/vms-ld.c gcc/config/alpha/vms-psxcrt0-64.c gcc/config/alpha/vms-psxcrt0.c gcc/config/alpha/vms_tramp.asm gcc/config/alpha/x-vms gcc/config/alpha/xm-vms.h gcc/config/arm/t-arm-coff gcc/config/h8300/coff.h gcc/config/i386/i386-aout.h gcc/config/i386/i386-coff.h gcc/config/i386/mmintrin-common.h gcc/config/ia64/itanium1.md gcc/config/libgloss.h gcc/config/m68k/coff.h gcc/config/m68k/m68k-aout.h gcc/config/mips/dbxmdebug.h gcc/config/mips/iris.h gcc/config/mips/iris5.h gcc/config/mips/sdemtk.opt gcc/config/pdp11/2bsd.h gcc/config/rs6000/aix41.h gcc/config/rs6000/aix41.opt gcc/config/rs6000/t-newas gcc/config/s390/fixdfdi.h gcc/config/s390/libgcc-glibc.ver gcc/config/s390/t-crtstuff gcc/config/s390/t-linux gcc/config/s390/t-tpf gcc/config/sh/coff.h gcc/config/sh/symbian.c gcc/config/sh/t-1e gcc/config/sh/t-mlib-sh1 gcc/config/sh/t-mlib-sh2 gcc/config/sh/t-mlib-sh2a gcc/config/sh/t-mlib-sh2a-nofpu gcc/config/sh/t-mlib-sh2a-single gcc/config/sh/t-mlib-sh2a-single-only gcc/config/sh/t-mlib-sh2e gcc/config/sh/t-mlib-sh3 gcc/config/sh/t-mlib-sh3e gcc/config/sh/t-mlib-sh4 gcc/config/sh/t-mlib-sh4-nofpu gcc/config/sh/t-mlib-sh4-single gcc/config/sh/t-mlib-sh4-single-only gcc/config/sh/t-mlib-sh4a gcc/config/sh/t-mlib-sh4a-nofpu gcc/config/sh/t-mlib-sh4a-single gcc/config/sh/t-mlib-sh4a-single-only gcc/config/sh/t-mlib-sh4al gcc/config/sh/t-mlib-sh5-32media gcc/config/sh/t-mlib-sh5-32media-nofpu gcc/config/sh/t-mlib-sh5-64media gcc/config/sh/t-mlib-sh5-64media-nofpu gcc/config/sh/t-mlib-sh5-compact gcc/config/sh/t-mlib-sh5-compact-nofpu gcc/config/sparc/sol2-gld.h gcc/doc/aot-compile.1 gcc/doc/c-tree.texi gcc/doc/cpp.1 gcc/doc/cpp.info gcc/doc/cppinternals.info gcc/doc/fsf-funding.7 gcc/doc/g++.1 gcc/doc/gc-analyze.1 gcc/doc/gcc.1 gcc/doc/gcc.info gcc/doc/gccinstall.info gcc/doc/gccint.info gcc/doc/gcj-dbtool.1 gcc/doc/gcj.1 gcc/doc/gcj.info gcc/doc/gcov.1 gcc/doc/gfdl.7 gcc/doc/gfortran.1 gcc/doc/gij.1 gcc/doc/gpl.7 gcc/doc/grmic.1 gcc/doc/jcf-dump.1 gcc/doc/jv-convert.1 gcc/doc/rebuild-gcj-db.1 gcc/dwarf.h gcc/dwarf2.h gcc/fix-header.c gcc/fixproto gcc/gen-protos.c gcc/gengtype-lex.c gcc/lto-wpa-fixup.c gcc/po/be.gmo gcc/po/da.gmo gcc/po/de.gmo gcc/po/el.gmo gcc/po/es.gmo gcc/po/fi.gmo gcc/po/fr.gmo gcc/po/id.gmo gcc/po/ja.gmo gcc/po/nl.gmo gcc/po/ru.gmo gcc/po/sr.gmo gcc/po/sv.gmo gcc/po/tr.gmo gcc/po/zh_CN.gmo gcc/po/zh_TW.gmo gcc/protoize.c gcc/rtl-factoring.c gcc/scan-decls.c gcc/scan-types.sh gcc/scan.c gcc/scan.h gcc/see.c gcc/sort-protos gcc/sys-protos.h gcc/sys-types.h gcc/tree-ssa-structalias.h gcc/tree-vect-analyze.c gcc/tree-vect-transform.c gcc/varray.c gcc/varray.h libcpp/makedepend.c libcpp/po/be.gmo libcpp/po/ca.gmo libcpp/po/da.gmo libcpp/po/de.gmo libcpp/po/el.gmo libcpp/po/es.gmo libcpp/po/fr.gmo libcpp/po/id.gmo libcpp/po/ja.gmo libcpp/po/nl.gmo libcpp/po/sv.gmo libcpp/po/tr.gmo libcpp/po/uk.gmo libcpp/po/vi.gmo libcpp/po/zh_CN.gmo libcpp/po/zh_TW.gmo libgomp/libgomp.info libgomp/testsuite/libgomp.graphite/pr4118.c libiberty/vmsbuild.com
diffstat 158 files changed, 0 insertions(+), 94299 deletions(-) [+]
line wrap: on
line diff
--- a/INSTALL/binaries.html	Mon May 24 12:48:09 2010 +0900
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,123 +0,0 @@
-<html lang="en">
-<head>
-<title>Installing GCC: Binaries</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Installing GCC: Binaries">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
-<!--
-Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
-1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
-2008 Free Software Foundation, Inc.
-
-   Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, the Front-Cover texts being (a) (see below), and
-with the Back-Cover Texts being (b) (see below).  A copy of the
-license is included in the section entitled "GNU Free Documentation License".
-
-(a) The FSF's Front-Cover Text is:
-
-     A GNU Manual
-
-(b) The FSF's Back-Cover Text is:
-
-     You have freedom to copy and modify this GNU Manual, like GNU
-     software.  Copies published by the Free Software Foundation raise
-     funds for GNU development.-->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
-</head>
-<body>
-<h1 class="settitle">Installing GCC: Binaries</h1>
-<a name="index-Binaries-1"></a><a name="index-Installing-GCC_003a-Binaries-2"></a>
-We are often asked about pre-compiled versions of GCC.  While we cannot
-provide these for all platforms, below you'll find links to binaries for
-various platforms where creating them by yourself is not easy due to various
-reasons.
-
-   <p>Please note that we did not create these binaries, nor do we
-support them.  If you have any problems installing them, please
-contact their makers.
-
-     <ul>
-<li>AIX:
-          <ul>
-<li><a href="http://www.bullfreeware.com">Bull's Freeware and Shareware Archive for AIX</a>;
-
-          <li><a href="http://pware.hvcc.edu">Hudson Valley Community College Open Source Software for IBM System p</a>;
-
-          <li><a href="http://www.perzl.org/aix/">AIX 5L and 6 Open Source Packages</a>. 
-</ul>
-
-     <li>DOS&mdash;<a href="http://www.delorie.com/djgpp/">DJGPP</a>.
-
-     <li>Renesas H8/300[HS]&mdash;<a href="http://h8300-hms.sourceforge.net/">GNU Development Tools for the Renesas H8/300[HS] Series</a>.
-
-     <li>HP-UX:
-          <ul>
-<li><a href="http://hpux.cs.utah.edu/">HP-UX Porting Center</a>;
-
-          <li><a href="ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/">Binaries for HP-UX 11.00 at Aachen University of Technology</a>. 
-</ul>
-
-     <li>Motorola 68HC11/68HC12&mdash;<a href="http://www.gnu-m68hc11.org">GNU Development Tools for the Motorola 68HC11/68HC12</a>.
-
-     <li><a href="http://www.sco.com/skunkware/devtools/index.html#gcc">SCO OpenServer/Unixware</a>.
-
-     <li>Solaris 2 (SPARC, Intel)&mdash;<a href="http://www.sunfreeware.com/">Sunfreeware</a>.
-
-     <li>SGI&mdash;<a href="http://freeware.sgi.com/">SGI Freeware</a>.
-
-     <li>Microsoft Windows:
-          <ul>
-<li>The <a href="http://sourceware.org/cygwin/">Cygwin</a> project;
-<li>The <a href="http://www.mingw.org/">MinGW</a> project. 
-</ul>
-
-     <li><a href="ftp://ftp.thewrittenword.com/packages/by-name/">The Written Word</a> offers binaries for
-AIX 4.3.3, 5.1 and 5.2,
-IRIX 6.5,
-Tru64 UNIX 4.0D and 5.1,
-GNU/Linux (i386),
-HP-UX 10.20, 11.00, and 11.11, and
-Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10.
-
-     <li><a href="http://www.openpkg.org/">OpenPKG</a> offers binaries for quite a
-number of platforms.
-
-     <li>The <a href="http://gcc.gnu.org/wiki/GFortranBinaries">GFortran Wiki</a> has
-links to GNU Fortran binaries for several platforms. 
-</ul>
-
-   <p>In addition to those specific offerings, you can get a binary
-distribution CD-ROM from the
-<a href="http://www.gnu.org/order/order.html">Free Software Foundation</a>. 
-It contains binaries for a number of platforms, and
-includes not only GCC, but other stuff as well.  The current CD does
-not contain the latest version of GCC, but it should allow
-bootstrapping the compiler.  An updated version of that disk is in the
-works.
-
-   <p><hr />
-<p><a href="./index.html">Return to the GCC Installation page</a>
-
-<!-- ***Specific**************************************************************** -->
-<!-- ***Old documentation****************************************************** -->
-<!-- ***GFDL******************************************************************** -->
-<!-- *************************************************************************** -->
-<!-- Part 6 The End of the Document -->
-</body></html>
-
--- a/INSTALL/build.html	Mon May 24 12:48:09 2010 +0900
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,313 +0,0 @@
-<html lang="en">
-<head>
-<title>Installing GCC: Building</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Installing GCC: Building">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
-<!--
-Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
-1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
-2008 Free Software Foundation, Inc.
-
-   Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, the Front-Cover texts being (a) (see below), and
-with the Back-Cover Texts being (b) (see below).  A copy of the
-license is included in the section entitled "GNU Free Documentation License".
-
-(a) The FSF's Front-Cover Text is:
-
-     A GNU Manual
-
-(b) The FSF's Back-Cover Text is:
-
-     You have freedom to copy and modify this GNU Manual, like GNU
-     software.  Copies published by the Free Software Foundation raise
-     funds for GNU development.-->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
-</head>
-<body>
-<h1 class="settitle">Installing GCC: Building</h1>
-<a name="index-Installing-GCC_003a-Building-1"></a>
-Now that GCC is configured, you are ready to build the compiler and
-runtime libraries.
-
-   <p>Some commands executed when making the compiler may fail (return a
-nonzero status) and be ignored by <samp><span class="command">make</span></samp>.  These failures, which
-are often due to files that were not found, are expected, and can safely
-be ignored.
-
-   <p>It is normal to have compiler warnings when compiling certain files. 
-Unless you are a GCC developer, you can generally ignore these warnings
-unless they cause compilation to fail.  Developers should attempt to fix
-any warnings encountered, however they can temporarily continue past
-warnings-as-errors by specifying the configure flag
-<samp><span class="option">--disable-werror</span></samp>.
-
-   <p>On certain old systems, defining certain environment variables such as
-<samp><span class="env">CC</span></samp> can interfere with the functioning of <samp><span class="command">make</span></samp>.
-
-   <p>If you encounter seemingly strange errors when trying to build the
-compiler in a directory other than the source directory, it could be
-because you have previously configured the compiler in the source
-directory.  Make sure you have done all the necessary preparations.
-
-   <p>If you build GCC on a BSD system using a directory stored in an old System
-V file system, problems may occur in running <samp><span class="command">fixincludes</span></samp> if the
-System V file system doesn't support symbolic links.  These problems
-result in a failure to fix the declaration of <code>size_t</code> in
-<samp><span class="file">sys/types.h</span></samp>.  If you find that <code>size_t</code> is a signed type and
-that type mismatches occur, this could be the cause.
-
-   <p>The solution is not to use such a directory for building GCC.
-
-   <p>Similarly, when building from SVN or snapshots, or if you modify
-<samp><span class="file">*.l</span></samp> files, you need the Flex lexical analyzer generator
-installed.  If you do not modify <samp><span class="file">*.l</span></samp> files, releases contain
-the Flex-generated files and you do not need Flex installed to build
-them.  There is still one Flex-based lexical analyzer (part of the
-build machinery, not of GCC itself) that is used even if you only
-build the C front end.
-
-   <p>When building from SVN or snapshots, or if you modify Texinfo
-documentation, you need version 4.7 or later of Texinfo installed if you
-want Info documentation to be regenerated.  Releases contain Info
-documentation pre-built for the unmodified documentation in the release.
-
-<h3 class="section"><a name="TOC0"></a>Building a native compiler</h3>
-
-<p>For a native build, the default configuration is to perform
-a 3-stage bootstrap of the compiler when &lsquo;<samp><span class="samp">make</span></samp>&rsquo; is invoked. 
-This will build the entire GCC system and ensure that it compiles
-itself correctly.  It can be disabled with the <samp><span class="option">--disable-bootstrap</span></samp>
-parameter to &lsquo;<samp><span class="samp">configure</span></samp>&rsquo;, but bootstrapping is suggested because
-the compiler will be tested more completely and could also have
-better performance.
-
-   <p>The bootstrapping process will complete the following steps:
-
-     <ul>
-<li>Build tools necessary to build the compiler.
-
-     <li>Perform a 3-stage bootstrap of the compiler.  This includes building
-three times the target tools for use by the compiler such as binutils
-(bfd, binutils, gas, gprof, ld, and opcodes) if they have been
-individually linked or moved into the top level GCC source tree before
-configuring.
-
-     <li>Perform a comparison test of the stage2 and stage3 compilers.
-
-     <li>Build runtime libraries using the stage3 compiler from the previous step.
-
-   </ul>
-
-   <p>If you are short on disk space you might consider &lsquo;<samp><span class="samp">make
-bootstrap-lean</span></samp>&rsquo; instead.  The sequence of compilation is the
-same described above, but object files from the stage1 and
-stage2 of the 3-stage bootstrap of the compiler are deleted as
-soon as they are no longer needed.
-
-   <p>If you wish to use non-default GCC flags when compiling the stage2
-and stage3 compilers, set <code>BOOT_CFLAGS</code> on the command line when
-doing &lsquo;<samp><span class="samp">make</span></samp>&rsquo;.  For example, if you want to save additional space
-during the bootstrap and in the final installation as well, you can
-build the compiler binaries without debugging information as in the
-following example.  This will save roughly 40% of disk space both for
-the bootstrap and the final installation.  (Libraries will still contain
-debugging information.)
-
-<pre class="smallexample">          make BOOT_CFLAGS='-O' bootstrap
-</pre>
-   <p>You can place non-default optimization flags into <code>BOOT_CFLAGS</code>; they
-are less well tested here than the default of &lsquo;<samp><span class="samp">-g -O2</span></samp>&rsquo;, but should
-still work.  In a few cases, you may find that you need to specify special
-flags such as <samp><span class="option">-msoft-float</span></samp> here to complete the bootstrap; or,
-if the native compiler miscompiles the stage1 compiler, you may need
-to work around this, by choosing <code>BOOT_CFLAGS</code> to avoid the parts
-of the stage1 compiler that were miscompiled, or by using &lsquo;<samp><span class="samp">make
-bootstrap4</span></samp>&rsquo; to increase the number of stages of bootstrap.
-
-   <p><code>BOOT_CFLAGS</code> does not apply to bootstrapped target libraries. 
-Since these are always compiled with the compiler currently being
-bootstrapped, you can use <code>CFLAGS_FOR_TARGET</code> to modify their
-compilation flags, as for non-bootstrapped target libraries. 
-Again, if the native compiler miscompiles the stage1 compiler, you may
-need to work around this by avoiding non-working parts of the stage1
-compiler.  Use <code>STAGE1_LIBCFLAGS</code> to this end.
-
-   <p>If you used the flag <samp><span class="option">--enable-languages=...</span></samp> to restrict
-the compilers to be built, only those you've actually enabled will be
-built.  This will of course only build those runtime libraries, for
-which the particular compiler has been built.  Please note,
-that re-defining <samp><span class="env">LANGUAGES</span></samp> when calling &lsquo;<samp><span class="samp">make</span></samp>&rsquo;
-<strong>does not</strong> work anymore!
-
-   <p>If the comparison of stage2 and stage3 fails, this normally indicates
-that the stage2 compiler has compiled GCC incorrectly, and is therefore
-a potentially serious bug which you should investigate and report.  (On
-a few systems, meaningful comparison of object files is impossible; they
-always appear &ldquo;different&rdquo;.  If you encounter this problem, you will
-need to disable comparison in the <samp><span class="file">Makefile</span></samp>.)
-
-   <p>If you do not want to bootstrap your compiler, you can configure with
-<samp><span class="option">--disable-bootstrap</span></samp>.  In particular cases, you may want to
-bootstrap your compiler even if the target system is not the same as
-the one you are building on: for example, you could build a
-<code>powerpc-unknown-linux-gnu</code> toolchain on a
-<code>powerpc64-unknown-linux-gnu</code> host.  In this case, pass
-<samp><span class="option">--enable-bootstrap</span></samp> to the configure script.
-
-<h3 class="section"><a name="TOC1"></a>Building a cross compiler</h3>
-
-<p>When building a cross compiler, it is not generally possible to do a
-3-stage bootstrap of the compiler.  This makes for an interesting problem
-as parts of GCC can only be built with GCC.
-
-   <p>To build a cross compiler, we first recommend building and installing a
-native compiler.  You can then use the native GCC compiler to build the
-cross compiler.  The installed native compiler needs to be GCC version
-2.95 or later.
-
-   <p>If the cross compiler is to be built with support for the Java
-programming language and the ability to compile .java source files is
-desired, the installed native compiler used to build the cross
-compiler needs to be the same GCC version as the cross compiler.  In
-addition the cross compiler needs to be configured with
-<samp><span class="option">--with-ecj-jar=...</span></samp>.
-
-   <p>Assuming you have already installed a native copy of GCC and configured
-your cross compiler, issue the command <samp><span class="command">make</span></samp>, which performs the
-following steps:
-
-     <ul>
-<li>Build host tools necessary to build the compiler.
-
-     <li>Build target tools for use by the compiler such as binutils (bfd,
-binutils, gas, gprof, ld, and opcodes)
-if they have been individually linked or moved into the top level GCC source
-tree before configuring.
-
-     <li>Build the compiler (single stage only).
-
-     <li>Build runtime libraries using the compiler from the previous step. 
-</ul>
-
-   <p>Note that if an error occurs in any step the make process will exit.
-
-   <p>If you are not building GNU binutils in the same source tree as GCC,
-you will need a cross-assembler and cross-linker installed before
-configuring GCC.  Put them in the directory
-<samp><var>prefix</var><span class="file">/</span><var>target</var><span class="file">/bin</span></samp>.  Here is a table of the tools
-you should put in this directory:
-
-     <dl>
-<dt><samp><span class="file">as</span></samp><dd>This should be the cross-assembler.
-
-     <br><dt><samp><span class="file">ld</span></samp><dd>This should be the cross-linker.
-
-     <br><dt><samp><span class="file">ar</span></samp><dd>This should be the cross-archiver: a program which can manipulate
-archive files (linker libraries) in the target machine's format.
-
-     <br><dt><samp><span class="file">ranlib</span></samp><dd>This should be a program to construct a symbol table in an archive file. 
-</dl>
-
-   <p>The installation of GCC will find these programs in that directory,
-and copy or link them to the proper place to for the cross-compiler to
-find them when run later.
-
-   <p>The easiest way to provide these files is to build the Binutils package. 
-Configure it with the same <samp><span class="option">--host</span></samp> and <samp><span class="option">--target</span></samp>
-options that you use for configuring GCC, then build and install
-them.  They install their executables automatically into the proper
-directory.  Alas, they do not support all the targets that GCC
-supports.
-
-   <p>If you are not building a C library in the same source tree as GCC,
-you should also provide the target libraries and headers before
-configuring GCC, specifying the directories with
-<samp><span class="option">--with-sysroot</span></samp> or <samp><span class="option">--with-headers</span></samp> and
-<samp><span class="option">--with-libs</span></samp>.  Many targets also require &ldquo;start files&rdquo; such
-as <samp><span class="file">crt0.o</span></samp> and
-<samp><span class="file">crtn.o</span></samp> which are linked into each executable.  There may be several
-alternatives for <samp><span class="file">crt0.o</span></samp>, for use with profiling or other
-compilation options.  Check your target's definition of
-<code>STARTFILE_SPEC</code> to find out what start files it uses.
-
-<h3 class="section"><a name="TOC2"></a>Building in parallel</h3>
-
-<p>GNU Make 3.79 and above, which is necessary to build GCC, support
-building in parallel.  To activate this, you can use &lsquo;<samp><span class="samp">make -j 2</span></samp>&rsquo;
-instead of &lsquo;<samp><span class="samp">make</span></samp>&rsquo;.  You can also specify a bigger number, and
-in most cases using a value greater than the number of processors in
-your machine will result in fewer and shorter I/O latency hits, thus
-improving overall throughput; this is especially true for slow drives
-and network filesystems.
-
-<h3 class="section"><a name="TOC3"></a>Building the Ada compiler</h3>
-
-<p>In order to build GNAT, the Ada compiler, you need a working GNAT
-compiler (GCC version 3.4 or later). 
-This includes GNAT tools such as <samp><span class="command">gnatmake</span></samp> and
-<samp><span class="command">gnatlink</span></samp>, since the Ada front end is written in Ada and
-uses some GNAT-specific extensions.
-
-   <p>In order to build a cross compiler, it is suggested to install
-the new compiler as native first, and then use it to build the cross
-compiler.
-
-   <p><samp><span class="command">configure</span></samp> does not test whether the GNAT installation works
-and has a sufficiently recent version; if too old a GNAT version is
-installed, the build will fail unless <samp><span class="option">--enable-languages</span></samp> is
-used to disable building the Ada front end.
-
-   <p><samp><span class="env">ADA_INCLUDE_PATH</span></samp> and <samp><span class="env">ADA_OBJECT_PATH</span></samp> environment variables
-must not be set when building the Ada compiler, the Ada tools, or the
-Ada runtime libraries. You can check that your build environment is clean
-by verifying that &lsquo;<samp><span class="samp">gnatls -v</span></samp>&rsquo; lists only one explicit path in each
-section.
-
-<h3 class="section"><a name="TOC4"></a>Building with profile feedback</h3>
-
-<p>It is possible to use profile feedback to optimize the compiler itself.  This
-should result in a faster compiler binary.  Experiments done on x86 using gcc
-3.3 showed approximately 7 percent speedup on compiling C programs.  To
-bootstrap the compiler with profile feedback, use <code>make profiledbootstrap</code>.
-
-   <p>When &lsquo;<samp><span class="samp">make profiledbootstrap</span></samp>&rsquo; is run, it will first build a <code>stage1</code>
-compiler.  This compiler is used to build a <code>stageprofile</code> compiler
-instrumented to collect execution counts of instruction and branch
-probabilities.  Then runtime libraries are compiled with profile collected. 
-Finally a <code>stagefeedback</code> compiler is built using the information collected.
-
-   <p>Unlike standard bootstrap, several additional restrictions apply.  The
-compiler used to build <code>stage1</code> needs to support a 64-bit integral type. 
-It is recommended to only use GCC for this.  Also parallel make is currently
-not supported since collisions in profile collecting may occur.
-
-   <p><hr />
-<p><a href="./index.html">Return to the GCC Installation page</a>
-
-<!-- ***Testing***************************************************************** -->
-<!-- ***Final install*********************************************************** -->
-<!-- ***Binaries**************************************************************** -->
-<!-- ***Specific**************************************************************** -->
-<!-- ***Old documentation****************************************************** -->
-<!-- ***GFDL******************************************************************** -->
-<!-- *************************************************************************** -->
-<!-- Part 6 The End of the Document -->
-</body></html>
-
--- a/INSTALL/configure.html	Mon May 24 12:48:09 2010 +0900
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,1078 +0,0 @@
-<html lang="en">
-<head>
-<title>Installing GCC: Configuration</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Installing GCC: Configuration">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
-<!--
-Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
-1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
-2008 Free Software Foundation, Inc.
-
-   Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, the Front-Cover texts being (a) (see below), and
-with the Back-Cover Texts being (b) (see below).  A copy of the
-license is included in the section entitled "GNU Free Documentation License".
-
-(a) The FSF's Front-Cover Text is:
-
-     A GNU Manual
-
-(b) The FSF's Back-Cover Text is:
-
-     You have freedom to copy and modify this GNU Manual, like GNU
-     software.  Copies published by the Free Software Foundation raise
-     funds for GNU development.-->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
-</head>
-<body>
-<h1 class="settitle">Installing GCC: Configuration</h1>
-<a name="index-Configuration-1"></a><a name="index-Installing-GCC_003a-Configuration-2"></a>
-Like most GNU software, GCC must be configured before it can be built. 
-This document describes the recommended configuration procedure
-for both native and cross targets.
-
-   <p>We use <var>srcdir</var> to refer to the toplevel source directory for
-GCC; we use <var>objdir</var> to refer to the toplevel build/object directory.
-
-   <p>If you obtained the sources via SVN, <var>srcdir</var> must refer to the top
-<samp><span class="file">gcc</span></samp> directory, the one where the <samp><span class="file">MAINTAINERS</span></samp> can be found,
-and not its <samp><span class="file">gcc</span></samp> subdirectory, otherwise the build will fail.
-
-   <p>If either <var>srcdir</var> or <var>objdir</var> is located on an automounted NFS
-file system, the shell's built-in <samp><span class="command">pwd</span></samp> command will return
-temporary pathnames.  Using these can lead to various sorts of build
-problems.  To avoid this issue, set the <samp><span class="env">PWDCMD</span></samp> environment
-variable to an automounter-aware <samp><span class="command">pwd</span></samp> command, e.g.,
-<samp><span class="command">pawd</span></samp> or &lsquo;<samp><span class="samp">amq -w</span></samp>&rsquo;, during the configuration and build
-phases.
-
-   <p>First, we <strong>highly</strong> recommend that GCC be built into a
-separate directory than the sources which does <strong>not</strong> reside
-within the source tree.  This is how we generally build GCC; building
-where <var>srcdir</var> == <var>objdir</var> should still work, but doesn't
-get extensive testing; building where <var>objdir</var> is a subdirectory
-of <var>srcdir</var> is unsupported.
-
-   <p>If you have previously built GCC in the same directory for a
-different target machine, do &lsquo;<samp><span class="samp">make distclean</span></samp>&rsquo; to delete all files
-that might be invalid.  One of the files this deletes is <samp><span class="file">Makefile</span></samp>;
-if &lsquo;<samp><span class="samp">make distclean</span></samp>&rsquo; complains that <samp><span class="file">Makefile</span></samp> does not exist
-or issues a message like &ldquo;don't know how to make distclean&rdquo; it probably
-means that the directory is already suitably clean.  However, with the
-recommended method of building in a separate <var>objdir</var>, you should
-simply use a different <var>objdir</var> for each target.
-
-   <p>Second, when configuring a native system, either <samp><span class="command">cc</span></samp> or
-<samp><span class="command">gcc</span></samp> must be in your path or you must set <samp><span class="env">CC</span></samp> in
-your environment before running configure.  Otherwise the configuration
-scripts may fail.
-
-   <p>To configure GCC:
-
-<pre class="smallexample">        % mkdir <var>objdir</var>
-        % cd <var>objdir</var>
-        % <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
-</pre>
-   <h3 class="heading"><a name="TOC0"></a>Distributor options</h3>
-
-<p>If you will be distributing binary versions of GCC, with modifications
-to the source code, you should use the options described in this
-section to make clear that your version contains modifications.
-
-     <dl>
-<dt><code>--with-pkgversion=</code><var>version</var><dd>Specify a string that identifies your package.  You may wish
-to include a build number or build date.  This version string will be
-included in the output of <samp><span class="command">gcc --version</span></samp>.  This suffix does
-not replace the default version string, only the &lsquo;<samp><span class="samp">GCC</span></samp>&rsquo; part.
-
-     <p>The default value is &lsquo;<samp><span class="samp">GCC</span></samp>&rsquo;.
-
-     <br><dt><code>--with-bugurl=</code><var>url</var><dd>Specify the URL that users should visit if they wish to report a bug. 
-You are of course welcome to forward bugs reported to you to the FSF,
-if you determine that they are not bugs in your modifications.
-
-     <p>The default value refers to the FSF's GCC bug tracker.
-
-   </dl>
-
-<h3 class="heading"><a name="TOC1"></a>Target specification</h3>
-
-     <ul>
-<li>GCC has code to correctly determine the correct value for <var>target</var>
-for nearly all native systems.  Therefore, we highly recommend you not
-provide a configure target when configuring a native compiler.
-
-     <li><var>target</var> must be specified as <samp><span class="option">--target=</span><var>target</var></samp>
-when configuring a cross compiler; examples of valid targets would be
-m68k-coff, sh-elf, etc.
-
-     <li>Specifying just <var>target</var> instead of <samp><span class="option">--target=</span><var>target</var></samp>
-implies that the host defaults to <var>target</var>. 
-</ul>
-
-<h3 class="heading"><a name="TOC2"></a>Options specification</h3>
-
-<p>Use <var>options</var> to override several configure time options for
-GCC.  A list of supported <var>options</var> follows; &lsquo;<samp><span class="samp">configure
---help</span></samp>&rsquo; may list other options, but those not listed below may not
-work and should not normally be used.
-
-   <p>Note that each <samp><span class="option">--enable</span></samp> option has a corresponding
-<samp><span class="option">--disable</span></samp> option and that each <samp><span class="option">--with</span></samp> option has a
-corresponding <samp><span class="option">--without</span></samp> option.
-
-     <dl>
-<dt><code>--prefix=</code><var>dirname</var><dd>Specify the toplevel installation
-directory.  This is the recommended way to install the tools into a directory
-other than the default.  The toplevel installation directory defaults to
-<samp><span class="file">/usr/local</span></samp>.
-
-     <p>We <strong>highly</strong> recommend against <var>dirname</var> being the same or a
-subdirectory of <var>objdir</var> or vice versa.  If specifying a directory
-beneath a user's home directory tree, some shells will not expand
-<var>dirname</var> correctly if it contains the &lsquo;<samp><span class="samp">~</span></samp>&rsquo; metacharacter; use
-<samp><span class="env">$HOME</span></samp> instead.
-
-     <p>The following standard <samp><span class="command">autoconf</span></samp> options are supported.  Normally you
-should not need to use these options.
-          <dl>
-<dt><code>--exec-prefix=</code><var>dirname</var><dd>Specify the toplevel installation directory for architecture-dependent
-files.  The default is <samp><var>prefix</var></samp>.
-
-          <br><dt><code>--bindir=</code><var>dirname</var><dd>Specify the installation directory for the executables called by users
-(such as <samp><span class="command">gcc</span></samp> and <samp><span class="command">g++</span></samp>).  The default is
-<samp><var>exec-prefix</var><span class="file">/bin</span></samp>.
-
-          <br><dt><code>--libdir=</code><var>dirname</var><dd>Specify the installation directory for object code libraries and
-internal data files of GCC.  The default is <samp><var>exec-prefix</var><span class="file">/lib</span></samp>.
-
-          <br><dt><code>--libexecdir=</code><var>dirname</var><dd>Specify the installation directory for internal executables of GCC. 
-The default is <samp><var>exec-prefix</var><span class="file">/libexec</span></samp>.
-
-          <br><dt><code>--with-slibdir=</code><var>dirname</var><dd>Specify the installation directory for the shared libgcc library.  The
-default is <samp><var>libdir</var></samp>.
-
-          <br><dt><code>--infodir=</code><var>dirname</var><dd>Specify the installation directory for documentation in info format. 
-The default is <samp><var>prefix</var><span class="file">/info</span></samp>.
-
-          <br><dt><code>--datadir=</code><var>dirname</var><dd>Specify the installation directory for some architecture-independent
-data files referenced by GCC.  The default is <samp><var>prefix</var><span class="file">/share</span></samp>.
-
-          <br><dt><code>--mandir=</code><var>dirname</var><dd>Specify the installation directory for manual pages.  The default is
-<samp><var>prefix</var><span class="file">/man</span></samp>.  (Note that the manual pages are only extracts from
-the full GCC manuals, which are provided in Texinfo format.  The manpages
-are derived by an automatic conversion process from parts of the full
-manual.)
-
-          <br><dt><code>--with-gxx-include-dir=</code><var>dirname</var><dd>Specify
-the installation directory for G++ header files.  The default is
-<samp><var>prefix</var><span class="file">/include/c++/</span><var>version</var></samp>.
-
-     </dl>
-
-     <br><dt><code>--program-prefix=</code><var>prefix</var><dd>GCC supports some transformations of the names of its programs when
-installing them.  This option prepends <var>prefix</var> to the names of
-programs to install in <var>bindir</var> (see above).  For example, specifying
-<samp><span class="option">--program-prefix=foo-</span></samp> would result in &lsquo;<samp><span class="samp">gcc</span></samp>&rsquo;
-being installed as <samp><span class="file">/usr/local/bin/foo-gcc</span></samp>.
-
-     <br><dt><code>--program-suffix=</code><var>suffix</var><dd>Appends <var>suffix</var> to the names of programs to install in <var>bindir</var>
-(see above).  For example, specifying <samp><span class="option">--program-suffix=-3.1</span></samp>
-would result in &lsquo;<samp><span class="samp">gcc</span></samp>&rsquo; being installed as
-<samp><span class="file">/usr/local/bin/gcc-3.1</span></samp>.
-
-     <br><dt><code>--program-transform-name=</code><var>pattern</var><dd>Applies the &lsquo;<samp><span class="samp">sed</span></samp>&rsquo; script <var>pattern</var> to be applied to the names
-of programs to install in <var>bindir</var> (see above).  <var>pattern</var> has to
-consist of one or more basic &lsquo;<samp><span class="samp">sed</span></samp>&rsquo; editing commands, separated by
-semicolons.  For example, if you want the &lsquo;<samp><span class="samp">gcc</span></samp>&rsquo; program name to be
-transformed to the installed program <samp><span class="file">/usr/local/bin/myowngcc</span></samp> and
-the &lsquo;<samp><span class="samp">g++</span></samp>&rsquo; program name to be transformed to
-<samp><span class="file">/usr/local/bin/gspecial++</span></samp> without changing other program names,
-you could use the pattern
-<samp><span class="option">--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'</span></samp>
-to achieve this effect.
-
-     <p>All three options can be combined and used together, resulting in more
-complex conversion patterns.  As a basic rule, <var>prefix</var> (and
-<var>suffix</var>) are prepended (appended) before further transformations
-can happen with a special transformation script <var>pattern</var>.
-
-     <p>As currently implemented, this option only takes effect for native
-builds; cross compiler binaries' names are not transformed even when a
-transformation is explicitly asked for by one of these options.
-
-     <p>For native builds, some of the installed programs are also installed
-with the target alias in front of their name, as in
-&lsquo;<samp><span class="samp">i686-pc-linux-gnu-gcc</span></samp>&rsquo;.  All of the above transformations happen
-before the target alias is prepended to the name&mdash;so, specifying
-<samp><span class="option">--program-prefix=foo-</span></samp> and <samp><span class="option">program-suffix=-3.1</span></samp>, the
-resulting binary would be installed as
-<samp><span class="file">/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1</span></samp>.
-
-     <p>As a last shortcoming, none of the installed Ada programs are
-transformed yet, which will be fixed in some time.
-
-     <br><dt><code>--with-local-prefix=</code><var>dirname</var><dd>Specify the
-installation directory for local include files.  The default is
-<samp><span class="file">/usr/local</span></samp>.  Specify this option if you want the compiler to
-search directory <samp><var>dirname</var><span class="file">/include</span></samp> for locally installed
-header files <em>instead</em> of <samp><span class="file">/usr/local/include</span></samp>.
-
-     <p>You should specify <samp><span class="option">--with-local-prefix</span></samp> <strong>only</strong> if your
-site has a different convention (not <samp><span class="file">/usr/local</span></samp>) for where to put
-site-specific files.
-
-     <p>The default value for <samp><span class="option">--with-local-prefix</span></samp> is <samp><span class="file">/usr/local</span></samp>
-regardless of the value of <samp><span class="option">--prefix</span></samp>.  Specifying
-<samp><span class="option">--prefix</span></samp> has no effect on which directory GCC searches for
-local header files.  This may seem counterintuitive, but actually it is
-logical.
-
-     <p>The purpose of <samp><span class="option">--prefix</span></samp> is to specify where to <em>install
-GCC</em>.  The local header files in <samp><span class="file">/usr/local/include</span></samp>&mdash;if you put
-any in that directory&mdash;are not part of GCC.  They are part of other
-programs&mdash;perhaps many others.  (GCC installs its own header files in
-another directory which is based on the <samp><span class="option">--prefix</span></samp> value.)
-
-     <p>Both the local-prefix include directory and the GCC-prefix include
-directory are part of GCC's &ldquo;system include&rdquo; directories.  Although these
-two directories are not fixed, they need to be searched in the proper
-order for the correct processing of the include_next directive.  The
-local-prefix include directory is searched before the GCC-prefix
-include directory.  Another characteristic of system include directories
-is that pedantic warnings are turned off for headers in these directories.
-
-     <p>Some autoconf macros add <samp><span class="option">-I </span><var>directory</var></samp> options to the
-compiler command line, to ensure that directories containing installed
-packages' headers are searched.  When <var>directory</var> is one of GCC's
-system include directories, GCC will ignore the option so that system
-directories continue to be processed in the correct order.  This
-may result in a search order different from what was specified but the
-directory will still be searched.
-
-     <p>GCC automatically searches for ordinary libraries using
-<samp><span class="env">GCC_EXEC_PREFIX</span></samp>.  Thus, when the same installation prefix is
-used for both GCC and packages, GCC will automatically search for
-both headers and libraries.  This provides a configuration that is
-easy to use.  GCC behaves in a manner similar to that when it is
-installed as a system compiler in <samp><span class="file">/usr</span></samp>.
-
-     <p>Sites that need to install multiple versions of GCC may not want to
-use the above simple configuration.  It is possible to use the
-<samp><span class="option">--program-prefix</span></samp>, <samp><span class="option">--program-suffix</span></samp> and
-<samp><span class="option">--program-transform-name</span></samp> options to install multiple versions
-into a single directory, but it may be simpler to use different prefixes
-and the <samp><span class="option">--with-local-prefix</span></samp> option to specify the location of the
-site-specific files for each version.  It will then be necessary for
-users to specify explicitly the location of local site libraries
-(e.g., with <samp><span class="env">LIBRARY_PATH</span></samp>).
-
-     <p>The same value can be used for both <samp><span class="option">--with-local-prefix</span></samp> and
-<samp><span class="option">--prefix</span></samp> provided it is not <samp><span class="file">/usr</span></samp>.  This can be used
-to avoid the default search of <samp><span class="file">/usr/local/include</span></samp>.
-
-     <p><strong>Do not</strong> specify <samp><span class="file">/usr</span></samp> as the <samp><span class="option">--with-local-prefix</span></samp>! 
-The directory you use for <samp><span class="option">--with-local-prefix</span></samp> <strong>must not</strong>
-contain any of the system's standard header files.  If it did contain
-them, certain programs would be miscompiled (including GNU Emacs, on
-certain targets), because this would override and nullify the header
-file corrections made by the <samp><span class="command">fixincludes</span></samp> script.
-
-     <p>Indications are that people who use this option use it based on mistaken
-ideas of what it is for.  People use it as if it specified where to
-install part of GCC.  Perhaps they make this assumption because
-installing GCC creates the directory.
-
-     <br><dt><code>--enable-shared[=</code><var>package</var><code>[,...]]</code><dd>Build shared versions of libraries, if shared libraries are supported on
-the target platform.  Unlike GCC 2.95.x and earlier, shared libraries
-are enabled by default on all platforms that support shared libraries.
-
-     <p>If a list of packages is given as an argument, build shared libraries
-only for the listed packages.  For other packages, only static libraries
-will be built.  Package names currently recognized in the GCC tree are
-&lsquo;<samp><span class="samp">libgcc</span></samp>&rsquo; (also known as &lsquo;<samp><span class="samp">gcc</span></samp>&rsquo;), &lsquo;<samp><span class="samp">libstdc++</span></samp>&rsquo; (not
-&lsquo;<samp><span class="samp">libstdc++-v3</span></samp>&rsquo;), &lsquo;<samp><span class="samp">libffi</span></samp>&rsquo;, &lsquo;<samp><span class="samp">zlib</span></samp>&rsquo;, &lsquo;<samp><span class="samp">boehm-gc</span></samp>&rsquo;,
-&lsquo;<samp><span class="samp">ada</span></samp>&rsquo;, &lsquo;<samp><span class="samp">libada</span></samp>&rsquo;, &lsquo;<samp><span class="samp">libjava</span></samp>&rsquo; and &lsquo;<samp><span class="samp">libobjc</span></samp>&rsquo;. 
-Note &lsquo;<samp><span class="samp">libiberty</span></samp>&rsquo; does not support shared libraries at all.
-
-     <p>Use <samp><span class="option">--disable-shared</span></samp> to build only static libraries.  Note that
-<samp><span class="option">--disable-shared</span></samp> does not accept a list of package names as
-argument, only <samp><span class="option">--enable-shared</span></samp> does.
-
-     <br><dt><code><a name="with_002dgnu_002das"></a>--with-gnu-as</code><dd>Specify that the compiler should assume that the
-assembler it finds is the GNU assembler.  However, this does not modify
-the rules to find an assembler and will result in confusion if the
-assembler found is not actually the GNU assembler.  (Confusion may also
-result if the compiler finds the GNU assembler but has not been
-configured with <samp><span class="option">--with-gnu-as</span></samp>.)  If you have more than one
-assembler installed on your system, you may want to use this option in
-connection with <samp><span class="option">--with-as=</span><var>pathname</var></samp> or
-<samp><span class="option">--with-build-time-tools=</span><var>pathname</var></samp>.
-
-     <p>The following systems are the only ones where it makes a difference
-whether you use the GNU assembler.  On any other system,
-<samp><span class="option">--with-gnu-as</span></samp> has no effect.
-
-          <ul>
-<li>&lsquo;<samp><span class="samp">hppa1.0-</span><var>any</var><span class="samp">-</span><var>any</var></samp>&rsquo;
-<li>&lsquo;<samp><span class="samp">hppa1.1-</span><var>any</var><span class="samp">-</span><var>any</var></samp>&rsquo;
-<li>&lsquo;<samp><span class="samp">sparc-sun-solaris2.</span><var>any</var></samp>&rsquo;
-<li>&lsquo;<samp><span class="samp">sparc64-</span><var>any</var><span class="samp">-solaris2.</span><var>any</var></samp>&rsquo;
-</ul>
-
-     <br><dt><code><a name="with_002das"></a>--with-as=</code><var>pathname</var><dd>Specify that the compiler should use the assembler pointed to by
-<var>pathname</var>, rather than the one found by the standard rules to find
-an assembler, which are:
-          <ul>
-<li>Unless GCC is being built with a cross compiler, check the
-<samp><var>libexec</var><span class="file">/gcc/</span><var>target</var><span class="file">/</span><var>version</var></samp> directory. 
-<var>libexec</var> defaults to <samp><var>exec-prefix</var><span class="file">/libexec</span></samp>;
-<var>exec-prefix</var> defaults to <var>prefix</var>, which
-defaults to <samp><span class="file">/usr/local</span></samp> unless overridden by the
-<samp><span class="option">--prefix=</span><var>pathname</var></samp> switch described above.  <var>target</var>
-is the target system triple, such as &lsquo;<samp><span class="samp">sparc-sun-solaris2.7</span></samp>&rsquo;, and
-<var>version</var> denotes the GCC version, such as 3.0.
-
-          <li>If the target system is the same that you are building on, check
-operating system specific directories (e.g. <samp><span class="file">/usr/ccs/bin</span></samp> on
-Sun Solaris 2).
-
-          <li>Check in the <samp><span class="env">PATH</span></samp> for a tool whose name is prefixed by the
-target system triple.
-
-          <li>Check in the <samp><span class="env">PATH</span></samp> for a tool whose name is not prefixed by the
-target system triple, if the host and target system triple are
-the same (in other words, we use a host tool if it can be used for
-the target as well). 
-</ul>
-
-     <p>You may want to use <samp><span class="option">--with-as</span></samp> if no assembler
-is installed in the directories listed above, or if you have multiple
-assemblers installed and want to choose one that is not found by the
-above rules.
-
-     <br><dt><code><a name="with_002dgnu_002dld"></a>--with-gnu-ld</code><dd>Same as <a href="#with-gnu-as"><samp><span class="option">--with-gnu-as</span></samp></a>
-but for the linker.
-
-     <br><dt><code>--with-ld=</code><var>pathname</var><dd>Same as <a href="#with-as"><samp><span class="option">--with-as</span></samp></a>
-but for the linker.
-
-     <br><dt><code>--with-stabs</code><dd>Specify that stabs debugging
-information should be used instead of whatever format the host normally
-uses.  Normally GCC uses the same debug format as the host system.
-
-     <p>On MIPS based systems and on Alphas, you must specify whether you want
-GCC to create the normal ECOFF debugging format, or to use BSD-style
-stabs passed through the ECOFF symbol table.  The normal ECOFF debug
-format cannot fully handle languages other than C.  BSD stabs format can
-handle other languages, but it only works with the GNU debugger GDB.
-
-     <p>Normally, GCC uses the ECOFF debugging format by default; if you
-prefer BSD stabs, specify <samp><span class="option">--with-stabs</span></samp> when you configure GCC.
-
-     <p>No matter which default you choose when you configure GCC, the user
-can use the <samp><span class="option">-gcoff</span></samp> and <samp><span class="option">-gstabs+</span></samp> options to specify explicitly
-the debug format for a particular compilation.
-
-     <p><samp><span class="option">--with-stabs</span></samp> is meaningful on the ISC system on the 386, also, if
-<samp><span class="option">--with-gas</span></samp> is used.  It selects use of stabs debugging
-information embedded in COFF output.  This kind of debugging information
-supports C++ well; ordinary COFF debugging information does not.
-
-     <p><samp><span class="option">--with-stabs</span></samp> is also meaningful on 386 systems running SVR4.  It
-selects use of stabs debugging information embedded in ELF output.  The
-C++ compiler currently (2.6.0) does not support the DWARF debugging
-information normally used on 386 SVR4 platforms; stabs provide a
-workable alternative.  This requires gas and gdb, as the normal SVR4
-tools can not generate or interpret stabs.
-
-     <br><dt><code>--disable-multilib</code><dd>Specify that multiple target
-libraries to support different target variants, calling
-conventions, etc. should not be built.  The default is to build a
-predefined set of them.
-
-     <p>Some targets provide finer-grained control over which multilibs are built
-(e.g., <samp><span class="option">--disable-softfloat</span></samp>):
-          <dl>
-<dt><code>arc-*-elf*</code><dd>biendian.
-
-          <br><dt><code>arm-*-*</code><dd>fpu, 26bit, underscore, interwork, biendian, nofmult.
-
-          <br><dt><code>m68*-*-*</code><dd>softfloat, m68881, m68000, m68020.
-
-          <br><dt><code>mips*-*-*</code><dd>single-float, biendian, softfloat.
-
-          <br><dt><code>powerpc*-*-*, rs6000*-*-*</code><dd>aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
-sysv, aix.
-
-     </dl>
-
-     <br><dt><code>--enable-threads</code><dd>Specify that the target
-supports threads.  This affects the Objective-C compiler and runtime
-library, and exception handling for other languages like C++ and Java. 
-On some systems, this is the default.
-
-     <p>In general, the best (and, in many cases, the only known) threading
-model available will be configured for use.  Beware that on some
-systems, GCC has not been taught what threading models are generally
-available for the system.  In this case, <samp><span class="option">--enable-threads</span></samp> is an
-alias for <samp><span class="option">--enable-threads=single</span></samp>.
-
-     <br><dt><code>--disable-threads</code><dd>Specify that threading support should be disabled for the system. 
-This is an alias for <samp><span class="option">--enable-threads=single</span></samp>.
-
-     <br><dt><code>--enable-threads=</code><var>lib</var><dd>Specify that
-<var>lib</var> is the thread support library.  This affects the Objective-C
-compiler and runtime library, and exception handling for other languages
-like C++ and Java.  The possibilities for <var>lib</var> are:
-
-          <dl>
-<dt><code>aix</code><dd>AIX thread support. 
-<br><dt><code>dce</code><dd>DCE thread support. 
-<br><dt><code>gnat</code><dd>Ada tasking support.  For non-Ada programs, this setting is equivalent
-to &lsquo;<samp><span class="samp">single</span></samp>&rsquo;.  When used in conjunction with the Ada run time, it
-causes GCC to use the same thread primitives as Ada uses.  This option
-is necessary when using both Ada and the back end exception handling,
-which is the default for most Ada targets. 
-<br><dt><code>mach</code><dd>Generic MACH thread support, known to work on NeXTSTEP.  (Please note
-that the file needed to support this configuration, <samp><span class="file">gthr-mach.h</span></samp>, is
-missing and thus this setting will cause a known bootstrap failure.) 
-<br><dt><code>no</code><dd>This is an alias for &lsquo;<samp><span class="samp">single</span></samp>&rsquo;. 
-<br><dt><code>posix</code><dd>Generic POSIX/Unix98 thread support. 
-<br><dt><code>posix95</code><dd>Generic POSIX/Unix95 thread support. 
-<br><dt><code>rtems</code><dd>RTEMS thread support. 
-<br><dt><code>single</code><dd>Disable thread support, should work for all platforms. 
-<br><dt><code>solaris</code><dd>Sun Solaris 2 thread support. 
-<br><dt><code>vxworks</code><dd>VxWorks thread support. 
-<br><dt><code>win32</code><dd>Microsoft Win32 API thread support. 
-<br><dt><code>nks</code><dd>Novell Kernel Services thread support. 
-</dl>
-
-     <br><dt><code>--enable-tls</code><dd>Specify that the target supports TLS (Thread Local Storage).  Usually
-configure can correctly determine if TLS is supported.  In cases where
-it guesses incorrectly, TLS can be explicitly enabled or disabled with
-<samp><span class="option">--enable-tls</span></samp> or <samp><span class="option">--disable-tls</span></samp>.  This can happen if
-the assembler supports TLS but the C library does not, or if the
-assumptions made by the configure test are incorrect.
-
-     <br><dt><code>--disable-tls</code><dd>Specify that the target does not support TLS. 
-This is an alias for <samp><span class="option">--enable-tls=no</span></samp>.
-
-     <br><dt><code>--with-cpu=</code><var>cpu</var><dt><code>--with-cpu-32=</code><var>cpu</var><dt><code>--with-cpu-64=</code><var>cpu</var><dd>Specify which cpu variant the compiler should generate code for by default. 
-<var>cpu</var> will be used as the default value of the <samp><span class="option">-mcpu=</span></samp> switch. 
-This option is only supported on some targets, including ARM, i386, M68k,
-PowerPC, and SPARC.  The <samp><span class="option">--with-cpu-32</span></samp> and
-<samp><span class="option">--with-cpu-64</span></samp> options specify separate default CPUs for
-32-bit and 64-bit modes; these options are only supported for i386 and
-x86-64.
-
-     <br><dt><code>--with-schedule=</code><var>cpu</var><dt><code>--with-arch=</code><var>cpu</var><dt><code>--with-arch-32=</code><var>cpu</var><dt><code>--with-arch-64=</code><var>cpu</var><dt><code>--with-tune=</code><var>cpu</var><dt><code>--with-tune-32=</code><var>cpu</var><dt><code>--with-tune-64=</code><var>cpu</var><dt><code>--with-abi=</code><var>abi</var><dt><code>--with-fpu=</code><var>type</var><dt><code>--with-float=</code><var>type</var><dd>These configure options provide default values for the <samp><span class="option">-mschedule=</span></samp>,
-<samp><span class="option">-march=</span></samp>, <samp><span class="option">-mtune=</span></samp>, <samp><span class="option">-mabi=</span></samp>, and <samp><span class="option">-mfpu=</span></samp>
-options and for <samp><span class="option">-mhard-float</span></samp> or <samp><span class="option">-msoft-float</span></samp>.  As with
-<samp><span class="option">--with-cpu</span></samp>, which switches will be accepted and acceptable values
-of the arguments depend on the target.
-
-     <br><dt><code>--with-mode=</code><var>mode</var><dd>Specify if the compiler should default to <samp><span class="option">-marm</span></samp> or <samp><span class="option">-mthumb</span></samp>. 
-This option is only supported on ARM targets.
-
-     <br><dt><code>--with-divide=</code><var>type</var><dd>Specify how the compiler should generate code for checking for
-division by zero.  This option is only supported on the MIPS target. 
-The possibilities for <var>type</var> are:
-          <dl>
-<dt><code>traps</code><dd>Division by zero checks use conditional traps (this is the default on
-systems that support conditional traps). 
-<br><dt><code>breaks</code><dd>Division by zero checks use the break instruction. 
-</dl>
-
-     <!-- If you make -with-llsc the default for additional targets, -->
-     <!-- update the -with-llsc description in the MIPS section below. -->
-     <br><dt><code>--with-llsc</code><dd>On MIPS targets, make <samp><span class="option">-mllsc</span></samp> the default when no
-<samp><span class="option">-mno-lsc</span></samp> option is passed.  This is the default for
-Linux-based targets, as the kernel will emulate them if the ISA does
-not provide them.
-
-     <br><dt><code>--without-llsc</code><dd>On MIPS targets, make <samp><span class="option">-mno-llsc</span></samp> the default when no
-<samp><span class="option">-mllsc</span></samp> option is passed.
-
-     <br><dt><code>--with-mips-plt</code><dd>On MIPS targets, make use of copy relocations and PLTs. 
-These features are extensions to the traditional
-SVR4-based MIPS ABIs and require support from GNU binutils
-and the runtime C library.
-
-     <br><dt><code>--enable-__cxa_atexit</code><dd>Define if you want to use __cxa_atexit, rather than atexit, to
-register C++ destructors for local statics and global objects. 
-This is essential for fully standards-compliant handling of
-destructors, but requires __cxa_atexit in libc.  This option is currently
-only available on systems with GNU libc.  When enabled, this will cause
-<samp><span class="option">-fuse-cxa-atexit</span></samp> to be passed by default.
-
-     <br><dt><code>--enable-target-optspace</code><dd>Specify that target
-libraries should be optimized for code space instead of code speed. 
-This is the default for the m32r platform.
-
-     <br><dt><code>--disable-cpp</code><dd>Specify that a user visible <samp><span class="command">cpp</span></samp> program should not be installed.
-
-     <br><dt><code>--with-cpp-install-dir=</code><var>dirname</var><dd>Specify that the user visible <samp><span class="command">cpp</span></samp> program should be installed
-in <samp><var>prefix</var><span class="file">/</span><var>dirname</var><span class="file">/cpp</span></samp>, in addition to <var>bindir</var>.
-
-     <br><dt><code>--enable-initfini-array</code><dd>Force the use of sections <code>.init_array</code> and <code>.fini_array</code>
-(instead of <code>.init</code> and <code>.fini</code>) for constructors and
-destructors.  Option <samp><span class="option">--disable-initfini-array</span></samp> has the
-opposite effect.  If neither option is specified, the configure script
-will try to guess whether the <code>.init_array</code> and
-<code>.fini_array</code> sections are supported and, if they are, use them.
-
-     <br><dt><code>--enable-maintainer-mode</code><dd>The build rules that
-regenerate the GCC master message catalog <samp><span class="file">gcc.pot</span></samp> are normally
-disabled.  This is because it can only be rebuilt if the complete source
-tree is present.  If you have changed the sources and want to rebuild the
-catalog, configuring with <samp><span class="option">--enable-maintainer-mode</span></samp> will enable
-this.  Note that you need a recent version of the <code>gettext</code> tools
-to do so.
-
-     <br><dt><code>--disable-bootstrap</code><dd>For a native build, the default configuration is to perform
-a 3-stage bootstrap of the compiler when &lsquo;<samp><span class="samp">make</span></samp>&rsquo; is invoked,
-testing that GCC can compile itself correctly.  If you want to disable
-this process, you can configure with <samp><span class="option">--disable-bootstrap</span></samp>.
-
-     <br><dt><code>--enable-bootstrap</code><dd>In special cases, you may want to perform a 3-stage build
-even if the target and host triplets are different. 
-This could happen when the host can run code compiled for
-the target (e.g. host is i686-linux, target is i486-linux). 
-Starting from GCC 4.2, to do this you have to configure explicitly
-with <samp><span class="option">--enable-bootstrap</span></samp>.
-
-     <br><dt><code>--enable-generated-files-in-srcdir</code><dd>Neither the .c and .h files that are generated from Bison and flex nor the
-info manuals and man pages that are built from the .texi files are present
-in the SVN development tree.  When building GCC from that development tree,
-or from one of our snapshots, those generated files are placed in your
-build directory, which allows for the source to be in a readonly
-directory.
-
-     <p>If you configure with <samp><span class="option">--enable-generated-files-in-srcdir</span></samp> then those
-generated files will go into the source directory.  This is mainly intended
-for generating release or prerelease tarballs of the GCC sources, since it
-is not a requirement that the users of source releases to have flex, Bison,
-or makeinfo.
-
-     <br><dt><code>--enable-version-specific-runtime-libs</code><dd>Specify
-that runtime libraries should be installed in the compiler specific
-subdirectory (<samp><var>libdir</var><span class="file">/gcc</span></samp>) rather than the usual places.  In
-addition, &lsquo;<samp><span class="samp">libstdc++</span></samp>&rsquo;'s include files will be installed into
-<samp><var>libdir</var></samp> unless you overruled it by using
-<samp><span class="option">--with-gxx-include-dir=</span><var>dirname</var></samp>.  Using this option is
-particularly useful if you intend to use several versions of GCC in
-parallel.  This is currently supported by &lsquo;<samp><span class="samp">libgfortran</span></samp>&rsquo;,
-&lsquo;<samp><span class="samp">libjava</span></samp>&rsquo;, &lsquo;<samp><span class="samp">libmudflap</span></samp>&rsquo;, &lsquo;<samp><span class="samp">libstdc++</span></samp>&rsquo;, and &lsquo;<samp><span class="samp">libobjc</span></samp>&rsquo;.
-
-     <br><dt><code>--enable-languages=</code><var>lang1</var><code>,</code><var>lang2</var><code>,...</code><dd>Specify that only a particular subset of compilers and
-their runtime libraries should be built.  For a list of valid values for
-<var>langN</var> you can issue the following command in the
-<samp><span class="file">gcc</span></samp> directory of your GCC source tree:<br>
-     <pre class="smallexample">          grep language= */config-lang.in
-</pre>
-     <p>Currently, you can use any of the following:
-<code>all</code>, <code>ada</code>, <code>c</code>, <code>c++</code>, <code>fortran</code>, <code>java</code>,
-<code>objc</code>, <code>obj-c++</code>. 
-Building the Ada compiler has special requirements, see below. 
-If you do not pass this flag, or specify the option <code>all</code>, then all
-default languages available in the <samp><span class="file">gcc</span></samp> sub-tree will be configured. 
-Ada and Objective-C++ are not default languages; the rest are. 
-Re-defining <code>LANGUAGES</code> when calling &lsquo;<samp><span class="samp">make</span></samp>&rsquo; <strong>does not</strong>
-work anymore, as those language sub-directories might not have been
-configured!
-
-     <br><dt><code>--enable-stage1-languages=</code><var>lang1</var><code>,</code><var>lang2</var><code>,...</code><dd>Specify that a particular subset of compilers and their runtime
-libraries should be built with the system C compiler during stage 1 of
-the bootstrap process, rather than only in later stages with the
-bootstrapped C compiler.  The list of valid values is the same as for
-<samp><span class="option">--enable-languages</span></samp>, and the option <code>all</code> will select all
-of the languages enabled by <samp><span class="option">--enable-languages</span></samp>.  This option is
-primarily useful for GCC development; for instance, when a development
-version of the compiler cannot bootstrap due to compiler bugs, or when
-one is debugging front ends other than the C front end.  When this
-option is used, one can then build the target libraries for the
-specified languages with the stage-1 compiler by using <samp><span class="command">make
-stage1-bubble all-target</span></samp>, or run the testsuite on the stage-1 compiler
-for the specified languages using <samp><span class="command">make stage1-start check-gcc</span></samp>.
-
-     <br><dt><code>--disable-libada</code><dd>Specify that the run-time libraries and tools used by GNAT should not
-be built.  This can be useful for debugging, or for compatibility with
-previous Ada build procedures, when it was required to explicitly
-do a &lsquo;<samp><span class="samp">make -C gcc gnatlib_and_tools</span></samp>&rsquo;.
-
-     <br><dt><code>--disable-libssp</code><dd>Specify that the run-time libraries for stack smashing protection
-should not be built.
-
-     <br><dt><code>--disable-libgomp</code><dd>Specify that the run-time libraries used by GOMP should not be built.
-
-     <br><dt><code>--with-dwarf2</code><dd>Specify that the compiler should
-use DWARF 2 debugging information as the default.
-
-     <br><dt><code>--enable-targets=all</code><dt><code>--enable-targets=</code><var>target_list</var><dd>Some GCC targets, e.g. powerpc64-linux, build bi-arch compilers. 
-These are compilers that are able to generate either 64-bit or 32-bit
-code.  Typically, the corresponding 32-bit target, e.g. 
-powerpc-linux for powerpc64-linux, only generates 32-bit code.  This
-option enables the 32-bit target to be a bi-arch compiler, which is
-useful when you want a bi-arch compiler that defaults to 32-bit, and
-you are building a bi-arch or multi-arch binutils in a combined tree. 
-Currently, this option only affects sparc-linux, powerpc-linux and
-x86-linux.
-
-     <br><dt><code>--enable-secureplt</code><dd>This option enables <samp><span class="option">-msecure-plt</span></samp> by default for powerpc-linux. 
-See &ldquo;RS/6000 and PowerPC Options&rdquo; in the main manual
-
-     <br><dt><code>--enable-cld</code><dd>This option enables <samp><span class="option">-mcld</span></samp> by default for 32-bit x86 targets. 
-See &ldquo;i386 and x86-64 Options&rdquo; in the main manual
-
-     <br><dt><code>--enable-win32-registry</code><dt><code>--enable-win32-registry=</code><var>key</var><dt><code>--disable-win32-registry</code><dd>The <samp><span class="option">--enable-win32-registry</span></samp> option enables Microsoft Windows-hosted GCC
-to look up installations paths in the registry using the following key:
-
-     <pre class="smallexample">          <code>HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\</code><var>key</var>
-</pre>
-     <p><var>key</var> defaults to GCC version number, and can be overridden by the
-<samp><span class="option">--enable-win32-registry=</span><var>key</var></samp> option.  Vendors and distributors
-who use custom installers are encouraged to provide a different key,
-perhaps one comprised of vendor name and GCC version number, to
-avoid conflict with existing installations.  This feature is enabled
-by default, and can be disabled by <samp><span class="option">--disable-win32-registry</span></samp>
-option.  This option has no effect on the other hosts.
-
-     <br><dt><code>--nfp</code><dd>Specify that the machine does not have a floating point unit.  This
-option only applies to &lsquo;<samp><span class="samp">m68k-sun-sunos</span><var>n</var></samp>&rsquo;.  On any other
-system, <samp><span class="option">--nfp</span></samp> has no effect.
-
-     <br><dt><code>--enable-werror</code><dt><code>--disable-werror</code><dt><code>--enable-werror=yes</code><dt><code>--enable-werror=no</code><dd>When you specify this option, it controls whether certain files in the
-compiler are built with <samp><span class="option">-Werror</span></samp> in bootstrap stage2 and later. 
-If you don't specify it, <samp><span class="option">-Werror</span></samp> is turned on for the main
-development trunk.  However it defaults to off for release branches and
-final releases.  The specific files which get <samp><span class="option">-Werror</span></samp> are
-controlled by the Makefiles.
-
-     <br><dt><code>--enable-checking</code><dt><code>--enable-checking=</code><var>list</var><dd>When you specify this option, the compiler is built to perform internal
-consistency checks of the requested complexity.  This does not change the
-generated code, but adds error checking within the compiler.  This will
-slow down the compiler and may only work properly if you are building
-the compiler with GCC.  This is &lsquo;<samp><span class="samp">yes</span></samp>&rsquo; by default when building
-from SVN or snapshots, but &lsquo;<samp><span class="samp">release</span></samp>&rsquo; for releases.  The default
-for building the stage1 compiler is &lsquo;<samp><span class="samp">yes</span></samp>&rsquo;.  More control
-over the checks may be had by specifying <var>list</var>.  The categories of
-checks available are &lsquo;<samp><span class="samp">yes</span></samp>&rsquo; (most common checks
-&lsquo;<samp><span class="samp">assert,misc,tree,gc,rtlflag,runtime</span></samp>&rsquo;), &lsquo;<samp><span class="samp">no</span></samp>&rsquo; (no checks at
-all), &lsquo;<samp><span class="samp">all</span></samp>&rsquo; (all but &lsquo;<samp><span class="samp">valgrind</span></samp>&rsquo;), &lsquo;<samp><span class="samp">release</span></samp>&rsquo; (cheapest
-checks &lsquo;<samp><span class="samp">assert,runtime</span></samp>&rsquo;) or &lsquo;<samp><span class="samp">none</span></samp>&rsquo; (same as &lsquo;<samp><span class="samp">no</span></samp>&rsquo;). 
-Individual checks can be enabled with these flags &lsquo;<samp><span class="samp">assert</span></samp>&rsquo;,
-&lsquo;<samp><span class="samp">df</span></samp>&rsquo;, &lsquo;<samp><span class="samp">fold</span></samp>&rsquo;, &lsquo;<samp><span class="samp">gc</span></samp>&rsquo;, &lsquo;<samp><span class="samp">gcac</span></samp>&rsquo; &lsquo;<samp><span class="samp">misc</span></samp>&rsquo;, &lsquo;<samp><span class="samp">rtl</span></samp>&rsquo;,
-&lsquo;<samp><span class="samp">rtlflag</span></samp>&rsquo;, &lsquo;<samp><span class="samp">runtime</span></samp>&rsquo;, &lsquo;<samp><span class="samp">tree</span></samp>&rsquo;, and &lsquo;<samp><span class="samp">valgrind</span></samp>&rsquo;.
-
-     <p>The &lsquo;<samp><span class="samp">valgrind</span></samp>&rsquo; check requires the external <samp><span class="command">valgrind</span></samp>
-simulator, available from <a href="http://valgrind.org/">http://valgrind.org/</a>.  The
-&lsquo;<samp><span class="samp">df</span></samp>&rsquo;, &lsquo;<samp><span class="samp">rtl</span></samp>&rsquo;, &lsquo;<samp><span class="samp">gcac</span></samp>&rsquo; and &lsquo;<samp><span class="samp">valgrind</span></samp>&rsquo; checks are very expensive. 
-To disable all checking, &lsquo;<samp><span class="samp">--disable-checking</span></samp>&rsquo; or
-&lsquo;<samp><span class="samp">--enable-checking=none</span></samp>&rsquo; must be explicitly requested.  Disabling
-assertions will make the compiler and runtime slightly faster but
-increase the risk of undetected internal errors causing wrong code to be
-generated.
-
-     <br><dt><code>--disable-stage1-checking</code><br><dt><code>--enable-stage1-checking</code><dt><code>--enable-stage1-checking=</code><var>list</var><dd>If no <samp><span class="option">--enable-checking</span></samp> option is specified the stage1
-compiler will be built with &lsquo;<samp><span class="samp">yes</span></samp>&rsquo; checking enabled, otherwise
-the stage1 checking flags are the same as specified by
-<samp><span class="option">--enable-checking</span></samp>.  To build the stage1 compiler with
-different checking options use <samp><span class="option">--enable-stage1-checking</span></samp>. 
-The list of checking options is the same as for <samp><span class="option">--enable-checking</span></samp>. 
-If your system is too slow or too small to bootstrap a released compiler
-with checking for stage1 enabled, you can use &lsquo;<samp><span class="samp">--disable-stage1-checking</span></samp>&rsquo;
-to disable checking for the stage1 compiler.
-
-     <br><dt><code>--enable-coverage</code><dt><code>--enable-coverage=</code><var>level</var><dd>With this option, the compiler is built to collect self coverage
-information, every time it is run.  This is for internal development
-purposes, and only works when the compiler is being built with gcc.  The
-<var>level</var> argument controls whether the compiler is built optimized or
-not, values are &lsquo;<samp><span class="samp">opt</span></samp>&rsquo; and &lsquo;<samp><span class="samp">noopt</span></samp>&rsquo;.  For coverage analysis you
-want to disable optimization, for performance analysis you want to
-enable optimization.  When coverage is enabled, the default level is
-without optimization.
-
-     <br><dt><code>--enable-gather-detailed-mem-stats</code><dd>When this option is specified more detailed information on memory
-allocation is gathered.  This information is printed when using
-<samp><span class="option">-fmem-report</span></samp>.
-
-     <br><dt><code>--with-gc</code><dt><code>--with-gc=</code><var>choice</var><dd>With this option you can specify the garbage collector implementation
-used during the compilation process.  <var>choice</var> can be one of
-&lsquo;<samp><span class="samp">page</span></samp>&rsquo; and &lsquo;<samp><span class="samp">zone</span></samp>&rsquo;, where &lsquo;<samp><span class="samp">page</span></samp>&rsquo; is the default.
-
-     <br><dt><code>--enable-nls</code><dt><code>--disable-nls</code><dd>The <samp><span class="option">--enable-nls</span></samp> option enables Native Language Support (NLS),
-which lets GCC output diagnostics in languages other than American
-English.  Native Language Support is enabled by default if not doing a
-canadian cross build.  The <samp><span class="option">--disable-nls</span></samp> option disables NLS.
-
-     <br><dt><code>--with-included-gettext</code><dd>If NLS is enabled, the <samp><span class="option">--with-included-gettext</span></samp> option causes the build
-procedure to prefer its copy of GNU <samp><span class="command">gettext</span></samp>.
-
-     <br><dt><code>--with-catgets</code><dd>If NLS is enabled, and if the host lacks <code>gettext</code> but has the
-inferior <code>catgets</code> interface, the GCC build procedure normally
-ignores <code>catgets</code> and instead uses GCC's copy of the GNU
-<code>gettext</code> library.  The <samp><span class="option">--with-catgets</span></samp> option causes the
-build procedure to use the host's <code>catgets</code> in this situation.
-
-     <br><dt><code>--with-libiconv-prefix=</code><var>dir</var><dd>Search for libiconv header files in <samp><var>dir</var><span class="file">/include</span></samp> and
-libiconv library files in <samp><var>dir</var><span class="file">/lib</span></samp>.
-
-     <br><dt><code>--enable-obsolete</code><dd>Enable configuration for an obsoleted system.  If you attempt to
-configure GCC for a system (build, host, or target) which has been
-obsoleted, and you do not specify this flag, configure will halt with an
-error message.
-
-     <p>All support for systems which have been obsoleted in one release of GCC
-is removed entirely in the next major release, unless someone steps
-forward to maintain the port.
-
-     <br><dt><code>--enable-decimal-float</code><dt><code>--enable-decimal-float=yes</code><dt><code>--enable-decimal-float=no</code><dt><code>--enable-decimal-float=bid</code><dt><code>--enable-decimal-float=dpd</code><dt><code>--disable-decimal-float</code><dd>Enable (or disable) support for the C decimal floating point extension
-that is in the IEEE 754-2008 standard.  This is enabled by default only
-on PowerPC, i386, and x86_64 GNU/Linux systems.  Other systems may also
-support it, but require the user to specifically enable it.  You can
-optionally control which decimal floating point format is used (either
-&lsquo;<samp><span class="samp">bid</span></samp>&rsquo; or &lsquo;<samp><span class="samp">dpd</span></samp>&rsquo;).  The &lsquo;<samp><span class="samp">bid</span></samp>&rsquo; (binary integer decimal)
-format is default on i386 and x86_64 systems, and the &lsquo;<samp><span class="samp">dpd</span></samp>&rsquo;
-(densely packed decimal) format is default on PowerPC systems.
-
-     <br><dt><code>--enable-fixed-point</code><dt><code>--disable-fixed-point</code><dd>Enable (or disable) support for C fixed-point arithmetic. 
-This option is enabled by default for some targets (such as MIPS) which
-have hardware-support for fixed-point operations.  On other targets, you
-may enable this option manually.
-
-     <br><dt><code>--with-long-double-128</code><dd>Specify if <code>long double</code> type should be 128-bit by default on selected
-GNU/Linux architectures.  If using <code>--without-long-double-128</code>,
-<code>long double</code> will be by default 64-bit, the same as <code>double</code> type. 
-When neither of these configure options are used, the default will be
-128-bit <code>long double</code> when built against GNU C Library 2.4 and later,
-64-bit <code>long double</code> otherwise.
-
-     <br><dt><code>--with-gmp=</code><var>pathname</var><dt><code>--with-gmp-include=</code><var>pathname</var><dt><code>--with-gmp-lib=</code><var>pathname</var><dt><code>--with-mpfr=</code><var>pathname</var><dt><code>--with-mpfr-include=</code><var>pathname</var><dt><code>--with-mpfr-lib=</code><var>pathname</var><dd>If you do not have GMP (the GNU Multiple Precision library) and the
-MPFR Libraries installed in a standard location and you want to build
-GCC, you can explicitly specify the directory where they are installed
-(&lsquo;<samp><span class="samp">--with-gmp=</span><var>gmpinstalldir</var></samp>&rsquo;,
-&lsquo;<samp><span class="samp">--with-mpfr=</span><var>mpfrinstalldir</var></samp>&rsquo;).  The
-<samp><span class="option">--with-gmp=</span><var>gmpinstalldir</var></samp> option is shorthand for
-<samp><span class="option">--with-gmp-lib=</span><var>gmpinstalldir</var><span class="option">/lib</span></samp> and
-<samp><span class="option">--with-gmp-include=</span><var>gmpinstalldir</var><span class="option">/include</span></samp>.  Likewise the
-<samp><span class="option">--with-mpfr=</span><var>mpfrinstalldir</var></samp> option is shorthand for
-<samp><span class="option">--with-mpfr-lib=</span><var>mpfrinstalldir</var><span class="option">/lib</span></samp> and
-<samp><span class="option">--with-mpfr-include=</span><var>mpfrinstalldir</var><span class="option">/include</span></samp>.  If these
-shorthand assumptions are not correct, you can use the explicit
-include and lib options directly.
-
-     <br><dt><code>--with-ppl=</code><var>pathname</var><dt><code>--with-ppl-include=</code><var>pathname</var><dt><code>--with-ppl-lib=</code><var>pathname</var><dt><code>--with-cloog=</code><var>pathname</var><dt><code>--with-cloog-include=</code><var>pathname</var><dt><code>--with-cloog-lib=</code><var>pathname</var><dd>If you do not have PPL (the Parma Polyhedra Library) and the CLooG
-libraries installed in a standard location and you want to build GCC,
-you can explicitly specify the directory where they are installed
-(&lsquo;<samp><span class="samp">--with-ppl=</span><var>pplinstalldir</var></samp>&rsquo;,
-&lsquo;<samp><span class="samp">--with-cloog=</span><var>clooginstalldir</var></samp>&rsquo;). The
-<samp><span class="option">--with-ppl=</span><var>pplinstalldir</var></samp> option is shorthand for
-<samp><span class="option">--with-ppl-lib=</span><var>pplinstalldir</var><span class="option">/lib</span></samp> and
-<samp><span class="option">--with-ppl-include=</span><var>pplinstalldir</var><span class="option">/include</span></samp>.  Likewise the
-<samp><span class="option">--with-cloog=</span><var>clooginstalldir</var></samp> option is shorthand for
-<samp><span class="option">--with-cloog-lib=</span><var>clooginstalldir</var><span class="option">/lib</span></samp> and
-<samp><span class="option">--with-cloog-include=</span><var>clooginstalldir</var><span class="option">/include</span></samp>.  If these
-shorthand assumptions are not correct, you can use the explicit
-include and lib options directly.
-
-     <br><dt><code>--with-host-libstdcxx=</code><var>linker-args</var><dd>If you are linking with a static copy of PPL, you can use this option
-to specify how the linker should find the standard C++ library used
-internally by PPL.  Typical values of <var>linker-args</var> might be
-&lsquo;<samp><span class="samp">-lstdc++</span></samp>&rsquo; or &lsquo;<samp><span class="samp">-Wl,-Bstatic,-lstdc++,-Bdynamic -lm</span></samp>&rsquo;.  If you are
-linking with a shared copy of PPL, you probably do not need this
-option; shared library dependencies will cause the linker to search
-for the standard C++ library automatically.
-
-     <br><dt><code>--with-debug-prefix-map=</code><var>map</var><dd>Convert source directory names using <samp><span class="option">-fdebug-prefix-map</span></samp> when
-building runtime libraries.  &lsquo;<samp><var>map</var></samp>&rsquo; is a space-separated
-list of maps of the form &lsquo;<samp><var>old</var><span class="samp">=</span><var>new</var></samp>&rsquo;.
-
-   </dl>
-
-<h4 class="subheading"><a name="TOC3"></a>Cross-Compiler-Specific Options</h4>
-
-<p>The following options only apply to building cross compilers.
-     <dl>
-<dt><code>--with-sysroot</code><dt><code>--with-sysroot=</code><var>dir</var><dd>Tells GCC to consider <var>dir</var> as the root of a tree that contains a
-(subset of) the root filesystem of the target operating system. 
-Target system headers, libraries and run-time object files will be
-searched in there.  The specified directory is not copied into the
-install tree, unlike the options <samp><span class="option">--with-headers</span></samp> and
-<samp><span class="option">--with-libs</span></samp> that this option obsoletes.  The default value,
-in case <samp><span class="option">--with-sysroot</span></samp> is not given an argument, is
-<samp><span class="option">${gcc_tooldir}/sys-root</span></samp>.  If the specified directory is a
-subdirectory of <samp><span class="option">${exec_prefix}</span></samp>, then it will be found relative to
-the GCC binaries if the installation tree is moved.
-
-     <br><dt><code>--with-build-sysroot</code><dt><code>--with-build-sysroot=</code><var>dir</var><dd>Tells GCC to consider <var>dir</var> as the system root (see
-<samp><span class="option">--with-sysroot</span></samp>) while building target libraries, instead of
-the directory specified with <samp><span class="option">--with-sysroot</span></samp>.  This option is
-only useful when you are already using <samp><span class="option">--with-sysroot</span></samp>.  You
-can use <samp><span class="option">--with-build-sysroot</span></samp> when you are configuring with
-<samp><span class="option">--prefix</span></samp> set to a directory that is different from the one in
-which you are installing GCC and your target libraries.
-
-     <p>This option affects the system root for the compiler used to build
-target libraries (which runs on the build system); it does not affect
-the compiler which is used to build GCC itself.
-
-     <br><dt><code>--with-headers</code><dt><code>--with-headers=</code><var>dir</var><dd>Deprecated in favor of <samp><span class="option">--with-sysroot</span></samp>. 
-Specifies that target headers are available when building a cross compiler. 
-The <var>dir</var> argument specifies a directory which has the target include
-files.  These include files will be copied into the <samp><span class="file">gcc</span></samp> install
-directory.  <em>This option with the </em><var>dir</var><em> argument is required</em> when
-building a cross compiler, if <samp><var>prefix</var><span class="file">/</span><var>target</var><span class="file">/sys-include</span></samp>
-doesn't pre-exist.  If <samp><var>prefix</var><span class="file">/</span><var>target</var><span class="file">/sys-include</span></samp> does
-pre-exist, the <var>dir</var> argument may be omitted.  <samp><span class="command">fixincludes</span></samp>
-will be run on these files to make them compatible with GCC.
-
-     <br><dt><code>--without-headers</code><dd>Tells GCC not use any target headers from a libc when building a cross
-compiler.  When crossing to GNU/Linux, you need the headers so GCC
-can build the exception handling for libgcc.
-
-     <br><dt><code>--with-libs</code><dt><code>--with-libs=``</code><var>dir1</var> <var>dir2</var><code> ... </code><var>dirN</var><code>''</code><dd>Deprecated in favor of <samp><span class="option">--with-sysroot</span></samp>. 
-Specifies a list of directories which contain the target runtime
-libraries.  These libraries will be copied into the <samp><span class="file">gcc</span></samp> install
-directory.  If the directory list is omitted, this option has no
-effect.
-
-     <br><dt><code>--with-newlib</code><dd>Specifies that &lsquo;<samp><span class="samp">newlib</span></samp>&rsquo; is
-being used as the target C library.  This causes <code>__eprintf</code> to be
-omitted from <samp><span class="file">libgcc.a</span></samp> on the assumption that it will be provided by
-&lsquo;<samp><span class="samp">newlib</span></samp>&rsquo;.
-
-     <br><dt><code>--with-build-time-tools=</code><var>dir</var><dd>Specifies where to find the set of target tools (assembler, linker, etc.) 
-that will be used while building GCC itself.  This option can be useful
-if the directory layouts are different between the system you are building
-GCC on, and the system where you will deploy it.
-
-     <p>For example, on a <samp><span class="option">ia64-hp-hpux</span></samp> system, you may have the GNU
-assembler and linker in <samp><span class="file">/usr/bin</span></samp>, and the native tools in a
-different path, and build a toolchain that expects to find the
-native tools in <samp><span class="file">/usr/bin</span></samp>.
-
-     <p>When you use this option, you should ensure that <var>dir</var> includes
-<samp><span class="command">ar</span></samp>, <samp><span class="command">as</span></samp>, <samp><span class="command">ld</span></samp>, <samp><span class="command">nm</span></samp>,
-<samp><span class="command">ranlib</span></samp> and <samp><span class="command">strip</span></samp> if necessary, and possibly
-<samp><span class="command">objdump</span></samp>.  Otherwise, GCC may use an inconsistent set of
-tools. 
-</dl>
-
-<h4 class="subheading"><a name="TOC4"></a>Java-Specific Options</h4>
-
-<p>The following option applies to the build of the Java front end.
-
-     <dl>
-<dt><code>--disable-libgcj</code><dd>Specify that the run-time libraries
-used by GCJ should not be built.  This is useful in case you intend
-to use GCJ with some other run-time, or you're going to install it
-separately, or it just happens not to build on your particular
-machine.  In general, if the Java front end is enabled, the GCJ
-libraries will be enabled too, unless they're known to not work on
-the target platform.  If GCJ is enabled but &lsquo;<samp><span class="samp">libgcj</span></samp>&rsquo; isn't built, you
-may need to port it; in this case, before modifying the top-level
-<samp><span class="file">configure.in</span></samp> so that &lsquo;<samp><span class="samp">libgcj</span></samp>&rsquo; is enabled by default on this platform,
-you may use <samp><span class="option">--enable-libgcj</span></samp> to override the default.
-
-   </dl>
-
-   <p>The following options apply to building &lsquo;<samp><span class="samp">libgcj</span></samp>&rsquo;.
-
-<h5 class="subsubheading"><a name="TOC5"></a>General Options</h5>
-
-     <dl>
-<dt><code>--enable-java-maintainer-mode</code><dd>By default the &lsquo;<samp><span class="samp">libjava</span></samp>&rsquo; build will not attempt to compile the
-<samp><span class="file">.java</span></samp> source files to <samp><span class="file">.class</span></samp>.  Instead, it will use the
-<samp><span class="file">.class</span></samp> files from the source tree.  If you use this option you
-must have executables named <samp><span class="command">ecj1</span></samp> and <samp><span class="command">gjavah</span></samp> in your path
-for use by the build.  You must use this option if you intend to
-modify any <samp><span class="file">.java</span></samp> files in <samp><span class="file">libjava</span></samp>.
-
-     <br><dt><code>--with-java-home=</code><var>dirname</var><dd>This &lsquo;<samp><span class="samp">libjava</span></samp>&rsquo; option overrides the default value of the
-&lsquo;<samp><span class="samp">java.home</span></samp>&rsquo; system property.  It is also used to set
-&lsquo;<samp><span class="samp">sun.boot.class.path</span></samp>&rsquo; to <samp><var>dirname</var><span class="file">/lib/rt.jar</span></samp>.  By
-default &lsquo;<samp><span class="samp">java.home</span></samp>&rsquo; is set to <samp><var>prefix</var></samp> and
-&lsquo;<samp><span class="samp">sun.boot.class.path</span></samp>&rsquo; to
-<samp><var>datadir</var><span class="file">/java/libgcj-</span><var>version</var><span class="file">.jar</span></samp>.
-
-     <br><dt><code>--with-ecj-jar=</code><var>filename</var><dd>This option can be used to specify the location of an external jar
-file containing the Eclipse Java compiler.  A specially modified
-version of this compiler is used by <samp><span class="command">gcj</span></samp> to parse
-<samp><span class="file">.java</span></samp> source files.  If this option is given, the
-&lsquo;<samp><span class="samp">libjava</span></samp>&rsquo; build will create and install an <samp><span class="file">ecj1</span></samp> executable
-which uses this jar file at runtime.
-
-     <p>If this option is not given, but an <samp><span class="file">ecj.jar</span></samp> file is found in
-the topmost source tree at configure time, then the &lsquo;<samp><span class="samp">libgcj</span></samp>&rsquo;
-build will create and install <samp><span class="file">ecj1</span></samp>, and will also install the
-discovered <samp><span class="file">ecj.jar</span></samp> into a suitable place in the install tree.
-
-     <p>If <samp><span class="file">ecj1</span></samp> is not installed, then the user will have to supply one
-on his path in order for <samp><span class="command">gcj</span></samp> to properly parse <samp><span class="file">.java</span></samp>
-source files.  A suitable jar is available from
-<a href="ftp://sourceware.org/pub/java/">ftp://sourceware.org/pub/java/</a>.
-
-     <br><dt><code>--disable-getenv-properties</code><dd>Don't set system properties from <samp><span class="env">GCJ_PROPERTIES</span></samp>.
-
-     <br><dt><code>--enable-hash-synchronization</code><dd>Use a global hash table for monitor locks.  Ordinarily,
-&lsquo;<samp><span class="samp">libgcj</span></samp>&rsquo;'s &lsquo;<samp><span class="samp">configure</span></samp>&rsquo; script automatically makes
-the correct choice for this option for your platform.  Only use
-this if you know you need the library to be configured differently.
-
-     <br><dt><code>--enable-interpreter</code><dd>Enable the Java interpreter.  The interpreter is automatically
-enabled by default on all platforms that support it.  This option
-is really only useful if you want to disable the interpreter
-(using <samp><span class="option">--disable-interpreter</span></samp>).
-
-     <br><dt><code>--disable-java-net</code><dd>Disable java.net.  This disables the native part of java.net only,
-using non-functional stubs for native method implementations.
-
-     <br><dt><code>--disable-jvmpi</code><dd>Disable JVMPI support.
-
-     <br><dt><code>--disable-libgcj-bc</code><dd>Disable BC ABI compilation of certain parts of libgcj.  By default,
-some portions of libgcj are compiled with <samp><span class="option">-findirect-dispatch</span></samp>
-and <samp><span class="option">-fno-indirect-classes</span></samp>, allowing them to be overridden at
-run-time.
-
-     <p>If <samp><span class="option">--disable-libgcj-bc</span></samp> is specified, libgcj is built without
-these options.  This allows the compile-time linker to resolve
-dependencies when statically linking to libgcj.  However it makes it
-impossible to override the affected portions of libgcj at run-time.
-
-     <br><dt><code>--enable-reduced-reflection</code><dd>Build most of libgcj with <samp><span class="option">-freduced-reflection</span></samp>.  This reduces
-the size of libgcj at the expense of not being able to do accurate
-reflection on the classes it contains.  This option is safe if you
-know that code using libgcj will never use reflection on the standard
-runtime classes in libgcj (including using serialization, RMI or CORBA).
-
-     <br><dt><code>--with-ecos</code><dd>Enable runtime eCos target support.
-
-     <br><dt><code>--without-libffi</code><dd>Don't use &lsquo;<samp><span class="samp">libffi</span></samp>&rsquo;.  This will disable the interpreter and JNI
-support as well, as these require &lsquo;<samp><span class="samp">libffi</span></samp>&rsquo; to work.
-
-     <br><dt><code>--enable-libgcj-debug</code><dd>Enable runtime debugging code.
-
-     <br><dt><code>--enable-libgcj-multifile</code><dd>If specified, causes all <samp><span class="file">.java</span></samp> source files to be
-compiled into <samp><span class="file">.class</span></samp> files in one invocation of
-&lsquo;<samp><span class="samp">gcj</span></samp>&rsquo;.  This can speed up build time, but is more
-resource-intensive.  If this option is unspecified or
-disabled, &lsquo;<samp><span class="samp">gcj</span></samp>&rsquo; is invoked once for each <samp><span class="file">.java</span></samp>
-file to compile into a <samp><span class="file">.class</span></samp> file.
-
-     <br><dt><code>--with-libiconv-prefix=DIR</code><dd>Search for libiconv in <samp><span class="file">DIR/include</span></samp> and <samp><span class="file">DIR/lib</span></samp>.
-
-     <br><dt><code>--enable-sjlj-exceptions</code><dd>Force use of the <code>setjmp</code>/<code>longjmp</code>-based scheme for exceptions. 
-&lsquo;<samp><span class="samp">configure</span></samp>&rsquo; ordinarily picks the correct value based on the platform. 
-Only use this option if you are sure you need a different setting.
-
-     <br><dt><code>--with-system-zlib</code><dd>Use installed &lsquo;<samp><span class="samp">zlib</span></samp>&rsquo; rather than that included with GCC.
-
-     <br><dt><code>--with-win32-nlsapi=ansi, unicows or unicode</code><dd>Indicates how MinGW &lsquo;<samp><span class="samp">libgcj</span></samp>&rsquo; translates between UNICODE
-characters and the Win32 API.
-
-     <br><dt><code>--enable-java-home</code><dd>If enabled, this creates a JPackage compatible SDK environment during install. 
-Note that if &ndash;enable-java-home is used, &ndash;with-arch-directory=ARCH must also
-be specified.
-
-     <br><dt><code>--with-arch-directory=ARCH</code><dd>Specifies the name to use for the <samp><span class="file">jre/lib/ARCH</span></samp> directory in the SDK
-environment created when &ndash;enable-java-home is passed. Typical names for this
-directory include i386, amd64, ia64, etc.
-
-     <br><dt><code>--with-os-directory=DIR</code><dd>Specifies the OS directory for the SDK include directory. This is set to auto
-detect, and is typically 'linux'.
-
-     <br><dt><code>--with-origin-name=NAME</code><dd>Specifies the JPackage origin name. This defaults to the 'gcj' in
-java-1.5.0-gcj.
-
-     <br><dt><code>--with-arch-suffix=SUFFIX</code><dd>Specifies the suffix for the sdk directory. Defaults to the empty string. 
-Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'.
-
-     <br><dt><code>--with-jvm-root-dir=DIR</code><dd>Specifies where to install the SDK. Default is $(prefix)/lib/jvm.
-
-     <br><dt><code>--with-jvm-jar-dir=DIR</code><dd>Specifies where to install jars. Default is $(prefix)/lib/jvm-exports.
-
-     <br><dt><code>--with-python-dir=DIR</code><dd>Specifies where to install the Python modules used for aot-compile. DIR should
-not include the prefix used in installation. For example, if the Python modules
-are to be installed in /usr/lib/python2.5/site-packages, then
-&ndash;with-python-dir=/lib/python2.5/site-packages should be passed. If this is
-not specified, then the Python modules are installed in $(prefix)/share/python.
-
-     <br><dt><code>--enable-aot-compile-rpm</code><dd>Adds aot-compile-rpm to the list of installed scripts.
-
-          <dl>
-<dt><code>ansi</code><dd>Use the single-byte <code>char</code> and the Win32 A functions natively,
-translating to and from UNICODE when using these functions.  If
-unspecified, this is the default.
-
-          <br><dt><code>unicows</code><dd>Use the <code>WCHAR</code> and Win32 W functions natively.  Adds
-<code>-lunicows</code> to <samp><span class="file">libgcj.spec</span></samp> to link with &lsquo;<samp><span class="samp">libunicows</span></samp>&rsquo;. 
-<samp><span class="file">unicows.dll</span></samp> needs to be deployed on Microsoft Windows 9X machines
-running built executables.  <samp><span class="file">libunicows.a</span></samp>, an open-source
-import library around Microsoft's <code>unicows.dll</code>, is obtained from
-<a href="http://libunicows.sourceforge.net/">http://libunicows.sourceforge.net/</a>, which also gives details
-on getting <samp><span class="file">unicows.dll</span></samp> from Microsoft.
-
-          <br><dt><code>unicode</code><dd>Use the <code>WCHAR</code> and Win32 W functions natively.  Does <em>not</em>
-add <code>-lunicows</code> to <samp><span class="file">libgcj.spec</span></samp>.  The built executables will
-only run on Microsoft Windows NT and above. 
-</dl>
-     </dl>
-
-<h5 class="subsubheading"><a name="TOC6"></a>AWT-Specific Options</h5>
-
-     <dl>
-<dt><code>--with-x</code><dd>Use the X Window System.
-
-     <br><dt><code>--enable-java-awt=PEER(S)</code><dd>Specifies the AWT peer library or libraries to build alongside
-&lsquo;<samp><span class="samp">libgcj</span></samp>&rsquo;.  If this option is unspecified or disabled, AWT
-will be non-functional.  Current valid values are <samp><span class="option">gtk</span></samp> and
-<samp><span class="option">xlib</span></samp>.  Multiple libraries should be separated by a
-comma (i.e. <samp><span class="option">--enable-java-awt=gtk,xlib</span></samp>).
-
-     <br><dt><code>--enable-gtk-cairo</code><dd>Build the cairo Graphics2D implementation on GTK.
-
-     <br><dt><code>--enable-java-gc=TYPE</code><dd>Choose garbage collector.  Defaults to <samp><span class="option">boehm</span></samp> if unspecified.
-
-     <br><dt><code>--disable-gtktest</code><dd>Do not try to compile and run a test GTK+ program.
-
-     <br><dt><code>--disable-glibtest</code><dd>Do not try to compile and run a test GLIB program.
-
-     <br><dt><code>--with-libart-prefix=PFX</code><dd>Prefix where libart is installed (optional).
-
-     <br><dt><code>--with-libart-exec-prefix=PFX</code><dd>Exec prefix where libart is installed (optional).
-
-     <br><dt><code>--disable-libarttest</code><dd>Do not try to compile and run a test libart program.
-
-</dl>
-
-   <p><hr />
-<p><a href="./index.html">Return to the GCC Installation page</a>
-
-<!-- ***Building**************************************************************** -->
-<!-- ***Testing***************************************************************** -->
-<!-- ***Final install*********************************************************** -->
-<!-- ***Binaries**************************************************************** -->
-<!-- ***Specific**************************************************************** -->
-<!-- ***Old documentation****************************************************** -->
-<!-- ***GFDL******************************************************************** -->
-<!-- *************************************************************************** -->
-<!-- Part 6 The End of the Document -->
-</body></html>
-
--- a/INSTALL/download.html	Mon May 24 12:48:09 2010 +0900
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,97 +0,0 @@
-<html lang="en">
-<head>
-<title>Downloading GCC</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Downloading GCC">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
-<!--
-Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
-1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
-2008 Free Software Foundation, Inc.
-
-   Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, the Front-Cover texts being (a) (see below), and
-with the Back-Cover Texts being (b) (see below).  A copy of the
-license is included in the section entitled "GNU Free Documentation License".
-
-(a) The FSF's Front-Cover Text is:
-
-     A GNU Manual
-
-(b) The FSF's Back-Cover Text is:
-
-     You have freedom to copy and modify this GNU Manual, like GNU
-     software.  Copies published by the Free Software Foundation raise
-     funds for GNU development.-->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
-</head>
-<body>
-<h1 class="settitle">Downloading GCC</h1>
-<a name="index-Downloading-GCC-1"></a><a name="index-Downloading-the-Source-2"></a>
-GCC is distributed via <a href="http://gcc.gnu.org/svn.html">SVN</a> and FTP
-tarballs compressed with <samp><span class="command">gzip</span></samp> or
-<samp><span class="command">bzip2</span></samp>.  It is possible to download a full distribution or specific
-components.
-
-   <p>Please refer to the <a href="http://gcc.gnu.org/releases.html">releases web page</a>
-for information on how to obtain GCC.
-
-   <p>The full distribution includes the C, C++, Objective-C, Fortran, Java,
-and Ada (in the case of GCC 3.1 and later) compilers.  The full
-distribution also includes runtime libraries for C++, Objective-C,
-Fortran, and Java.  In GCC 3.0 and later versions, the GNU compiler
-testsuites are also included in the full distribution.
-
-   <p>If you choose to download specific components, you must download the core
-GCC distribution plus any language specific distributions you wish to
-use.  The core distribution includes the C language front end as well as the
-shared components.  Each language has a tarball which includes the language
-front end as well as the language runtime (when appropriate).
-
-   <p>Unpack the core distribution as well as any language specific
-distributions in the same directory.
-
-   <p>If you also intend to build binutils (either to upgrade an existing
-installation or for use in place of the corresponding tools of your
-OS), unpack the binutils distribution either in the same directory or
-a separate one.  In the latter case, add symbolic links to any
-components of the binutils you intend to build alongside the compiler
-(<samp><span class="file">bfd</span></samp>, <samp><span class="file">binutils</span></samp>, <samp><span class="file">gas</span></samp>, <samp><span class="file">gprof</span></samp>, <samp><span class="file">ld</span></samp>,
-<samp><span class="file">opcodes</span></samp>, <small class="dots">...</small>) to the directory containing the GCC sources.
-
-   <p>Likewise, the GMP and MPFR libraries can be automatically built together
-with GCC.  Unpack the GMP and/or MPFR source distributions in the
-directory containing the GCC sources and rename their directories to
-<samp><span class="file">gmp</span></samp> and <samp><span class="file">mpfr</span></samp>, respectively (or use symbolic links with the
-same name).
-
-   <p><hr />
-<p><a href="./index.html">Return to the GCC Installation page</a>
-
-<!-- ***Configuration*********************************************************** -->
-<!-- ***Building**************************************************************** -->
-<!-- ***Testing***************************************************************** -->
-<!-- ***Final install*********************************************************** -->
-<!-- ***Binaries**************************************************************** -->
-<!-- ***Specific**************************************************************** -->
-<!-- ***Old documentation****************************************************** -->
-<!-- ***GFDL******************************************************************** -->
-<!-- *************************************************************************** -->
-<!-- Part 6 The End of the Document -->
-</body></html>
-
--- a/INSTALL/finalinstall.html	Mon May 24 12:48:09 2010 +0900
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,170 +0,0 @@
-<html lang="en">
-<head>
-<title>Installing GCC: Final installation</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Installing GCC: Final installation">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
-<!--
-Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
-1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
-2008 Free Software Foundation, Inc.
-
-   Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, the Front-Cover texts being (a) (see below), and
-with the Back-Cover Texts being (b) (see below).  A copy of the
-license is included in the section entitled "GNU Free Documentation License".
-
-(a) The FSF's Front-Cover Text is:
-
-     A GNU Manual
-
-(b) The FSF's Back-Cover Text is:
-
-     You have freedom to copy and modify this GNU Manual, like GNU
-     software.  Copies published by the Free Software Foundation raise
-     funds for GNU development.-->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
-</head>
-<body>
-<h1 class="settitle">Installing GCC: Final installation</h1>
-Now that GCC has been built (and optionally tested), you can install it with
-<pre class="smallexample">     cd <var>objdir</var>; make install
-</pre>
-   <p>We strongly recommend to install into a target directory where there is
-no previous version of GCC present.  Also, the GNAT runtime should not
-be stripped, as this would break certain features of the debugger that
-depend on this debugging information (catching Ada exceptions for
-instance).
-
-   <p>That step completes the installation of GCC; user level binaries can
-be found in <samp><var>prefix</var><span class="file">/bin</span></samp> where <var>prefix</var> is the value
-you specified with the <samp><span class="option">--prefix</span></samp> to configure (or
-<samp><span class="file">/usr/local</span></samp> by default).  (If you specified <samp><span class="option">--bindir</span></samp>,
-that directory will be used instead; otherwise, if you specified
-<samp><span class="option">--exec-prefix</span></samp>, <samp><var>exec-prefix</var><span class="file">/bin</span></samp> will be used.) 
-Headers for the C++ and Java libraries are installed in
-<samp><var>prefix</var><span class="file">/include</span></samp>; libraries in <samp><var>libdir</var></samp>
-(normally <samp><var>prefix</var><span class="file">/lib</span></samp>); internal parts of the compiler in
-<samp><var>libdir</var><span class="file">/gcc</span></samp> and <samp><var>libexecdir</var><span class="file">/gcc</span></samp>; documentation
-in info format in <samp><var>infodir</var></samp> (normally
-<samp><var>prefix</var><span class="file">/info</span></samp>).
-
-   <p>When installing cross-compilers, GCC's executables
-are not only installed into <samp><var>bindir</var></samp>, that
-is, <samp><var>exec-prefix</var><span class="file">/bin</span></samp>, but additionally into
-<samp><var>exec-prefix</var><span class="file">/</span><var>target-alias</var><span class="file">/bin</span></samp>, if that directory
-exists.  Typically, such <dfn>tooldirs</dfn> hold target-specific
-binutils, including assembler and linker.
-
-   <p>Installation into a temporary staging area or into a <samp><span class="command">chroot</span></samp>
-jail can be achieved with the command
-
-<pre class="smallexample">     make DESTDIR=<var>path-to-rootdir</var> install
-</pre>
-   <p class="noindent">where <var>path-to-rootdir</var> is the absolute path of
-a directory relative to which all installation paths will be
-interpreted.  Note that the directory specified by <code>DESTDIR</code>
-need not exist yet; it will be created if necessary.
-
-   <p>There is a subtle point with tooldirs and <code>DESTDIR</code>:
-If you relocate a cross-compiler installation with
-e.g. &lsquo;<samp><span class="samp">DESTDIR=</span><var>rootdir</var></samp>&rsquo;, then the directory
-<samp><var>rootdir</var><span class="file">/</span><var>exec-prefix</var><span class="file">/</span><var>target-alias</var><span class="file">/bin</span></samp> will
-be filled with duplicated GCC executables only if it already exists,
-it will not be created otherwise.  This is regarded as a feature,
-not as a bug, because it gives slightly more control to the packagers
-using the <code>DESTDIR</code> feature.
-
-   <p>If you are bootstrapping a released version of GCC then please
-quickly review the build status page for your release, available from
-<a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>. 
-If your system is not listed for the version of GCC that you built,
-send a note to
-<a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a> indicating
-that you successfully built and installed GCC. 
-Include the following information:
-
-     <ul>
-<li>Output from running <samp><var>srcdir</var><span class="file">/config.guess</span></samp>.  Do not send
-that file itself, just the one-line output from running it.
-
-     <li>The output of &lsquo;<samp><span class="samp">gcc -v</span></samp>&rsquo; for your newly installed <samp><span class="command">gcc</span></samp>. 
-This tells us which version of GCC you built and the options you passed to
-configure.
-
-     <li>Whether you enabled all languages or a subset of them.  If you used a
-full distribution then this information is part of the configure
-options in the output of &lsquo;<samp><span class="samp">gcc -v</span></samp>&rsquo;, but if you downloaded the
-&ldquo;core&rdquo; compiler plus additional front ends then it isn't apparent
-which ones you built unless you tell us about it.
-
-     <li>If the build was for GNU/Linux, also include:
-          <ul>
-<li>The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
-this information should be available from <samp><span class="file">/etc/issue</span></samp>.
-
-          <li>The version of the Linux kernel, available from &lsquo;<samp><span class="samp">uname --version</span></samp>&rsquo;
-or &lsquo;<samp><span class="samp">uname -a</span></samp>&rsquo;.
-
-          <li>The version of glibc you used; for RPM-based systems like Red Hat,
-Mandrake, and SuSE type &lsquo;<samp><span class="samp">rpm -q glibc</span></samp>&rsquo; to get the glibc version,
-and on systems like Debian and Progeny use &lsquo;<samp><span class="samp">dpkg -l libc6</span></samp>&rsquo;. 
-</ul>
-     For other systems, you can include similar information if you think it is
-relevant.
-
-     <li>Any other information that you think would be useful to people building
-GCC on the same configuration.  The new entry in the build status list
-will include a link to the archived copy of your message. 
-</ul>
-
-   <p>We'd also like to know if the
-<a href="specific.html">host/target specific installation notes</a>
-didn't include your host/target information or if that information is
-incomplete or out of date.  Send a note to
-<a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a> detailing how the information should be changed.
-
-   <p>If you find a bug, please report it following the
-<a href="../bugs.html">bug reporting guidelines</a>.
-
-   <p>If you want to print the GCC manuals, do &lsquo;<samp><span class="samp">cd </span><var>objdir</var><span class="samp">; make
-dvi</span></samp>&rsquo;.  You will need to have <samp><span class="command">texi2dvi</span></samp> (version at least 4.7)
-and TeX installed.  This creates a number of <samp><span class="file">.dvi</span></samp> files in
-subdirectories of <samp><var>objdir</var></samp>; these may be converted for
-printing with programs such as <samp><span class="command">dvips</span></samp>.  Alternately, by using
-&lsquo;<samp><span class="samp">make pdf</span></samp>&rsquo; in place of &lsquo;<samp><span class="samp">make dvi</span></samp>&rsquo;, you can create documentation
-in the form of <samp><span class="file">.pdf</span></samp> files; this requires <samp><span class="command">texi2pdf</span></samp>, which
-is included with Texinfo version 4.8 and later.  You can also
-<a href="http://shop.fsf.org/">buy printed manuals from the Free Software Foundation</a>, though such manuals may not be for the most
-recent version of GCC.
-
-   <p>If you would like to generate online HTML documentation, do &lsquo;<samp><span class="samp">cd
-</span><var>objdir</var><span class="samp">; make html</span></samp>&rsquo; and HTML will be generated for the gcc manuals in
-<samp><var>objdir</var><span class="file">/gcc/HTML</span></samp>.
-
-   <p><hr />
-<p><a href="./index.html">Return to the GCC Installation page</a>
-
-<!-- ***Binaries**************************************************************** -->
-<!-- ***Specific**************************************************************** -->
-<!-- ***Old documentation****************************************************** -->
-<!-- ***GFDL******************************************************************** -->
-<!-- *************************************************************************** -->
-<!-- Part 6 The End of the Document -->
-</body></html>
-
--- a/INSTALL/gfdl.html	Mon May 24 12:48:09 2010 +0900
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,463 +0,0 @@
-<html lang="en">
-<head>
-<title>Installing GCC: GNU Free Documentation License</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Installing GCC: GNU Free Documentation License">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
-<!--
-Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
-1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
-2008 Free Software Foundation, Inc.
-
-   Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, the Front-Cover texts being (a) (see below), and
-with the Back-Cover Texts being (b) (see below).  A copy of the
-license is included in the section entitled "GNU Free Documentation License".
-
-(a) The FSF's Front-Cover Text is:
-
-     A GNU Manual
-
-(b) The FSF's Back-Cover Text is:
-
-     You have freedom to copy and modify this GNU Manual, like GNU
-     software.  Copies published by the Free Software Foundation raise
-     funds for GNU development.-->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
-</head>
-<body>
-<h1 class="settitle">Installing GCC: GNU Free Documentation License</h1>
-<h1 align="center">Installing GCC: GNU Free Documentation License</h1><!-- man begin DESCRIPTION -->
-
-   <p><a name="index-FDL_002c-GNU-Free-Documentation-License-1"></a><div align="center">Version 1.2, November 2002</div>
-
-<pre class="display">     Copyright &copy; 2000,2001,2002 Free Software Foundation, Inc.
-     51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
-     
-     Everyone is permitted to copy and distribute verbatim copies
-     of this license document, but changing it is not allowed.
-</pre>
-     <ol type=1 start=0>
-<li>PREAMBLE
-
-     <p>The purpose of this License is to make a manual, textbook, or other
-functional and useful document <dfn>free</dfn> in the sense of freedom: to
-assure everyone the effective freedom to copy and redistribute it,
-with or without modifying it, either commercially or noncommercially. 
-Secondarily, this License preserves for the author and publisher a way
-to get credit for their work, while not being considered responsible
-for modifications made by others.
-
-     <p>This License is a kind of &ldquo;copyleft&rdquo;, which means that derivative
-works of the document must themselves be free in the same sense.  It
-complements the GNU General Public License, which is a copyleft
-license designed for free software.
-
-     <p>We have designed this License in order to use it for manuals for free
-software, because free software needs free documentation: a free
-program should come with manuals providing the same freedoms that the
-software does.  But this License is not limited to software manuals;
-it can be used for any textual work, regardless of subject matter or
-whether it is published as a printed book.  We recommend this License
-principally for works whose purpose is instruction or reference.
-
-     <li>APPLICABILITY AND DEFINITIONS
-
-     <p>This License applies to any manual or other work, in any medium, that
-contains a notice placed by the copyright holder saying it can be
-distributed under the terms of this License.  Such a notice grants a
-world-wide, royalty-free license, unlimited in duration, to use that
-work under the conditions stated herein.  The &ldquo;Document&rdquo;, below,
-refers to any such manual or work.  Any member of the public is a
-licensee, and is addressed as &ldquo;you&rdquo;.  You accept the license if you
-copy, modify or distribute the work in a way requiring permission
-under copyright law.
-
-     <p>A &ldquo;Modified Version&rdquo; of the Document means any work containing the
-Document or a portion of it, either copied verbatim, or with
-modifications and/or translated into another language.
-
-     <p>A &ldquo;Secondary Section&rdquo; is a named appendix or a front-matter section
-of the Document that deals exclusively with the relationship of the
-publishers or authors of the Document to the Document's overall
-subject (or to related matters) and contains nothing that could fall
-directly within that overall subject.  (Thus, if the Document is in
-part a textbook of mathematics, a Secondary Section may not explain
-any mathematics.)  The relationship could be a matter of historical
-connection with the subject or with related matters, or of legal,
-commercial, philosophical, ethical or political position regarding
-them.
-
-     <p>The &ldquo;Invariant Sections&rdquo; are certain Secondary Sections whose titles
-are designated, as being those of Invariant Sections, in the notice
-that says that the Document is released under this License.  If a
-section does not fit the above definition of Secondary then it is not
-allowed to be designated as Invariant.  The Document may contain zero
-Invariant Sections.  If the Document does not identify any Invariant
-Sections then there are none.
-
-     <p>The &ldquo;Cover Texts&rdquo; are certain short passages of text that are listed,
-as Front-Cover Texts or Back-Cover Texts, in the notice that says that
-the Document is released under this License.  A Front-Cover Text may
-be at most 5 words, and a Back-Cover Text may be at most 25 words.
-
-     <p>A &ldquo;Transparent&rdquo; copy of the Document means a machine-readable copy,
-represented in a format whose specification is available to the
-general public, that is suitable for revising the document
-straightforwardly with generic text editors or (for images composed of
-pixels) generic paint programs or (for drawings) some widely available
-drawing editor, and that is suitable for input to text formatters or
-for automatic translation to a variety of formats suitable for input
-to text formatters.  A copy made in an otherwise Transparent file
-format whose markup, or absence of markup, has been arranged to thwart
-or discourage subsequent modification by readers is not Transparent. 
-An image format is not Transparent if used for any substantial amount
-of text.  A copy that is not &ldquo;Transparent&rdquo; is called &ldquo;Opaque&rdquo;.
-
-     <p>Examples of suitable formats for Transparent copies include plain
-<span class="sc">ascii</span> without markup, Texinfo input format, LaTeX input
-format, <acronym>SGML</acronym> or <acronym>XML</acronym> using a publicly available
-<acronym>DTD</acronym>, and standard-conforming simple <acronym>HTML</acronym>,
-PostScript or <acronym>PDF</acronym> designed for human modification.  Examples
-of transparent image formats include <acronym>PNG</acronym>, <acronym>XCF</acronym> and
-<acronym>JPG</acronym>.  Opaque formats include proprietary formats that can be
-read and edited only by proprietary word processors, <acronym>SGML</acronym> or
-<acronym>XML</acronym> for which the <acronym>DTD</acronym> and/or processing tools are
-not generally available, and the machine-generated <acronym>HTML</acronym>,
-PostScript or <acronym>PDF</acronym> produced by some word processors for
-output purposes only.
-
-     <p>The &ldquo;Title Page&rdquo; means, for a printed book, the title page itself,
-plus such following pages as are needed to hold, legibly, the material
-this License requires to appear in the title page.  For works in
-formats which do not have any title page as such, &ldquo;Title Page&rdquo; means
-the text near the most prominent appearance of the work's title,
-preceding the beginning of the body of the text.
-
-     <p>A section &ldquo;Entitled XYZ&rdquo; means a named subunit of the Document whose
-title either is precisely XYZ or contains XYZ in parentheses following
-text that translates XYZ in another language.  (Here XYZ stands for a
-specific section name mentioned below, such as &ldquo;Acknowledgements&rdquo;,
-&ldquo;Dedications&rdquo;, &ldquo;Endorsements&rdquo;, or &ldquo;History&rdquo;.)  To &ldquo;Preserve the Title&rdquo;
-of such a section when you modify the Document means that it remains a
-section &ldquo;Entitled XYZ&rdquo; according to this definition.
-
-     <p>The Document may include Warranty Disclaimers next to the notice which
-states that this License applies to the Document.  These Warranty
-Disclaimers are considered to be included by reference in this
-License, but only as regards disclaiming warranties: any other
-implication that these Warranty Disclaimers may have is void and has
-no effect on the meaning of this License.
-
-     <li>VERBATIM COPYING
-
-     <p>You may copy and distribute the Document in any medium, either
-commercially or noncommercially, provided that this License, the
-copyright notices, and the license notice saying this License applies
-to the Document are reproduced in all copies, and that you add no other
-conditions whatsoever to those of this License.  You may not use
-technical measures to obstruct or control the reading or further
-copying of the copies you make or distribute.  However, you may accept
-compensation in exchange for copies.  If you distribute a large enough
-number of copies you must also follow the conditions in section 3.
-
-     <p>You may also lend copies, under the same conditions stated above, and
-you may publicly display copies.
-
-     <li>COPYING IN QUANTITY
-
-     <p>If you publish printed copies (or copies in media that commonly have
-printed covers) of the Document, numbering more than 100, and the
-Document's license notice requires Cover Texts, you must enclose the
-copies in covers that carry, clearly and legibly, all these Cover
-Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
-the back cover.  Both covers must also clearly and legibly identify
-you as the publisher of these copies.  The front cover must present
-the full title with all words of the title equally prominent and
-visible.  You may add other material on the covers in addition. 
-Copying with changes limited to the covers, as long as they preserve
-the title of the Document and satisfy these conditions, can be treated
-as verbatim copying in other respects.
-
-     <p>If the required texts for either cover are too voluminous to fit
-legibly, you should put the first ones listed (as many as fit
-reasonably) on the actual cover, and continue the rest onto adjacent
-pages.
-
-     <p>If you publish or distribute Opaque copies of the Document numbering
-more than 100, you must either include a machine-readable Transparent
-copy along with each Opaque copy, or state in or with each Opaque copy
-a computer-network location from which the general network-using
-public has access to download using public-standard network protocols
-a complete Transparent copy of the Document, free of added material. 
-If you use the latter option, you must take reasonably prudent steps,
-when you begin distribution of Opaque copies in quantity, to ensure
-that this Transparent copy will remain thus accessible at the stated
-location until at least one year after the last time you distribute an
-Opaque copy (directly or through your agents or retailers) of that
-edition to the public.
-
-     <p>It is requested, but not required, that you contact the authors of the
-Document well before redistributing any large number of copies, to give
-them a chance to provide you with an updated version of the Document.
-
-     <li>MODIFICATIONS
-
-     <p>You may copy and distribute a Modified Version of the Document under
-the conditions of sections 2 and 3 above, provided that you release
-the Modified Version under precisely this License, with the Modified
-Version filling the role of the Document, thus licensing distribution
-and modification of the Modified Version to whoever possesses a copy
-of it.  In addition, you must do these things in the Modified Version:
-
-          <ol type=A start=1>
-<li>Use in the Title Page (and on the covers, if any) a title distinct
-from that of the Document, and from those of previous versions
-(which should, if there were any, be listed in the History section
-of the Document).  You may use the same title as a previous version
-if the original publisher of that version gives permission.
-
-          <li>List on the Title Page, as authors, one or more persons or entities
-responsible for authorship of the modifications in the Modified
-Version, together with at least five of the principal authors of the
-Document (all of its principal authors, if it has fewer than five),
-unless they release you from this requirement.
-
-          <li>State on the Title page the name of the publisher of the
-Modified Version, as the publisher.
-
-          <li>Preserve all the copyright notices of the Document.
-
-          <li>Add an appropriate copyright notice for your modifications
-adjacent to the other copyright notices.
-
-          <li>Include, immediately after the copyright notices, a license notice
-giving the public permission to use the Modified Version under the
-terms of this License, in the form shown in the Addendum below.
-
-          <li>Preserve in that license notice the full lists of Invariant Sections
-and required Cover Texts given in the Document's license notice.
-
-          <li>Include an unaltered copy of this License.
-
-          <li>Preserve the section Entitled &ldquo;History&rdquo;, Preserve its Title, and add
-to it an item stating at least the title, year, new authors, and
-publisher of the Modified Version as given on the Title Page.  If
-there is no section Entitled &ldquo;History&rdquo; in the Document, create one
-stating the title, year, authors, and publisher of the Document as
-given on its Title Page, then add an item describing the Modified
-Version as stated in the previous sentence.
-
-          <li>Preserve the network location, if any, given in the Document for
-public access to a Transparent copy of the Document, and likewise
-the network locations given in the Document for previous versions
-it was based on.  These may be placed in the &ldquo;History&rdquo; section. 
-You may omit a network location for a work that was published at
-least four years before the Document itself, or if the original
-publisher of the version it refers to gives permission.
-
-          <li>For any section Entitled &ldquo;Acknowledgements&rdquo; or &ldquo;Dedications&rdquo;, Preserve
-the Title of the section, and preserve in the section all the
-substance and tone of each of the contributor acknowledgements and/or
-dedications given therein.
-
-          <li>Preserve all the Invariant Sections of the Document,
-unaltered in their text and in their titles.  Section numbers
-or the equivalent are not considered part of the section titles.
-
-          <li>Delete any section Entitled &ldquo;Endorsements&rdquo;.  Such a section
-may not be included in the Modified Version.
-
-          <li>Do not retitle any existing section to be Entitled &ldquo;Endorsements&rdquo; or
-to conflict in title with any Invariant Section.
-
-          <li>Preserve any Warranty Disclaimers.
-          </ol>
-
-     <p>If the Modified Version includes new front-matter sections or
-appendices that qualify as Secondary Sections and contain no material
-copied from the Document, you may at your option designate some or all
-of these sections as invariant.  To do this, add their titles to the
-list of Invariant Sections in the Modified Version's license notice. 
-These titles must be distinct from any other section titles.
-
-     <p>You may add a section Entitled &ldquo;Endorsements&rdquo;, provided it contains
-nothing but endorsements of your Modified Version by various
-parties&mdash;for example, statements of peer review or that the text has
-been approved by an organization as the authoritative definition of a
-standard.
-
-     <p>You may add a passage of up to five words as a Front-Cover Text, and a
-passage of up to 25 words as a Back-Cover Text, to the end of the list
-of Cover Texts in the Modified Version.  Only one passage of
-Front-Cover Text and one of Back-Cover Text may be added by (or
-through arrangements made by) any one entity.  If the Document already
-includes a cover text for the same cover, previously added by you or
-by arrangement made by the same entity you are acting on behalf of,
-you may not add another; but you may replace the old one, on explicit
-permission from the previous publisher that added the old one.
-
-     <p>The author(s) and publisher(s) of the Document do not by this License
-give permission to use their names for publicity for or to assert or
-imply endorsement of any Modified Version.
-
-     <li>COMBINING DOCUMENTS
-
-     <p>You may combine the Document with other documents released under this
-License, under the terms defined in section 4 above for modified
-versions, provided that you include in the combination all of the
-Invariant Sections of all of the original documents, unmodified, and
-list them all as Invariant Sections of your combined work in its
-license notice, and that you preserve all their Warranty Disclaimers.
-
-     <p>The combined work need only contain one copy of this License, and
-multiple identical Invariant Sections may be replaced with a single
-copy.  If there are multiple Invariant Sections with the same name but
-different contents, make the title of each such section unique by
-adding at the end of it, in parentheses, the name of the original
-author or publisher of that section if known, or else a unique number. 
-Make the same adjustment to the section titles in the list of
-Invariant Sections in the license notice of the combined work.
-
-     <p>In the combination, you must combine any sections Entitled &ldquo;History&rdquo;
-in the various original documents, forming one section Entitled
-&ldquo;History&rdquo;; likewise combine any sections Entitled &ldquo;Acknowledgements&rdquo;,
-and any sections Entitled &ldquo;Dedications&rdquo;.  You must delete all
-sections Entitled &ldquo;Endorsements.&rdquo;
-
-     <li>COLLECTIONS OF DOCUMENTS
-
-     <p>You may make a collection consisting of the Document and other documents
-released under this License, and replace the individual copies of this
-License in the various documents with a single copy that is included in
-the collection, provided that you follow the rules of this License for
-verbatim copying of each of the documents in all other respects.
-
-     <p>You may extract a single document from such a collection, and distribute
-it individually under this License, provided you insert a copy of this
-License into the extracted document, and follow this License in all
-other respects regarding verbatim copying of that document.
-
-     <li>AGGREGATION WITH INDEPENDENT WORKS
-
-     <p>A compilation of the Document or its derivatives with other separate
-and independent documents or works, in or on a volume of a storage or
-distribution medium, is called an &ldquo;aggregate&rdquo; if the copyright
-resulting from the compilation is not used to limit the legal rights
-of the compilation's users beyond what the individual works permit. 
-When the Document is included in an aggregate, this License does not
-apply to the other works in the aggregate which are not themselves
-derivative works of the Document.
-
-     <p>If the Cover Text requirement of section 3 is applicable to these
-copies of the Document, then if the Document is less than one half of
-the entire aggregate, the Document's Cover Texts may be placed on
-covers that bracket the Document within the aggregate, or the
-electronic equivalent of covers if the Document is in electronic form. 
-Otherwise they must appear on printed covers that bracket the whole
-aggregate.
-
-     <li>TRANSLATION
-
-     <p>Translation is considered a kind of modification, so you may
-distribute translations of the Document under the terms of section 4. 
-Replacing Invariant Sections with translations requires special
-permission from their copyright holders, but you may include
-translations of some or all Invariant Sections in addition to the
-original versions of these Invariant Sections.  You may include a
-translation of this License, and all the license notices in the
-Document, and any Warranty Disclaimers, provided that you also include
-the original English version of this License and the original versions
-of those notices and disclaimers.  In case of a disagreement between
-the translation and the original version of this License or a notice
-or disclaimer, the original version will prevail.
-
-     <p>If a section in the Document is Entitled &ldquo;Acknowledgements&rdquo;,
-&ldquo;Dedications&rdquo;, or &ldquo;History&rdquo;, the requirement (section 4) to Preserve
-its Title (section 1) will typically require changing the actual
-title.
-
-     <li>TERMINATION
-
-     <p>You may not copy, modify, sublicense, or distribute the Document except
-as expressly provided for under this License.  Any other attempt to
-copy, modify, sublicense or distribute the Document is void, and will
-automatically terminate your rights under this License.  However,
-parties who have received copies, or rights, from you under this
-License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
-     <li>FUTURE REVISIONS OF THIS LICENSE
-
-     <p>The Free Software Foundation may publish new, revised versions
-of the GNU Free Documentation License from time to time.  Such new
-versions will be similar in spirit to the present version, but may
-differ in detail to address new problems or concerns.  See
-<a href="http://www.gnu.org/copyleft/">http://www.gnu.org/copyleft/</a>.
-
-     <p>Each version of the License is given a distinguishing version number. 
-If the Document specifies that a particular numbered version of this
-License &ldquo;or any later version&rdquo; applies to it, you have the option of
-following the terms and conditions either of that specified version or
-of any later version that has been published (not as a draft) by the
-Free Software Foundation.  If the Document does not specify a version
-number of this License, you may choose any version ever published (not
-as a draft) by the Free Software Foundation.
-        </ol>
-
-<h3 class="unnumberedsec"><a name="TOC0"></a>ADDENDUM: How to use this License for your documents</h3>
-
-<p>To use this License in a document you have written, include a copy of
-the License in the document and put the following copyright and
-license notices just after the title page:
-
-<pre class="smallexample">       Copyright (C)  <var>year</var>  <var>your name</var>.
-       Permission is granted to copy, distribute and/or modify this document
-       under the terms of the GNU Free Documentation License, Version 1.2
-       or any later version published by the Free Software Foundation;
-       with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
-       Texts.  A copy of the license is included in the section entitled ``GNU
-       Free Documentation License''.
-</pre>
-   <p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
-replace the &ldquo;with...Texts.&rdquo; line with this:
-
-<pre class="smallexample">         with the Invariant Sections being <var>list their titles</var>, with
-         the Front-Cover Texts being <var>list</var>, and with the Back-Cover Texts
-         being <var>list</var>.
-</pre>
-   <p>If you have Invariant Sections without Cover Texts, or some other
-combination of the three, merge those two alternatives to suit the
-situation.
-
-   <p>If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of
-free software license, such as the GNU General Public License,
-to permit their use in free software.
-
-<!-- Local Variables: -->
-<!-- ispell-local-pdict: "ispell-dict" -->
-<!-- End: -->
-<!-- man end -->
-   <p><hr />
-<p><a href="./index.html">Return to the GCC Installation page</a>
-
-<!-- *************************************************************************** -->
-<!-- Part 6 The End of the Document -->
-</body></html>
-
--- a/INSTALL/index.html	Mon May 24 12:48:09 2010 +0900
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,125 +0,0 @@
-<html lang="en">
-<head>
-<title>Installing GCC</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Installing GCC">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
-<!--
-Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
-1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
-2008 Free Software Foundation, Inc.
-
-   Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, the Front-Cover texts being (a) (see below), and
-with the Back-Cover Texts being (b) (see below).  A copy of the
-license is included in the section entitled "GNU Free Documentation License".
-
-(a) The FSF's Front-Cover Text is:
-
-     A GNU Manual
-
-(b) The FSF's Back-Cover Text is:
-
-     You have freedom to copy and modify this GNU Manual, like GNU
-     software.  Copies published by the Free Software Foundation raise
-     funds for GNU development.-->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
-</head>
-<body>
-<h1 class="settitle">Installing GCC</h1>
-The latest version of this document is always available at
-<a href="http://gcc.gnu.org/install/">http://gcc.gnu.org/install/</a>.
-
-   <p>This document describes the generic installation procedure for GCC as well
-as detailing some target specific installation instructions.
-
-   <p>GCC includes several components that previously were separate distributions
-with their own installation instructions.  This document supersedes all
-package specific installation instructions.
-
-   <p><em>Before</em> starting the build/install procedure please check the
-<a href="specific.html">host/target specific installation notes</a>. 
-We recommend you browse the entire generic installation instructions before
-you proceed.
-
-   <p>Lists of successful builds for released versions of GCC are
-available at <a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>. 
-These lists are updated as new information becomes available.
-
-   <p>The installation procedure itself is broken into five steps.
-
-     <ol type=1 start=1>
-<li><a href="prerequisites.html">Prerequisites</a>
-<li><a href="download.html">Downloading the source</a>
-<li><a href="configure.html">Configuration</a>
-<li><a href="build.html">Building</a>
-<li><a href="test.html">Testing</a> (optional)
-<li><a href="finalinstall.html">Final install</a>
-        </ol>
-
-   <p>Please note that GCC does not support &lsquo;<samp><span class="samp">make uninstall</span></samp>&rsquo; and probably
-won't do so in the near future as this would open a can of worms.  Instead,
-we suggest that you install GCC into a directory of its own and simply
-remove that directory when you do not need that specific version of GCC
-any longer, and, if shared libraries are installed there as well, no
-more binaries exist that use them.
-
-   <p>There are also some <a href="old.html">old installation instructions</a>,
-which are mostly obsolete but still contain some information which has
-not yet been merged into the main part of this manual.
-
-   <p><hr />
-<p><a href="./index.html">Return to the GCC Installation page</a>
-
-   <p>Copyright &copy; 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
-1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
-2008 Free Software Foundation, Inc.
-   <pre class="sp">
-
-</pre>
-Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, the Front-Cover texts being (a) (see below), and
-with the Back-Cover Texts being (b) (see below).  A copy of the
-license is included in the section entitled &ldquo;<a href="./gfdl.html">GNU Free Documentation License</a>&rdquo;.
-
-   <p>(a) The FSF's Front-Cover Text is:
-
-   <p>A GNU Manual
-
-   <p>(b) The FSF's Back-Cover Text is:
-
-   <p>You have freedom to copy and modify this GNU Manual, like GNU
-     software.  Copies published by the Free Software Foundation raise
-     funds for GNU development.
-
-<!-- ***Prerequisites************************************************** -->
-<!-- ***Downloading the source************************************************** -->
-<!-- ***Configuration*********************************************************** -->
-<!-- ***Building**************************************************************** -->
-<!-- ***Testing***************************************************************** -->
-<!-- ***Final install*********************************************************** -->
-<!-- ***Binaries**************************************************************** -->
-<!-- ***Specific**************************************************************** -->
-<!-- ***Old documentation****************************************************** -->
-<!-- ***GFDL******************************************************************** -->
-<!-- *************************************************************************** -->
-<!-- Part 6 The End of the Document -->
-</body></html>
-
--- a/INSTALL/old.html	Mon May 24 12:48:09 2010 +0900
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,213 +0,0 @@
-<html lang="en">
-<head>
-<title>Installing GCC: Old documentation</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Installing GCC: Old documentation">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
-<!--
-Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
-1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
-2008 Free Software Foundation, Inc.
-
-   Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, the Front-Cover texts being (a) (see below), and
-with the Back-Cover Texts being (b) (see below).  A copy of the
-license is included in the section entitled "GNU Free Documentation License".
-
-(a) The FSF's Front-Cover Text is:
-
-     A GNU Manual
-
-(b) The FSF's Back-Cover Text is:
-
-     You have freedom to copy and modify this GNU Manual, like GNU
-     software.  Copies published by the Free Software Foundation raise
-     funds for GNU development.-->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
-</head>
-<body>
-<h1 class="settitle">Installing GCC: Old documentation</h1>
-<h1 align="center">Old installation documentation</h1>
-
-   <p>Note most of this information is out of date and superseded by the
-previous chapters of this manual.  It is provided for historical
-reference only, because of a lack of volunteers to merge it into the
-main manual.
-
-   <p>Here is the procedure for installing GCC on a GNU or Unix system.
-
-     <ol type=1 start=1>
-<li>If you have chosen a configuration for GCC which requires other GNU
-tools (such as GAS or the GNU linker) instead of the standard system
-tools, install the required tools in the build directory under the names
-<samp><span class="file">as</span></samp>, <samp><span class="file">ld</span></samp> or whatever is appropriate.
-
-     <p>Alternatively, you can do subsequent compilation using a value of the
-<code>PATH</code> environment variable such that the necessary GNU tools come
-before the standard system tools.
-
-     <li>Specify the host, build and target machine configurations.  You do this
-when you run the <samp><span class="file">configure</span></samp> script.
-
-     <p>The <dfn>build</dfn> machine is the system which you are using, the
-<dfn>host</dfn> machine is the system where you want to run the resulting
-compiler (normally the build machine), and the <dfn>target</dfn> machine is
-the system for which you want the compiler to generate code.
-
-     <p>If you are building a compiler to produce code for the machine it runs
-on (a native compiler), you normally do not need to specify any operands
-to <samp><span class="file">configure</span></samp>; it will try to guess the type of machine you are on
-and use that as the build, host and target machines.  So you don't need
-to specify a configuration when building a native compiler unless
-<samp><span class="file">configure</span></samp> cannot figure out what your configuration is or guesses
-wrong.
-
-     <p>In those cases, specify the build machine's <dfn>configuration name</dfn>
-with the <samp><span class="option">--host</span></samp> option; the host and target will default to be
-the same as the host machine.
-
-     <p>Here is an example:
-
-     <pre class="smallexample">          ./configure --host=sparc-sun-sunos4.1
-</pre>
-     <p>A configuration name may be canonical or it may be more or less
-abbreviated.
-
-     <p>A canonical configuration name has three parts, separated by dashes. 
-It looks like this: &lsquo;<samp><var>cpu</var><span class="samp">-</span><var>company</var><span class="samp">-</span><var>system</var></samp>&rsquo;. 
-(The three parts may themselves contain dashes; <samp><span class="file">configure</span></samp>
-can figure out which dashes serve which purpose.)  For example,
-&lsquo;<samp><span class="samp">m68k-sun-sunos4.1</span></samp>&rsquo; specifies a Sun 3.
-
-     <p>You can also replace parts of the configuration by nicknames or aliases. 
-For example, &lsquo;<samp><span class="samp">sun3</span></samp>&rsquo; stands for &lsquo;<samp><span class="samp">m68k-sun</span></samp>&rsquo;, so
-&lsquo;<samp><span class="samp">sun3-sunos4.1</span></samp>&rsquo; is another way to specify a Sun 3.
-
-     <p>You can specify a version number after any of the system types, and some
-of the CPU types.  In most cases, the version is irrelevant, and will be
-ignored.  So you might as well specify the version if you know it.
-
-     <p>See <a href="#Configurations">Configurations</a>, for a list of supported configuration names and
-notes on many of the configurations.  You should check the notes in that
-section before proceeding any further with the installation of GCC.
-
-        </ol>
-
-   <p><h2><a name="Configurations"></a>Configurations Supported by GCC</h2><a name="index-configurations-supported-by-GCC-1"></a>
-Here are the possible CPU types:
-
-   <blockquote>
-<!-- gmicro, fx80, spur and tahoe omitted since they don't work. -->
-1750a, a29k, alpha, arm, avr, c<var>n</var>, clipper, dsp16xx, elxsi, fr30, h8300,
-hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860, i960, ip2k, m32r,
-m68000, m68k, m6811, m6812, m88k, mcore, mips, mipsel, mips64, mips64el,
-mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle, romp, rs6000, sh, sparc,
-sparclite, sparc64, v850, vax, we32k. 
-</blockquote>
-
-   <p>Here are the recognized company names.  As you can see, customary
-abbreviations are used rather than the longer official names.
-
-<!-- What should be done about merlin, tek*, dolphin? -->
-   <blockquote>
-acorn, alliant, altos, apollo, apple, att, bull,
-cbm, convergent, convex, crds, dec, dg, dolphin,
-elxsi, encore, harris, hitachi, hp, ibm, intergraph, isi,
-mips, motorola, ncr, next, ns, omron, plexus,
-sequent, sgi, sony, sun, tti, unicom, wrs. 
-</blockquote>
-
-   <p>The company name is meaningful only to disambiguate when the rest of
-the information supplied is insufficient.  You can omit it, writing
-just &lsquo;<samp><var>cpu</var><span class="samp">-</span><var>system</var></samp>&rsquo;, if it is not needed.  For example,
-&lsquo;<samp><span class="samp">vax-ultrix4.2</span></samp>&rsquo; is equivalent to &lsquo;<samp><span class="samp">vax-dec-ultrix4.2</span></samp>&rsquo;.
-
-   <p>Here is a list of system types:
-
-   <blockquote>
-386bsd, aix, acis, amigaos, aos, aout, aux, bosx, bsd, clix, coff, ctix, cxux,
-dgux, dynix, ebmon, ecoff, elf, esix, freebsd, hms, genix, gnu, linux,
-linux-gnu, hiux, hpux, iris, irix, isc, luna, lynxos, mach, minix, msdos, mvs,
-netbsd, newsos, nindy, ns, osf, osfrose, ptx, riscix, riscos, rtu, sco, sim,
-solaris, sunos, sym, sysv, udi, ultrix, unicos, uniplus, unos, vms, vsta,
-vxworks, winnt, xenix. 
-</blockquote>
-
-<p class="noindent">You can omit the system type; then <samp><span class="file">configure</span></samp> guesses the
-operating system from the CPU and company.
-
-   <p>You can add a version number to the system type; this may or may not
-make a difference.  For example, you can write &lsquo;<samp><span class="samp">bsd4.3</span></samp>&rsquo; or
-&lsquo;<samp><span class="samp">bsd4.4</span></samp>&rsquo; to distinguish versions of BSD.  In practice, the version
-number is most needed for &lsquo;<samp><span class="samp">sysv3</span></samp>&rsquo; and &lsquo;<samp><span class="samp">sysv4</span></samp>&rsquo;, which are often
-treated differently.
-
-   <p>&lsquo;<samp><span class="samp">linux-gnu</span></samp>&rsquo; is the canonical name for the GNU/Linux target; however
-GCC will also accept &lsquo;<samp><span class="samp">linux</span></samp>&rsquo;.  The version of the kernel in use is
-not relevant on these systems.  A suffix such as &lsquo;<samp><span class="samp">libc1</span></samp>&rsquo; or &lsquo;<samp><span class="samp">aout</span></samp>&rsquo;
-distinguishes major versions of the C library; all of the suffixed versions
-are obsolete.
-
-   <p>If you specify an impossible combination such as &lsquo;<samp><span class="samp">i860-dg-vms</span></samp>&rsquo;,
-then you may get an error message from <samp><span class="file">configure</span></samp>, or it may
-ignore part of the information and do the best it can with the rest. 
-<samp><span class="file">configure</span></samp> always prints the canonical name for the alternative
-that it used.  GCC does not support all possible alternatives.
-
-   <p>Often a particular model of machine has a name.  Many machine names are
-recognized as aliases for CPU/company combinations.  Thus, the machine
-name &lsquo;<samp><span class="samp">sun3</span></samp>&rsquo;, mentioned above, is an alias for &lsquo;<samp><span class="samp">m68k-sun</span></samp>&rsquo;. 
-Sometimes we accept a company name as a machine name, when the name is
-popularly used for a particular machine.  Here is a table of the known
-machine names:
-
-   <blockquote>
-3300, 3b1, 3b<var>n</var>, 7300, altos3068, altos,
-apollo68, att-7300, balance,
-convex-c<var>n</var>, crds, decstation-3100,
-decstation, delta, encore,
-fx2800, gmicro, hp7<var>nn</var>, hp8<var>nn</var>,
-hp9k2<var>nn</var>, hp9k3<var>nn</var>, hp9k7<var>nn</var>,
-hp9k8<var>nn</var>, iris4d, iris, isi68,
-m3230, magnum, merlin, miniframe,
-mmax, news-3600, news800, news, next,
-pbd, pc532, pmax, powerpc, powerpcle, ps2, risc-news,
-rtpc, sun2, sun386i, sun386, sun3,
-sun4, symmetry, tower-32, tower. 
-</blockquote>
-
-<p class="noindent">Remember that a machine name specifies both the cpu type and the company
-name. 
-If you want to install your own homemade configuration files, you can
-use &lsquo;<samp><span class="samp">local</span></samp>&rsquo; as the company name to access them.  If you use
-configuration &lsquo;<samp><var>cpu</var><span class="samp">-local</span></samp>&rsquo;, the configuration name
-without the cpu prefix
-is used to form the configuration file names.
-
-   <p>Thus, if you specify &lsquo;<samp><span class="samp">m68k-local</span></samp>&rsquo;, configuration uses
-files <samp><span class="file">m68k.md</span></samp>, <samp><span class="file">local.h</span></samp>, <samp><span class="file">m68k.c</span></samp>,
-<samp><span class="file">xm-local.h</span></samp>, <samp><span class="file">t-local</span></samp>, and <samp><span class="file">x-local</span></samp>, all in the
-directory <samp><span class="file">config/m68k</span></samp>. 
-<hr />
-<p><a href="./index.html">Return to the GCC Installation page</a>
-
-<!-- ***GFDL******************************************************************** -->
-<!-- *************************************************************************** -->
-<!-- Part 6 The End of the Document -->
-</body></html>
-
--- a/INSTALL/prerequisites.html	Mon May 24 12:48:09 2010 +0900
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,271 +0,0 @@
-<html lang="en">
-<head>
-<title>Prerequisites for GCC</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Prerequisites for GCC">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
-<!--
-Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
-1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
-2008 Free Software Foundation, Inc.
-
-   Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, the Front-Cover texts being (a) (see below), and
-with the Back-Cover Texts being (b) (see below).  A copy of the
-license is included in the section entitled "GNU Free Documentation License".
-
-(a) The FSF's Front-Cover Text is:
-
-     A GNU Manual
-
-(b) The FSF's Back-Cover Text is:
-
-     You have freedom to copy and modify this GNU Manual, like GNU
-     software.  Copies published by the Free Software Foundation raise
-     funds for GNU development.-->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
-</head>
-<body>
-<h1 class="settitle">Prerequisites for GCC</h1>
-<a name="index-Prerequisites-1"></a>
-GCC requires that various tools and packages be available for use in the
-build procedure.  Modifying GCC sources requires additional tools
-described below.
-
-<h3 class="heading"><a name="TOC0"></a>Tools/packages necessary for building GCC</h3>
-
-     <dl>
-<dt>ISO C90 compiler<dd>Necessary to bootstrap GCC, although versions of GCC prior
-to 3.4 also allow bootstrapping with a traditional (K&amp;R) C compiler.
-
-     <p>To build all languages in a cross-compiler or other configuration where
-3-stage bootstrap is not performed, you need to start with an existing
-GCC binary (version 2.95 or later) because source code for language
-frontends other than C might use GCC extensions.
-
-     <br><dt>GNAT<dd>
-In order to build the Ada compiler (GNAT) you must already have GNAT
-installed because portions of the Ada frontend are written in Ada (with
-GNAT extensions.)  Refer to the Ada installation instructions for more
-specific information.
-
-     <br><dt>A &ldquo;working&rdquo; POSIX compatible shell, or GNU bash<dd>
-Necessary when running <samp><span class="command">configure</span></samp> because some
-<samp><span class="command">/bin/sh</span></samp> shells have bugs and may crash when configuring the
-target libraries.  In other cases, <samp><span class="command">/bin/sh</span></samp> or <samp><span class="command">ksh</span></samp>
-have disastrous corner-case performance problems.  This
-can cause target <samp><span class="command">configure</span></samp> runs to literally take days to
-complete in some cases.
-
-     <p>So on some platforms <samp><span class="command">/bin/ksh</span></samp> is sufficient, on others it
-isn't.  See the host/target specific instructions for your platform, or
-use <samp><span class="command">bash</span></samp> to be sure.  Then set <samp><span class="env">CONFIG_SHELL</span></samp> in your
-environment to your &ldquo;good&rdquo; shell prior to running
-<samp><span class="command">configure</span></samp>/<samp><span class="command">make</span></samp>.
-
-     <p><samp><span class="command">zsh</span></samp> is not a fully compliant POSIX shell and will not
-work when configuring GCC.
-
-     <br><dt>A POSIX or SVR4 awk<dd>
-Necessary for creating some of the generated source files for GCC. 
-If in doubt, use a recent GNU awk version, as some of the older ones
-are broken.  GNU awk version 3.1.5 is known to work.
-
-     <br><dt>GNU binutils<dd>
-Necessary in some circumstances, optional in others.  See the
-host/target specific instructions for your platform for the exact
-requirements.
-
-     <br><dt>gzip version 1.2.4 (or later) or<dt>bzip2 version 1.0.2 (or later)<dd>
-Necessary to uncompress GCC <samp><span class="command">tar</span></samp> files when source code is
-obtained via FTP mirror sites.
-
-     <br><dt>GNU make version 3.80 (or later)<dd>
-You must have GNU make installed to build GCC.
-
-     <br><dt>GNU tar version 1.14 (or later)<dd>
-Necessary (only on some platforms) to untar the source code.  Many
-systems' <samp><span class="command">tar</span></samp> programs will also work, only try GNU
-<samp><span class="command">tar</span></samp> if you have problems.
-
-     <br><dt>GNU Multiple Precision Library (GMP) version 4.1 (or later)<dd>
-Necessary to build GCC.  If you do not have it installed in your
-library search path, you will have to configure with the
-<samp><span class="option">--with-gmp</span></samp> configure option.  See also <samp><span class="option">--with-gmp-lib</span></samp>
-and <samp><span class="option">--with-gmp-include</span></samp>.  Alternatively, if a GMP source
-distribution is found in a subdirectory of your GCC sources named
-<samp><span class="file">gmp</span></samp>, it will be built together with GCC.
-
-     <br><dt>MPFR Library version 2.3.2 (or later)<dd>
-Necessary to build GCC.  It can be downloaded from
-<a href="http://www.mpfr.org/">http://www.mpfr.org/</a>.  The version of MPFR that is bundled with
-GMP 4.1.x contains numerous bugs.  Although GCC may appear to function
-with the buggy versions of MPFR, there are a few bugs that will not be
-fixed when using this version.  It is strongly recommended to upgrade
-to the recommended version of MPFR.
-
-     <p>The <samp><span class="option">--with-mpfr</span></samp> configure option should be used if your MPFR
-Library is not installed in your default library search path.  See also
-<samp><span class="option">--with-mpfr-lib</span></samp> and <samp><span class="option">--with-mpfr-include</span></samp>. 
-Alternatively, if a MPFR source distribution is found in a subdirectory
-of your GCC sources named <samp><span class="file">mpfr</span></samp>, it will be built together with
-GCC.
-
-     <br><dt>Parma Polyhedra Library (PPL) version 0.10<dd>
-Necessary to build GCC with the Graphite loop optimizations. 
-It can be downloaded from <a href="http://www.cs.unipr.it/ppl/Download/">http://www.cs.unipr.it/ppl/Download/</a>.
-
-     <p>The <samp><span class="option">--with-ppl</span></samp> configure option should be used if PPL is not
-installed in your default library search path.
-
-     <br><dt>CLooG-PPL version 0.15<dd>
-Necessary to build GCC with the Graphite loop optimizations.  It can
-be downloaded from <a href="ftp://gcc.gnu.org/pub/gcc/infrastructure/">ftp://gcc.gnu.org/pub/gcc/infrastructure/</a>. 
-The code in <samp><span class="file">cloog-ppl-0.15.tar.gz</span></samp> comes from a branch of CLooG
-available from <a href="http://repo.or.cz/w/cloog-ppl.git">http://repo.or.cz/w/cloog-ppl.git</a>.  CLooG-PPL
-should be configured with <samp><span class="option">--with-ppl</span></samp>.
-
-     <p>The <samp><span class="option">--with-cloog</span></samp> configure option should be used if CLooG is
-not installed in your default library search path.
-
-     <br><dt><samp><span class="command">jar</span></samp>, or InfoZIP (<samp><span class="command">zip</span></samp> and <samp><span class="command">unzip</span></samp>)<dd>
-Necessary to build libgcj, the GCJ runtime.
-
-</dl>
-
-<h3 class="heading"><a name="TOC1"></a>Tools/packages necessary for modifying GCC</h3>
-
-     <dl>
-<dt>autoconf version 2.59<dt>GNU m4 version 1.4 (or later)<dd>
-Necessary when modifying <samp><span class="file">configure.ac</span></samp>, <samp><span class="file">aclocal.m4</span></samp>, etc. 
-to regenerate <samp><span class="file">configure</span></samp> and <samp><span class="file">config.in</span></samp> files.
-
-     <br><dt>automake version 1.9.6<dd>
-Necessary when modifying a <samp><span class="file">Makefile.am</span></samp> file to regenerate its
-associated <samp><span class="file">Makefile.in</span></samp>.
-
-     <p>Much of GCC does not use automake, so directly edit the <samp><span class="file">Makefile.in</span></samp>
-file.  Specifically this applies to the <samp><span class="file">gcc</span></samp>, <samp><span class="file">intl</span></samp>,
-<samp><span class="file">libcpp</span></samp>, <samp><span class="file">libiberty</span></samp>, <samp><span class="file">libobjc</span></samp> directories as well
-as any of their subdirectories.
-
-     <p>For directories that use automake, GCC requires the latest release in
-the 1.9.x series, which is currently 1.9.6.  When regenerating a directory
-to a newer version, please update all the directories using an older 1.9.x
-to the latest released version.
-
-     <br><dt>gettext version 0.14.5 (or later)<dd>
-Needed to regenerate <samp><span class="file">gcc.pot</span></samp>.
-
-     <br><dt>gperf version 2.7.2 (or later)<dd>
-Necessary when modifying <samp><span class="command">gperf</span></samp> input files, e.g. 
-<samp><span class="file">gcc/cp/cfns.gperf</span></samp> to regenerate its associated header file, e.g. 
-<samp><span class="file">gcc/cp/cfns.h</span></samp>.
-
-     <br><dt>DejaGnu 1.4.4<dt>Expect<dt>Tcl<dd>
-Necessary to run the GCC testsuite; see the section on testing for details.
-
-     <br><dt>autogen version 5.5.4 (or later) and<dt>guile version 1.4.1 (or later)<dd>
-Necessary to regenerate <samp><span class="file">fixinc/fixincl.x</span></samp> from
-<samp><span class="file">fixinc/inclhack.def</span></samp> and <samp><span class="file">fixinc/*.tpl</span></samp>.
-
-     <p>Necessary to run &lsquo;<samp><span class="samp">make check</span></samp>&rsquo; for <samp><span class="file">fixinc</span></samp>.
-
-     <p>Necessary to regenerate the top level <samp><span class="file">Makefile.in</span></samp> file from
-<samp><span class="file">Makefile.tpl</span></samp> and <samp><span class="file">Makefile.def</span></samp>.
-
-     <br><dt>Flex version 2.5.4 (or later)<dd>
-Necessary when modifying <samp><span class="file">*.l</span></samp> files.
-
-     <p>Necessary to build GCC during development because the generated output
-files are not included in the SVN repository.  They are included in
-releases.
-
-     <br><dt>Texinfo version 4.7 (or later)<dd>
-Necessary for running <samp><span class="command">makeinfo</span></samp> when modifying <samp><span class="file">*.texi</span></samp>
-files to test your changes.
-
-     <p>Necessary for running <samp><span class="command">make dvi</span></samp> or <samp><span class="command">make pdf</span></samp> to
-create printable documentation in DVI or PDF format.  Texinfo version
-4.8 or later is required for <samp><span class="command">make pdf</span></samp>.
-
-     <p>Necessary to build GCC documentation during development because the
-generated output files are not included in the SVN repository.  They are
-included in releases.
-
-     <br><dt>TeX (any working version)<dd>
-Necessary for running <samp><span class="command">texi2dvi</span></samp> and <samp><span class="command">texi2pdf</span></samp>, which
-are used when running <samp><span class="command">make dvi</span></samp> or <samp><span class="command">make pdf</span></samp> to create
-DVI or PDF files, respectively.
-
-     <br><dt>SVN (any version)<dt>SSH (any version)<dd>
-Necessary to access the SVN repository.  Public releases and weekly
-snapshots of the development sources are also available via FTP.
-
-     <br><dt>Perl version 5.6.1 (or later)<dd>
-Necessary when regenerating <samp><span class="file">Makefile</span></samp> dependencies in libiberty. 
-Necessary when regenerating <samp><span class="file">libiberty/functions.texi</span></samp>. 
-Necessary when generating manpages from Texinfo manuals. 
-Necessary when targetting Darwin, building libstdc++,
-and not using <samp><span class="option">--disable-symvers</span></samp>. 
-Used by various scripts to generate some files included in SVN (mainly
-Unicode-related and rarely changing) from source tables.
-
-     <br><dt>GNU diffutils version 2.7 (or later)<dd>
-Useful when submitting patches for the GCC source code.
-
-     <br><dt>patch version 2.5.4 (or later)<dd>
-Necessary when applying patches, created with <samp><span class="command">diff</span></samp>, to one's
-own sources.
-
-     <br><dt>ecj1<dt>gjavah<dd>
-If you wish to modify <samp><span class="file">.java</span></samp> files in libjava, you will need to
-configure with <samp><span class="option">--enable-java-maintainer-mode</span></samp>, and you will need
-to have executables named <samp><span class="command">ecj1</span></samp> and <samp><span class="command">gjavah</span></samp> in your path. 
-The <samp><span class="command">ecj1</span></samp> executable should run the Eclipse Java compiler via
-the GCC-specific entry point.  You can download a suitable jar from
-<a href="ftp://sourceware.org/pub/java/">ftp://sourceware.org/pub/java/</a>, or by running the script
-<samp><span class="command">contrib/download_ecj</span></samp>.
-
-     <br><dt>antlr.jar version 2.7.1 (or later)<dt>antlr binary<dd>
-If you wish to build the <samp><span class="command">gjdoc</span></samp> binary in libjava, you will
-need to have a <samp><span class="file">antlr.jar</span></samp> library available. The library is
-searched in system locations but can be configured with
-<samp><span class="option">--with-antlr-jar=</span></samp> instead.  When configuring with
-<samp><span class="option">--enable-java-maintainer-mode</span></samp>, you will need to have one of
-the executables named <samp><span class="command">cantlr</span></samp>, <samp><span class="command">runantlr</span></samp> or
-<samp><span class="command">antlr</span></samp> in your path.
-
-</dl>
-
-   <p><hr />
-<p><a href="./index.html">Return to the GCC Installation page</a>
-
-<!-- ***Downloading the source************************************************** -->
-<!-- ***Configuration*********************************************************** -->
-<!-- ***Building**************************************************************** -->
-<!-- ***Testing***************************************************************** -->
-<!-- ***Final install*********************************************************** -->
-<!-- ***Binaries**************************************************************** -->
-<!-- ***Specific**************************************************************** -->
-<!-- ***Old documentation****************************************************** -->
-<!-- ***GFDL******************************************************************** -->
-<!-- *************************************************************************** -->
-<!-- Part 6 The End of the Document -->
-</body></html>
-
--- a/INSTALL/specific.html	Mon May 24 12:48:09 2010 +0900
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,1542 +0,0 @@
-<html lang="en">
-<head>
-<title>Host/Target specific installation notes for GCC</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Host/Target specific installation notes for GCC">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
-<!--
-Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
-1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
-2008 Free Software Foundation, Inc.
-
-   Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, the Front-Cover texts being (a) (see below), and
-with the Back-Cover Texts being (b) (see below).  A copy of the
-license is included in the section entitled "GNU Free Documentation License".
-
-(a) The FSF's Front-Cover Text is:
-
-     A GNU Manual
-
-(b) The FSF's Back-Cover Text is:
-
-     You have freedom to copy and modify this GNU Manual, like GNU
-     software.  Copies published by the Free Software Foundation raise
-     funds for GNU development.-->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
-</head>
-<body>
-<h1 class="settitle">Host/Target specific installation notes for GCC</h1>
-<a name="index-Specific-1"></a><a name="index-Specific-installation-notes-2"></a><a name="index-Target-specific-installation-3"></a><a name="index-Host-specific-installation-4"></a><a name="index-Target-specific-installation-notes-5"></a>
-Please read this document carefully <em>before</em> installing the
-GNU Compiler Collection on your machine.
-
-   <p>Note that this list of install notes is <em>not</em> a list of supported
-hosts or targets.  Not all supported hosts and targets are listed
-here, only the ones that require host-specific or target-specific
-information are.
-
-     <ul>
-<li><a href="#alpha-x-x">alpha*-*-*</a>
-<li><a href="#alpha-dec-osf">alpha*-dec-osf*</a>
-<li><a href="#arc-x-elf">arc-*-elf</a>
-<li><a href="#arm-x-elf">arm-*-elf</a>
-<a href="#arm-x-coff">arm-*-coff</a>
-<a href="#arm-x-aout">arm-*-aout</a>
-<li><a href="#avr">avr</a>
-<li><a href="#bfin">Blackfin</a>
-<li><a href="#dos">DOS</a>
-<li><a href="#x-x-freebsd">*-*-freebsd*</a>
-<li><a href="#h8300-hms">h8300-hms</a>
-<li><a href="#hppa-hp-hpux">hppa*-hp-hpux*</a>
-<li><a href="#hppa-hp-hpux10">hppa*-hp-hpux10</a>
-<li><a href="#hppa-hp-hpux11">hppa*-hp-hpux11</a>
-<li><a href="#x-x-linux-gnu">*-*-linux-gnu</a>
-<li><a href="#ix86-x-linux">i?86-*-linux*</a>
-<li><a href="#ix86-x-solaris210">i?86-*-solaris2.10</a>
-<li><a href="#ia64-x-linux">ia64-*-linux</a>
-<li><a href="#ia64-x-hpux">ia64-*-hpux*</a>
-<li><a href="#x-ibm-aix">*-ibm-aix*</a>
-<li><a href="#iq2000-x-elf">iq2000-*-elf</a>
-<li><a href="#m32c-x-elf">m32c-*-elf</a>
-<li><a href="#m32r-x-elf">m32r-*-elf</a>
-<li><a href="#m6811-elf">m6811-elf</a>
-<li><a href="#m6812-elf">m6812-elf</a>
-<li><a href="#m68k-x-x">m68k-*-*</a>
-<li><a href="#m68k-uclinux">m68k-uclinux</a>
-<li><a href="#mips-x-x">mips-*-*</a>
-<li><a href="#mips-sgi-irix5">mips-sgi-irix5</a>
-<li><a href="#mips-sgi-irix6">mips-sgi-irix6</a>
-<li><a href="#powerpc-x-x">powerpc*-*-*</a>
-<li><a href="#powerpc-x-darwin">powerpc-*-darwin*</a>
-<li><a href="#powerpc-x-elf">powerpc-*-elf</a>
-<li><a href="#powerpc-x-linux-gnu">powerpc*-*-linux-gnu*</a>
-<li><a href="#powerpc-x-netbsd">powerpc-*-netbsd*</a>
-<li><a href="#powerpc-x-eabisim">powerpc-*-eabisim</a>
-<li><a href="#powerpc-x-eabi">powerpc-*-eabi</a>
-<li><a href="#powerpcle-x-elf">powerpcle-*-elf</a>
-<li><a href="#powerpcle-x-eabisim">powerpcle-*-eabisim</a>
-<li><a href="#powerpcle-x-eabi">powerpcle-*-eabi</a>
-<li><a href="#s390-x-linux">s390-*-linux*</a>
-<li><a href="#s390x-x-linux">s390x-*-linux*</a>
-<li><a href="#s390x-ibm-tpf">s390x-ibm-tpf*</a>
-<li><a href="#x-x-solaris2">*-*-solaris2*</a>
-<li><a href="#sparc-sun-solaris2">sparc-sun-solaris2*</a>
-<li><a href="#sparc-sun-solaris27">sparc-sun-solaris2.7</a>
-<li><a href="#sparc-x-linux">sparc-*-linux*</a>
-<li><a href="#sparc64-x-solaris2">sparc64-*-solaris2*</a>
-<li><a href="#sparcv9-x-solaris2">sparcv9-*-solaris2*</a>
-<li><a href="#x-x-vxworks">*-*-vxworks*</a>
-<li><a href="#x86-64-x-x">x86_64-*-*</a> amd64-*-*
-<li><a href="#xtensa-x-elf">xtensa*-*-elf</a>
-<li><a href="#xtensa-x-linux">xtensa*-*-linux*</a>
-<li><a href="#windows">Microsoft Windows</a>
-<li><a href="#x-x-cygwin">*-*-cygwin</a>
-<li><a href="#x-x-interix">*-*-interix</a>
-<li><a href="#x-x-mingw">*-*-mingw</a>
-<li><a href="#os2">OS/2</a>
-<li><a href="#older">Older systems</a>
-</ul>
-
-     <ul>
-<li><a href="#elf">all ELF targets</a> (SVR4, Solaris 2, etc.) 
-</ul>
-
-   <p><!-- -------- host/target specific issues start here ---------------- -->
-<hr />
-
-<h3 class="heading"><a name="TOC0"></a><a name="alpha_002dx_002dx"></a>alpha*-*-*</h3>
-
-<p>This section contains general configuration information for all
-alpha-based platforms using ELF (in particular, ignore this section for
-DEC OSF/1, Digital UNIX and Tru64 UNIX).  In addition to reading this
-section, please read all other sections that match your target.
-
-   <p>We require binutils 2.11.2 or newer. 
-Previous binutils releases had a number of problems with DWARF 2
-debugging information, not the least of which is incorrect linking of
-shared libraries.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC1"></a><a name="alpha_002ddec_002dosf"></a>alpha*-dec-osf*</h3>
-
-<p>Systems using processors that implement the DEC Alpha architecture and
-are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq
-Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
-
-   <p>As of GCC 3.2, versions before <code>alpha*-dec-osf4</code> are no longer
-supported.  (These are the versions which identify themselves as DEC
-OSF/1.)
-
-   <p>In Digital Unix V4.0, virtual memory exhausted bootstrap failures
-may be fixed by configuring with <samp><span class="option">--with-gc=simple</span></samp>,
-reconfiguring Kernel Virtual Memory and Swap parameters
-per the <samp><span class="command">/usr/sbin/sys_check</span></samp> Tuning Suggestions,
-or applying the patch in
-<a href="http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html">http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html</a>.
-
-   <p>In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not
-currently (2001-06-13) work with <samp><span class="command">mips-tfile</span></samp>.  As a workaround,
-we need to use the old assembler, invoked via the barely documented
-<samp><span class="option">-oldas</span></samp> option.  To bootstrap GCC, you either need to use the
-Compaq C Compiler:
-
-<pre class="smallexample">        % CC=cc <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
-</pre>
-   <p>or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
-
-<pre class="smallexample">        % CC=gcc -Wa,-oldas <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
-</pre>
-   <p>As of GNU binutils 2.11.2, neither GNU <samp><span class="command">as</span></samp> nor GNU <samp><span class="command">ld</span></samp>
-are supported on Tru64 UNIX, so you must not configure GCC with
-<samp><span class="option">--with-gnu-as</span></samp> or <samp><span class="option">--with-gnu-ld</span></samp>.
-
-   <p>GCC writes a &lsquo;<samp><span class="samp">.verstamp</span></samp>&rsquo; directive to the assembler output file
-unless it is built as a cross-compiler.  It gets the version to use from
-the system header file <samp><span class="file">/usr/include/stamp.h</span></samp>.  If you install a
-new version of DEC Unix, you should rebuild GCC to pick up the new version
-stamp.
-
-   <p>&lsquo;<samp><span class="samp">make compare</span></samp>&rsquo; may fail on old versions of DEC Unix unless you add
-<samp><span class="option">-save-temps</span></samp> to <code>BOOT_CFLAGS</code>.  On these systems, the name
-of the assembler input file is stored in the object file, and that makes
-comparison fail if it differs between the <code>stage1</code> and
-<code>stage2</code> compilations.  The option <samp><span class="option">-save-temps</span></samp> forces a
-fixed name to be used for the assembler input file, instead of a
-randomly chosen name in <samp><span class="file">/tmp</span></samp>.  Do not add <samp><span class="option">-save-temps</span></samp>
-unless the comparisons fail without that option.  If you add
-<samp><span class="option">-save-temps</span></samp>, you will have to manually delete the &lsquo;<samp><span class="samp">.i</span></samp>&rsquo; and
-&lsquo;<samp><span class="samp">.s</span></samp>&rsquo; files after each series of compilations.
-
-   <p>GCC now supports both the native (ECOFF) debugging format used by DBX
-and GDB and an encapsulated STABS format for use only with GDB.  See the
-discussion of the <samp><span class="option">--with-stabs</span></samp> option of <samp><span class="file">configure</span></samp> above
-for more information on these formats and how to select them.
-
-   <p>There is a bug in DEC's assembler that produces incorrect line numbers
-for ECOFF format when the &lsquo;<samp><span class="samp">.align</span></samp>&rsquo; directive is used.  To work
-around this problem, GCC will not emit such alignment directives
-while writing ECOFF format debugging information even if optimization is
-being performed.  Unfortunately, this has the very undesirable
-side-effect that code addresses when <samp><span class="option">-O</span></samp> is specified are
-different depending on whether or not <samp><span class="option">-g</span></samp> is also specified.
-
-   <p>To avoid this behavior, specify <samp><span class="option">-gstabs+</span></samp> and use GDB instead of
-DBX.  DEC is now aware of this problem with the assembler and hopes to
-provide a fix shortly.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC2"></a><a name="arc_002dx_002delf"></a>arc-*-elf</h3>
-
-<p>Argonaut ARC processor. 
-This configuration is intended for embedded systems.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC3"></a><a name="arm_002dx_002delf"></a>arm-*-elf</h3>
-
-<p>ARM-family processors.  Subtargets that use the ELF object format
-require GNU binutils 2.13 or newer.  Such subtargets include:
-<code>arm-*-freebsd</code>, <code>arm-*-netbsdelf</code>, <code>arm-*-*linux</code>
-and <code>arm-*-rtems</code>.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC4"></a><a name="arm_002dx_002dcoff"></a>arm-*-coff</h3>
-
-<p>ARM-family processors.  Note that there are two different varieties
-of PE format subtarget supported: <code>arm-wince-pe</code> and
-<code>arm-pe</code> as well as a standard COFF target <code>arm-*-coff</code>.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC5"></a><a name="arm_002dx_002daout"></a>arm-*-aout</h3>
-
-<p>ARM-family processors.  These targets support the AOUT file format:
-<code>arm-*-aout</code>, <code>arm-*-netbsd</code>.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC6"></a><a name="avr"></a>avr</h3>
-
-<p>ATMEL AVR-family micro controllers.  These are used in embedded
-applications.  There are no standard Unix configurations. 
-See &ldquo;AVR Options&rdquo; in the main manual
-for the list of supported MCU types.
-
-   <p>Use &lsquo;<samp><span class="samp">configure --target=avr --enable-languages="c"</span></samp>&rsquo; to configure GCC.
-
-   <p>Further installation notes and other useful information about AVR tools
-can also be obtained from:
-
-     <ul>
-<li><a href="http://www.nongnu.org/avr/">http://www.nongnu.org/avr/</a>
-<li><a href="http://www.amelek.gda.pl/avr/">http://www.amelek.gda.pl/avr/</a>
-</ul>
-
-   <p>We <em>strongly</em> recommend using binutils 2.13 or newer.
-
-   <p>The following error:
-<pre class="smallexample">       Error: register required
-</pre>
-   <p>indicates that you should upgrade to a newer version of the binutils.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC7"></a><a name="bfin"></a>Blackfin</h3>
-
-<p>The Blackfin processor, an Analog Devices DSP. 
-See &ldquo;Blackfin Options&rdquo; in the main manual
-
-   <p>More information, and a version of binutils with support for this processor,
-is available at <a href="http://blackfin.uclinux.org">http://blackfin.uclinux.org</a>
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC8"></a><a name="cris"></a>CRIS</h3>
-
-<p>CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
-series.  These are used in embedded applications.
-
-   <p>See &ldquo;CRIS Options&rdquo; in the main manual
-for a list of CRIS-specific options.
-
-   <p>There are a few different CRIS targets:
-     <dl>
-<dt><code>cris-axis-elf</code><dd>Mainly for monolithic embedded systems.  Includes a multilib for the
-&lsquo;<samp><span class="samp">v10</span></samp>&rsquo; core used in &lsquo;<samp><span class="samp">ETRAX 100 LX</span></samp>&rsquo;. 
-<br><dt><code>cris-axis-linux-gnu</code><dd>A GNU/Linux port for the CRIS architecture, currently targeting
-&lsquo;<samp><span class="samp">ETRAX 100 LX</span></samp>&rsquo; by default. 
-</dl>
-
-   <p>For <code>cris-axis-elf</code> you need binutils 2.11
-or newer.  For <code>cris-axis-linux-gnu</code> you need binutils 2.12 or newer.
-
-   <p>Pre-packaged tools can be obtained from
-<a href="ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/">ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/</a>.  More
-information about this platform is available at
-<a href="http://developer.axis.com/">http://developer.axis.com/</a>.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC9"></a><a name="crx"></a>CRX</h3>
-
-<p>The CRX CompactRISC architecture is a low-power 32-bit architecture with
-fast context switching and architectural extensibility features.
-
-   <p>See &ldquo;CRX Options&rdquo; in the main manual for a list of CRX-specific options.
-
-   <p>Use &lsquo;<samp><span class="samp">configure --target=crx-elf --enable-languages=c,c++</span></samp>&rsquo; to configure
-GCC for building a CRX cross-compiler. The option &lsquo;<samp><span class="samp">--target=crx-elf</span></samp>&rsquo;
-is also used to build the &lsquo;<samp><span class="samp">newlib</span></samp>&rsquo; C library for CRX.
-
-   <p>It is also possible to build libstdc++-v3 for the CRX architecture. This
-needs to be done in a separate step with the following configure settings:
-&lsquo;<samp><span class="samp">gcc/libstdc++-v3/configure --host=crx-elf --with-newlib
---enable-sjlj-exceptions --enable-cxx-flags='-fexceptions -frtti'</span></samp>&rsquo;
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC10"></a><a name="dos"></a>DOS</h3>
-
-<p>Please have a look at the <a href="binaries.html">binaries page</a>.
-
-   <p>You cannot install GCC by itself on MSDOS; it will not compile under
-any MSDOS compiler except itself.  You need to get the complete
-compilation package DJGPP, which includes binaries as well as sources,
-and includes all the necessary compilation tools and libraries.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC11"></a><a name="x_002dx_002dfreebsd"></a>*-*-freebsd*</h3>
-
-<p>The version of binutils installed in <samp><span class="file">/usr/bin</span></samp> probably works with
-this release of GCC.  However, on FreeBSD 4, bootstrapping against the
-latest FSF binutils is known to improve overall testsuite results; and,
-on FreeBSD/alpha, using binutils 2.14 or later is required to build libjava.
-
-   <p>Support for FreeBSD 1 was discontinued in GCC 3.2.
-
-   <p>Support for FreeBSD 2 will be discontinued after GCC 3.4.  The
-following was true for GCC 3.1 but the current status is unknown. 
-For FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All
-configuration support and files as shipped with GCC 2.95 are still in
-place.  FreeBSD 2.2.7 has been known to bootstrap completely; however,
-it is unknown which version of binutils was used (it is assumed that it
-was the system copy in <samp><span class="file">/usr/bin</span></samp>) and C++ EH failures were noted.
-
-   <p>For FreeBSD using the ELF file format: DWARF 2 debugging is now the
-default for all CPU architectures.  It had been the default on
-FreeBSD/alpha since its inception.  You may use <samp><span class="option">-gstabs</span></samp> instead
-of <samp><span class="option">-g</span></samp>, if you really want the old debugging format.  There are
-no known issues with mixing object files and libraries with different
-debugging formats.  Otherwise, this release of GCC should now match more
-of the configuration used in the stock FreeBSD configuration of GCC.  In
-particular, <samp><span class="option">--enable-threads</span></samp> is now configured by default. 
-However, as a general user, do not attempt to replace the system
-compiler with this release.  Known to bootstrap and check with good
-results on FreeBSD 4.9-STABLE and 5-CURRENT.  In the past, known to
-bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
-4.3, 4.4, 4.5, 4.8-STABLE.
-
-   <p>In principle, <samp><span class="option">--enable-threads</span></samp> is now compatible with
-<samp><span class="option">--enable-libgcj</span></samp> on FreeBSD.  However, it has only been built
-and tested on &lsquo;<samp><span class="samp">i386-*-freebsd[45]</span></samp>&rsquo; and &lsquo;<samp><span class="samp">alpha-*-freebsd[45]</span></samp>&rsquo;. 
-The static
-library may be incorrectly built (symbols are missing at link time). 
-There is a rare timing-based startup hang (probably involves an
-assumption about the thread library).  Multi-threaded boehm-gc (required for
-libjava) exposes severe threaded signal-handling bugs on FreeBSD before
-4.5-RELEASE.  Other CPU architectures
-supported by FreeBSD will require additional configuration tuning in, at
-the very least, both boehm-gc and libffi.
-
-   <p>Shared <samp><span class="file">libgcc_s.so</span></samp> is now built and installed by default.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC12"></a><a name="h8300_002dhms"></a>h8300-hms</h3>
-
-<p>Renesas H8/300 series of processors.
-
-   <p>Please have a look at the <a href="binaries.html">binaries page</a>.
-
-   <p>The calling convention and structure layout has changed in release 2.6. 
-All code must be recompiled.  The calling convention now passes the
-first three arguments in function calls in registers.  Structures are no
-longer a multiple of 2 bytes.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC13"></a><a name="hppa_002dhp_002dhpux"></a>hppa*-hp-hpux*</h3>
-
-<p>Support for HP-UX version 9 and older was discontinued in GCC 3.4.
-
-   <p>We require using gas/binutils on all hppa platforms.  Version 2.19 or
-later is recommended.
-
-   <p>It may be helpful to configure GCC with the
-<a href="./configure.html#with-gnu-as"><samp><span class="option">--with-gnu-as</span></samp></a> and
-<samp><span class="option">--with-as=...</span></samp> options to ensure that GCC can find GAS.
-
-   <p>The HP assembler should not be used with GCC.  It is rarely tested and may
-not work.  It shouldn't be used with any languages other than C due to its
-many limitations.
-
-   <p>Specifically, <samp><span class="option">-g</span></samp> does not work (HP-UX uses a peculiar debugging
-format which GCC does not know about).  It also inserts timestamps
-into each object file it creates, causing the 3-stage comparison test to
-fail during a bootstrap.  You should be able to continue by saying
-&lsquo;<samp><span class="samp">make all-host all-target</span></samp>&rsquo; after getting the failure from &lsquo;<samp><span class="samp">make</span></samp>&rsquo;.
-
-   <p>Various GCC features are not supported.  For example, it does not support weak
-symbols or alias definitions.  As a result, explicit template instantiations
-are required when using C++.  This makes it difficult if not impossible to
-build many C++ applications.
-
-   <p>There are two default scheduling models for instructions.  These are
-PROCESSOR_7100LC and PROCESSOR_8000.  They are selected from the pa-risc
-architecture specified for the target machine when configuring. 
-PROCESSOR_8000 is the default.  PROCESSOR_7100LC is selected when
-the target is a &lsquo;<samp><span class="samp">hppa1*</span></samp>&rsquo; machine.
-
-   <p>The PROCESSOR_8000 model is not well suited to older processors.  Thus,
-it is important to completely specify the machine architecture when
-configuring if you want a model other than PROCESSOR_8000.  The macro
-TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
-default scheduling model is desired.
-
-   <p>As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
-through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later. 
-This namespace change might cause problems when bootstrapping with
-an earlier version of GCC or the HP compiler as essentially the same
-namespace is required for an entire build.  This problem can be avoided
-in a number of ways.  With HP cc, <samp><span class="env">UNIX_STD</span></samp> can be set to &lsquo;<samp><span class="samp">95</span></samp>&rsquo;
-or &lsquo;<samp><span class="samp">98</span></samp>&rsquo;.  Another way is to add an appropriate set of predefines
-to <samp><span class="env">CC</span></samp>.  The description for the <samp><span class="option">munix=</span></samp> option contains
-a list of the predefines used with each standard.
-
-   <p>More specific information to &lsquo;<samp><span class="samp">hppa*-hp-hpux*</span></samp>&rsquo; targets follows.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC14"></a><a name="hppa_002dhp_002dhpux10"></a>hppa*-hp-hpux10</h3>
-
-<p>For hpux10.20, we <em>highly</em> recommend you pick up the latest sed patch
-<code>PHCO_19798</code> from HP.  HP has two sites which provide patches free of
-charge:
-
-     <ul>
-<li><a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
-Latin-America</a><li><a href="http://europe.itrc.hp.com/service/home/home.do">http://europe.itrc.hp.com/service/home/home.do</a> Europe. 
-</ul>
-
-   <p>The C++ ABI has changed incompatibly in GCC 4.0.  COMDAT subspaces are
-used for one-only code and data.  This resolves many of the previous
-problems in using C++ on this target.  However, the ABI is not compatible
-with the one implemented under HP-UX 11 using secondary definitions.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC15"></a><a name="hppa_002dhp_002dhpux11"></a>hppa*-hp-hpux11</h3>
-
-<p>GCC 3.0 and up support HP-UX 11.  GCC 2.95.x is not supported and cannot
-be used to compile GCC 3.0 and up.
-
-   <p>The libffi and libjava libraries haven't been ported to 64-bit HP-UX and don't build.
-
-   <p>Refer to <a href="binaries.html">binaries</a> for information about obtaining
-precompiled GCC binaries for HP-UX.  Precompiled binaries must be obtained
-to build the Ada language as it can't be bootstrapped using C.  Ada is
-only available for the 32-bit PA-RISC runtime.
-
-   <p>Starting with GCC 3.4 an ISO C compiler is required to bootstrap.  The
-bundled compiler supports only traditional C; you will need either HP's
-unbundled compiler, or a binary distribution of GCC.
-
-   <p>It is possible to build GCC 3.3 starting with the bundled HP compiler,
-but the process requires several steps.  GCC 3.3 can then be used to
-build later versions.  The fastjar program contains ISO C code and
-can't be built with the HP bundled compiler.  This problem can be
-avoided by not building the Java language.  For example, use the
-<samp><span class="option">--enable-languages="c,c++,f77,objc"</span></samp> option in your configure
-command.
-
-   <p>There are several possible approaches to building the distribution. 
-Binutils can be built first using the HP tools.  Then, the GCC
-distribution can be built.  The second approach is to build GCC
-first using the HP tools, then build binutils, then rebuild GCC. 
-There have been problems with various binary distributions, so it
-is best not to start from a binary distribution.
-
-   <p>On 64-bit capable systems, there are two distinct targets.  Different
-installation prefixes must be used if both are to be installed on
-the same system.  The &lsquo;<samp><span class="samp">hppa[1-2]*-hp-hpux11*</span></samp>&rsquo; target generates code
-for the 32-bit PA-RISC runtime architecture and uses the HP linker. 
-The &lsquo;<samp><span class="samp">hppa64-hp-hpux11*</span></samp>&rsquo; target generates 64-bit code for the
-PA-RISC 2.0 architecture.
-
-   <p>The script config.guess now selects the target type based on the compiler
-detected during configuration.  You must define <samp><span class="env">PATH</span></samp> or <samp><span class="env">CC</span></samp> so
-that configure finds an appropriate compiler for the initial bootstrap. 
-When <samp><span class="env">CC</span></samp> is used, the definition should contain the options that are
-needed whenever <samp><span class="env">CC</span></samp> is used.
-
-   <p>Specifically, options that determine the runtime architecture must be
-in <samp><span class="env">CC</span></samp> to correctly select the target for the build.  It is also
-convenient to place many other compiler options in <samp><span class="env">CC</span></samp>.  For example,
-<samp><span class="env">CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"</span></samp>
-can be used to bootstrap the GCC 3.3 branch with the HP compiler in
-64-bit K&amp;R/bundled mode.  The <samp><span class="option">+DA2.0W</span></samp> option will result in
-the automatic selection of the &lsquo;<samp><span class="samp">hppa64-hp-hpux11*</span></samp>&rsquo; target.  The
-macro definition table of cpp needs to be increased for a successful
-build with the HP compiler.  _CLASSIC_TYPES and _HPUX_SOURCE need to
-be defined when building with the bundled compiler, or when using the
-<samp><span class="option">-Ac</span></samp> option.  These defines aren't necessary with <samp><span class="option">-Ae</span></samp>.
-
-   <p>It is best to explicitly configure the &lsquo;<samp><span class="samp">hppa64-hp-hpux11*</span></samp>&rsquo; target
-with the <samp><span class="option">--with-ld=...</span></samp> option.  This overrides the standard
-search for ld.  The two linkers supported on this target require different
-commands.  The default linker is determined during configuration.  As a
-result, it's not possible to switch linkers in the middle of a GCC build. 
-This has been reported to sometimes occur in unified builds of binutils
-and GCC.
-
-   <p>A recent linker patch must be installed for the correct operation of
-GCC 3.3 and later.  <code>PHSS_26559</code> and <code>PHSS_24304</code> are the
-oldest linker patches that are known to work.  They are for HP-UX
-11.00 and 11.11, respectively.  <code>PHSS_24303</code>, the companion to
-<code>PHSS_24304</code>, might be usable but it hasn't been tested.  These
-patches have been superseded.  Consult the HP patch database to obtain
-the currently recommended linker patch for your system.
-
-   <p>The patches are necessary for the support of weak symbols on the
-32-bit port, and for the running of initializers and finalizers.  Weak
-symbols are implemented using SOM secondary definition symbols.  Prior
-to HP-UX 11, there are bugs in the linker support for secondary symbols. 
-The patches correct a problem of linker core dumps creating shared
-libraries containing secondary symbols, as well as various other
-linking issues involving secondary symbols.
-
-   <p>GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
-run initializers and finalizers on the 64-bit port.  The 32-bit port
-uses the linker <samp><span class="option">+init</span></samp> and <samp><span class="option">+fini</span></samp> options for the same
-purpose.  The patches correct various problems with the +init/+fini
-options, including program core dumps.  Binutils 2.14 corrects a
-problem on the 64-bit port resulting from HP's non-standard use of
-the .init and .fini sections for array initializers and finalizers.
-
-   <p>Although the HP and GNU linkers are both supported for the
-&lsquo;<samp><span class="samp">hppa64-hp-hpux11*</span></samp>&rsquo; target, it is strongly recommended that the
-HP linker be used for link editing on this target.
-
-   <p>At this time, the GNU linker does not support the creation of long
-branch stubs.  As a result, it can't successfully link binaries
-containing branch offsets larger than 8 megabytes.  In addition,
-there are problems linking shared libraries, linking executables
-with <samp><span class="option">-static</span></samp>, and with dwarf2 unwind and exception support. 
-It also doesn't provide stubs for internal calls to global functions
-in shared libraries, so these calls can't be overloaded.
-
-   <p>The HP dynamic loader does not support GNU symbol versioning, so symbol
-versioning is not supported.  It may be necessary to disable symbol
-versioning with <samp><span class="option">--disable-symvers</span></samp> when using GNU ld.
-
-   <p>POSIX threads are the default.  The optional DCE thread library is not
-supported, so <samp><span class="option">--enable-threads=dce</span></samp> does not work.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC16"></a><a name="x_002dx_002dlinux_002dgnu"></a>*-*-linux-gnu</h3>
-
-<p>Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
-in glibc 2.2.5 and later.  More information is available in the
-libstdc++-v3 documentation.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC17"></a><a name="ix86_002dx_002dlinux"></a>i?86-*-linux*</h3>
-
-<p>As of GCC 3.3, binutils 2.13.1 or later is required for this platform. 
-See <a href="http://gcc.gnu.org/PR10877">bug 10877</a> for more information.
-
-   <p>If you receive Signal 11 errors when building on GNU/Linux, then it is
-possible you have a hardware problem.  Further information on this can be
-found on <a href="http://www.bitwizard.nl/sig11/">www.bitwizard.nl</a>.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC18"></a><a name="ix86_002dx_002dsolaris210"></a>i?86-*-solaris2.10</h3>
-
-<p>Use this for Solaris 10 or later on x86 and x86-64 systems.  This
-configuration is supported by GCC 4.0 and later versions only.
-
-   <p>It is recommended that you configure GCC to use the GNU assembler in
-<samp><span class="file">/usr/sfw/bin/gas</span></samp> but the Sun linker, using the options
-<samp><span class="option">--with-gnu-as --with-as=/usr/sfw/bin/gas --without-gnu-ld
---with-ld=/usr/ccs/bin/ld</span></samp>.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC19"></a><a name="ia64_002dx_002dlinux"></a>ia64-*-linux</h3>
-
-<p>IA-64 processor (also known as IPF, or Itanium Processor Family)
-running GNU/Linux.
-
-   <p>If you are using the installed system libunwind library with
-<samp><span class="option">--with-system-libunwind</span></samp>, then you must use libunwind 0.98 or
-later.
-
-   <p>None of the following versions of GCC has an ABI that is compatible
-with any of the other versions in this list, with the exception that
-Red Hat 2.96 and Trillian 000171 are compatible with each other:
-3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. 
-This primarily affects C++ programs and programs that create shared libraries. 
-GCC 3.1 or later is recommended for compiling linux, the kernel. 
-As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
-more major ABI changes are expected.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC20"></a><a name="ia64_002dx_002dhpux"></a>ia64-*-hpux*</h3>
-
-<p>Building GCC on this target requires the GNU Assembler.  The bundled HP
-assembler will not work.  To prevent GCC from using the wrong assembler,
-the option <samp><span class="option">--with-gnu-as</span></samp> may be necessary.
-
-   <p>The GCC libunwind library has not been ported to HPUX.  This means that for
-GCC versions 3.2.3 and earlier, <samp><span class="option">--enable-libunwind-exceptions</span></samp>
-is required to build GCC.  For GCC 3.3 and later, this is the default. 
-For gcc 3.4.3 and later, <samp><span class="option">--enable-libunwind-exceptions</span></samp> is
-removed and the system libunwind library will always be used.
-
-   <p><hr />
-<!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
-
-<h3 class="heading"><a name="TOC21"></a><a name="x_002dibm_002daix"></a>*-ibm-aix*</h3>
-
-<p>Support for AIX version 3 and older was discontinued in GCC 3.4.
-
-   <p>&ldquo;out of memory&rdquo; bootstrap failures may indicate a problem with
-process resource limits (ulimit).  Hard limits are configured in the
-<samp><span class="file">/etc/security/limits</span></samp> system configuration file.
-
-   <p>To speed up the configuration phases of bootstrapping and installing GCC,
-one may use GNU Bash instead of AIX <samp><span class="command">/bin/sh</span></samp>, e.g.,
-
-<pre class="smallexample">        % CONFIG_SHELL=/opt/freeware/bin/bash
-        % export CONFIG_SHELL
-</pre>
-   <p>and then proceed as described in <a href="build.html">the build instructions</a>, where we strongly recommend specifying an absolute path
-to invoke <var>srcdir</var>/configure.
-
-   <p>Because GCC on AIX is built as a 32-bit executable by default,
-(although it can generate 64-bit programs) the GMP and MPFR libraries
-required by gfortran must be 32-bit libraries.  Building GMP and MPFR
-as static archive libraries works better than shared libraries.
-
-   <p>Errors involving <code>alloca</code> when building GCC generally are due
-to an incorrect definition of <code>CC</code> in the Makefile or mixing files
-compiled with the native C compiler and GCC.  During the stage1 phase of
-the build, the native AIX compiler <strong>must</strong> be invoked as <samp><span class="command">cc</span></samp>
-(not <samp><span class="command">xlc</span></samp>).  Once <samp><span class="command">configure</span></samp> has been informed of
-<samp><span class="command">xlc</span></samp>, one needs to use &lsquo;<samp><span class="samp">make distclean</span></samp>&rsquo; to remove the
-configure cache files and ensure that <samp><span class="env">CC</span></samp> environment variable
-does not provide a definition that will confuse <samp><span class="command">configure</span></samp>. 
-If this error occurs during stage2 or later, then the problem most likely
-is the version of Make (see above).
-
-   <p>The native <samp><span class="command">as</span></samp> and <samp><span class="command">ld</span></samp> are recommended for bootstrapping
-on AIX 4 and required for bootstrapping on AIX 5L.  The GNU Assembler
-reports that it supports WEAK symbols on AIX 4, which causes GCC to try to
-utilize weak symbol functionality although it is not supported.  The GNU
-Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC. 
-The native AIX tools do interoperate with GCC.
-
-   <p>Building <samp><span class="file">libstdc++.a</span></samp> requires a fix for an AIX Assembler bug
-APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1).  It also requires a
-fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
-referenced as APAR IY53606 (AIX 5.2) or a APAR IY54774 (AIX 5.1)
-
-   <p>&lsquo;<samp><span class="samp">libstdc++</span></samp>&rsquo; in GCC 3.4 increments the major version number of the
-shared object and GCC installation places the <samp><span class="file">libstdc++.a</span></samp>
-shared library in a common location which will overwrite the and GCC
-3.3 version of the shared library.  Applications either need to be
-re-linked against the new shared library or the GCC 3.1 and GCC 3.3
-versions of the &lsquo;<samp><span class="samp">libstdc++</span></samp>&rsquo; shared object needs to be available
-to the AIX runtime loader.  The GCC 3.1 &lsquo;<samp><span class="samp">libstdc++.so.4</span></samp>&rsquo;, if
-present, and GCC 3.3 &lsquo;<samp><span class="samp">libstdc++.so.5</span></samp>&rsquo; shared objects can be
-installed for runtime dynamic loading using the following steps to set
-the &lsquo;<samp><span class="samp">F_LOADONLY</span></samp>&rsquo; flag in the shared object for <em>each</em>
-multilib <samp><span class="file">libstdc++.a</span></samp> installed:
-
-   <p>Extract the shared objects from the currently installed
-<samp><span class="file">libstdc++.a</span></samp> archive:
-<pre class="smallexample">        % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
-</pre>
-   <p>Enable the &lsquo;<samp><span class="samp">F_LOADONLY</span></samp>&rsquo; flag so that the shared object will be
-available for runtime dynamic loading, but not linking:
-<pre class="smallexample">        % strip -e libstdc++.so.4 libstdc++.so.5
-</pre>
-   <p>Archive the runtime-only shared object in the GCC 3.4
-<samp><span class="file">libstdc++.a</span></samp> archive:
-<pre class="smallexample">        % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
-</pre>
-   <p>Linking executables and shared libraries may produce warnings of
-duplicate symbols.  The assembly files generated by GCC for AIX always
-have included multiple symbol definitions for certain global variable
-and function declarations in the original program.  The warnings should
-not prevent the linker from producing a correct library or runnable
-executable.
-
-   <p>AIX 4.3 utilizes a &ldquo;large format&rdquo; archive to support both 32-bit and
-64-bit object modules.  The routines provided in AIX 4.3.0 and AIX 4.3.1
-to parse archive libraries did not handle the new format correctly. 
-These routines are used by GCC and result in error messages during
-linking such as &ldquo;not a COFF file&rdquo;.  The version of the routines shipped
-with AIX 4.3.1 should work for a 32-bit environment.  The <samp><span class="option">-g</span></samp>
-option of the archive command may be used to create archives of 32-bit
-objects using the original &ldquo;small format&rdquo;.  A correct version of the
-routines is shipped with AIX 4.3.2 and above.
-
-   <p>Some versions of the AIX binder (linker) can fail with a relocation
-overflow severe error when the <samp><span class="option">-bbigtoc</span></samp> option is used to link
-GCC-produced object files into an executable that overflows the TOC.  A fix
-for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
-available from IBM Customer Support and from its
-<a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
-website as PTF U455193.
-
-   <p>The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
-with a segmentation fault when invoked by any version of GCC.  A fix for
-APAR IX87327 is available from IBM Customer Support and from its
-<a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
-website as PTF U461879.  This fix is incorporated in AIX 4.3.3 and above.
-
-   <p>The initial assembler shipped with AIX 4.3.0 generates incorrect object
-files.  A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
-TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
-<a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
-website as PTF U453956.  This fix is incorporated in AIX 4.3.1 and above.
-
-   <p>AIX provides National Language Support (NLS).  Compilers and assemblers
-use NLS to support locale-specific representations of various data
-formats including floating-point numbers (e.g., &lsquo;<samp><span class="samp">.</span></samp>&rsquo;  vs &lsquo;<samp><span class="samp">,</span></samp>&rsquo; for
-separating decimal fractions).  There have been problems reported where
-GCC does not produce the same floating-point formats that the assembler
-expects.  If one encounters this problem, set the <samp><span class="env">LANG</span></samp>
-environment variable to &lsquo;<samp><span class="samp">C</span></samp>&rsquo; or &lsquo;<samp><span class="samp">En_US</span></samp>&rsquo;.
-
-   <p>By default, GCC for AIX 4.1 and above produces code that can be used on
-both Power or PowerPC processors.
-
-   <p>A default can be specified with the <samp><span class="option">-mcpu=</span><var>cpu_type</var></samp>
-switch and using the configure option <samp><span class="option">--with-cpu-</span><var>cpu_type</var></samp>.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC22"></a><a name="iq2000_002dx_002delf"></a>iq2000-*-elf</h3>
-
-<p>Vitesse IQ2000 processors.  These are used in embedded
-applications.  There are no standard Unix configurations.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC23"></a><a name="m32c_002dx_002delf"></a>m32c-*-elf</h3>
-
-<p>Renesas M32C processor. 
-This configuration is intended for embedded systems.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC24"></a><a name="m32r_002dx_002delf"></a>m32r-*-elf</h3>
-
-<p>Renesas M32R processor. 
-This configuration is intended for embedded systems.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC25"></a><a name="m6811_002delf"></a>m6811-elf</h3>
-
-<p>Motorola 68HC11 family micro controllers.  These are used in embedded
-applications.  There are no standard Unix configurations.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC26"></a><a name="m6812_002delf"></a>m6812-elf</h3>
-
-<p>Motorola 68HC12 family micro controllers.  These are used in embedded
-applications.  There are no standard Unix configurations.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC27"></a><a name="m68k_002dx_002dx"></a>m68k-*-*</h3>
-
-<p>By default, &lsquo;<samp><span class="samp">m68k-*-aout</span></samp>&rsquo;, &lsquo;<samp><span class="samp">m68k-*-coff*</span></samp>&rsquo;,
-&lsquo;<samp><span class="samp">m68k-*-elf*</span></samp>&rsquo;, &lsquo;<samp><span class="samp">m68k-*-rtems</span></samp>&rsquo;,  &lsquo;<samp><span class="samp">m68k-*-uclinux</span></samp>&rsquo; and
-&lsquo;<samp><span class="samp">m68k-*-linux</span></samp>&rsquo;
-build libraries for both M680x0 and ColdFire processors.  If you only
-need the M680x0 libraries, you can omit the ColdFire ones by passing
-<samp><span class="option">--with-arch=m68k</span></samp> to <samp><span class="command">configure</span></samp>.  Alternatively, you
-can omit the M680x0 libraries by passing <samp><span class="option">--with-arch=cf</span></samp> to
-<samp><span class="command">configure</span></samp>.  These targets default to 5206 or 5475 code as
-appropriate for the target system when
-configured with <samp><span class="option">--with-arch=cf</span></samp> and 68020 code otherwise.
-
-   <p>The &lsquo;<samp><span class="samp">m68k-*-netbsd</span></samp>&rsquo; and
-&lsquo;<samp><span class="samp">m68k-*-openbsd</span></samp>&rsquo; targets also support the <samp><span class="option">--with-arch</span></samp>
-option.  They will generate ColdFire CFV4e code when configured with
-<samp><span class="option">--with-arch=cf</span></samp> and 68020 code otherwise.
-
-   <p>You can override the default processors listed above by configuring
-with <samp><span class="option">--with-cpu=</span><var>target</var></samp>.  This <var>target</var> can either
-be a <samp><span class="option">-mcpu</span></samp> argument or one of the following values:
-&lsquo;<samp><span class="samp">m68000</span></samp>&rsquo;, &lsquo;<samp><span class="samp">m68010</span></samp>&rsquo;, &lsquo;<samp><span class="samp">m68020</span></samp>&rsquo;, &lsquo;<samp><span class="samp">m68030</span></samp>&rsquo;,
-&lsquo;<samp><span class="samp">m68040</span></samp>&rsquo;, &lsquo;<samp><span class="samp">m68060</span></samp>&rsquo;, &lsquo;<samp><span class="samp">m68020-40</span></samp>&rsquo; and &lsquo;<samp><span class="samp">m68020-60</span></samp>&rsquo;.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC28"></a><a name="m68k_002dx_002duclinux"></a>m68k-*-uclinux</h3>
-
-<p>GCC 4.3 changed the uClinux configuration so that it uses the
-&lsquo;<samp><span class="samp">m68k-linux-gnu</span></samp>&rsquo; ABI rather than the &lsquo;<samp><span class="samp">m68k-elf</span></samp>&rsquo; ABI. 
-It also added improved support for C++ and flat shared libraries,
-both of which were ABI changes.  However, you can still use the
-original ABI by configuring for &lsquo;<samp><span class="samp">m68k-uclinuxoldabi</span></samp>&rsquo; or
-&lsquo;<samp><span class="samp">m68k-</span><var>vendor</var><span class="samp">-uclinuxoldabi</span></samp>&rsquo;.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC29"></a><a name="mips_002dx_002dx"></a>mips-*-*</h3>
-
-<p>If on a MIPS system you get an error message saying &ldquo;does not have gp
-sections for all it's [sic] sectons [sic]&rdquo;, don't worry about it.  This
-happens whenever you use GAS with the MIPS linker, but there is not
-really anything wrong, and it is okay to use the output file.  You can
-stop such warnings by installing the GNU linker.
-
-   <p>It would be nice to extend GAS to produce the gp tables, but they are
-optional, and there should not be a warning about their absence.
-
-   <p>The libstdc++ atomic locking routines for MIPS targets requires MIPS II
-and later.  A patch went in just after the GCC 3.3 release to
-make &lsquo;<samp><span class="samp">mips*-*-*</span></samp>&rsquo; use the generic implementation instead.  You can also
-configure for &lsquo;<samp><span class="samp">mipsel-elf</span></samp>&rsquo; as a workaround.  The
-&lsquo;<samp><span class="samp">mips*-*-linux*</span></samp>&rsquo; target continues to use the MIPS II routines.  More
-work on this is expected in future releases.
-
-<!-- If you make -with-llsc the default for another target, please also -->
-<!-- update the description of the -with-llsc option. -->
-   <p>The built-in <code>__sync_*</code> functions are available on MIPS II and
-later systems and others that support the &lsquo;<samp><span class="samp">ll</span></samp>&rsquo;, &lsquo;<samp><span class="samp">sc</span></samp>&rsquo; and
-&lsquo;<samp><span class="samp">sync</span></samp>&rsquo; instructions.  This can be overridden by passing
-<samp><span class="option">--with-llsc</span></samp> or <samp><span class="option">--without-llsc</span></samp> when configuring GCC. 
-Since the Linux kernel emulates these instructions if they are
-missing, the default for &lsquo;<samp><span class="samp">mips*-*-linux*</span></samp>&rsquo; targets is
-<samp><span class="option">--with-llsc</span></samp>.  The <samp><span class="option">--with-llsc</span></samp> and
-<samp><span class="option">--without-llsc</span></samp> configure options may be overridden at compile
-time by passing the <samp><span class="option">-mllsc</span></samp> or <samp><span class="option">-mno-llsc</span></samp> options to
-the compiler.
-
-   <p>MIPS systems check for division by zero (unless
-<samp><span class="option">-mno-check-zero-division</span></samp> is passed to the compiler) by
-generating either a conditional trap or a break instruction.  Using
-trap results in smaller code, but is only supported on MIPS II and
-later.  Also, some versions of the Linux kernel have a bug that
-prevents trap from generating the proper signal (<code>SIGFPE</code>).  To enable
-the use of break, use the <samp><span class="option">--with-divide=breaks</span></samp>
-<samp><span class="command">configure</span></samp> option when configuring GCC.  The default is to
-use traps on systems that support them.
-
-   <p>Cross-compilers for the MIPS as target using the MIPS assembler
-currently do not work, because the auxiliary programs
-<samp><span class="file">mips-tdump.c</span></samp> and <samp><span class="file">mips-tfile.c</span></samp> can't be compiled on
-anything but a MIPS.  It does work to cross compile for a MIPS
-if you use the GNU assembler and linker.
-
-   <p>The assembler from GNU binutils 2.17 and earlier has a bug in the way
-it sorts relocations for REL targets (o32, o64, EABI).  This can cause
-bad code to be generated for simple C++ programs.  Also the linker
-from GNU binutils versions prior to 2.17 has a bug which causes the
-runtime linker stubs in very large programs, like <samp><span class="file">libgcj.so</span></samp>, to
-be incorrectly generated.  GNU Binutils 2.18 and later (and snapshots
-made after Nov. 9, 2006) should be free from both of these problems.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC30"></a><a name="mips_002dsgi_002dirix5"></a>mips-sgi-irix5</h3>
-
-<p>In order to compile GCC on an SGI running IRIX 5, the &lsquo;<samp><span class="samp">compiler_dev.hdr</span></samp>&rsquo;
-subsystem must be installed from the IDO CD-ROM supplied by SGI. 
-It is also available for download from
-<a href="ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist">ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist</a>.
-
-   <p>If you use the MIPS C compiler to bootstrap, it may be necessary
-to increase its table size for switch statements with the
-<samp><span class="option">-Wf,-XNg1500</span></samp> option.  If you use the <samp><span class="option">-O2</span></samp>
-optimization option, you also need to use <samp><span class="option">-Olimit 3000</span></samp>.
-
-   <p>To enable debugging under IRIX 5, you must use GNU binutils 2.15 or
-later, and use the <samp><span class="option">--with-gnu-ld</span></samp> <samp><span class="command">configure</span></samp> option
-when configuring GCC.  You need to use GNU <samp><span class="command">ar</span></samp> and <samp><span class="command">nm</span></samp>,
-also distributed with GNU binutils.
-
-   <p>Some users have reported that <samp><span class="command">/bin/sh</span></samp> will hang during bootstrap. 
-This problem can be avoided by running the commands:
-
-<pre class="smallexample">        % CONFIG_SHELL=/bin/ksh
-        % export CONFIG_SHELL
-</pre>
-   <p>before starting the build.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC31"></a><a name="mips_002dsgi_002dirix6"></a>mips-sgi-irix6</h3>
-
-<p>If you are using SGI's MIPSpro <samp><span class="command">cc</span></samp> as your bootstrap compiler, you must
-ensure that the N32 ABI is in use.  To test this, compile a simple C
-file with <samp><span class="command">cc</span></samp> and then run <samp><span class="command">file</span></samp> on the
-resulting object file.  The output should look like:
-
-<pre class="smallexample">     test.o: ELF N32 MSB ...
-</pre>
-   <p>If you see:
-
-<pre class="smallexample">     test.o: ELF 32-bit MSB ...
-</pre>
-   <p>or
-
-<pre class="smallexample">     test.o: ELF 64-bit MSB ...
-</pre>
-   <p>then your version of <samp><span class="command">cc</span></samp> uses the O32 or N64 ABI by default.  You
-should set the environment variable <samp><span class="env">CC</span></samp> to &lsquo;<samp><span class="samp">cc -n32</span></samp>&rsquo;
-before configuring GCC.
-
-   <p>If you want the resulting <samp><span class="command">gcc</span></samp> to run on old 32-bit systems
-with the MIPS R4400 CPU, you need to ensure that only code for the &lsquo;<samp><span class="samp">mips3</span></samp>&rsquo;
-instruction set architecture (ISA) is generated.  While GCC 3.x does
-this correctly, both GCC 2.95 and SGI's MIPSpro <samp><span class="command">cc</span></samp> may change
-the ISA depending on the machine where GCC is built.  Using one of them
-as the bootstrap compiler may result in &lsquo;<samp><span class="samp">mips4</span></samp>&rsquo; code, which won't run at
-all on &lsquo;<samp><span class="samp">mips3</span></samp>&rsquo;-only systems.  For the test program above, you should see:
-
-<pre class="smallexample">     test.o: ELF N32 MSB mips-3 ...
-</pre>
-   <p>If you get:
-
-<pre class="smallexample">     test.o: ELF N32 MSB mips-4 ...
-</pre>
-   <p>instead, you should set the environment variable <samp><span class="env">CC</span></samp> to &lsquo;<samp><span class="samp">cc
--n32 -mips3</span></samp>&rsquo; or &lsquo;<samp><span class="samp">gcc -mips3</span></samp>&rsquo; respectively before configuring GCC.
-
-   <p>MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
-<code>memcmp</code>.  Either add <code>-U__INLINE_INTRINSICS</code> to the <samp><span class="env">CC</span></samp>
-environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
-
-   <p>GCC on IRIX 6 is usually built to support the N32, O32 and N64 ABIs.  If
-you build GCC on a system that doesn't have the N64 libraries installed
-or cannot run 64-bit binaries,
-you need to configure with <samp><span class="option">--disable-multilib</span></samp> so GCC doesn't
-try to use them.  This will disable building the O32 libraries, too. 
-Look for <samp><span class="file">/usr/lib64/libc.so.1</span></samp> to see if you
-have the 64-bit libraries installed.
-
-   <p>To enable debugging for the O32 ABI, you must use GNU <samp><span class="command">as</span></samp> from
-GNU binutils 2.15 or later.  You may also use GNU <samp><span class="command">ld</span></samp>, but
-this is not required and currently causes some problems with Ada.
-
-   <p>The <samp><span class="option">--enable-libgcj</span></samp>
-option is disabled by default: IRIX 6 uses a very low default limit
-(20480) for the command line length.  Although <samp><span class="command">libtool</span></samp> contains a
-workaround for this problem, at least the N64 &lsquo;<samp><span class="samp">libgcj</span></samp>&rsquo; is known not
-to build despite this, running into an internal error of the native
-<samp><span class="command">ld</span></samp>.  A sure fix is to increase this limit (&lsquo;<samp><span class="samp">ncargs</span></samp>&rsquo;) to
-its maximum of 262144 bytes.  If you have root access, you can use the
-<samp><span class="command">systune</span></samp> command to do this.
-
-   <p><code>wchar_t</code> support in &lsquo;<samp><span class="samp">libstdc++</span></samp>&rsquo; is not available for old
-IRIX 6.5.x releases, x &lt; 19.  The problem cannot be autodetected
-and in order to build GCC for such targets you need to configure with
-<samp><span class="option">--disable-wchar_t</span></samp>.
-
-   <p>See <a href="http://freeware.sgi.com/">http://freeware.sgi.com/</a> for more
-information about using GCC on IRIX platforms.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC32"></a><a name="powerpc_002dx_002dx"></a>powerpc-*-*</h3>
-
-<p>You can specify a default version for the <samp><span class="option">-mcpu=</span><var>cpu_type</var></samp>
-switch by using the configure option <samp><span class="option">--with-cpu-</span><var>cpu_type</var></samp>.
-
-   <p>You will need
-<a href="ftp://ftp.kernel.org/pub/linux/devel/binutils">binutils 2.15</a>
-or newer for a working GCC.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC33"></a><a name="powerpc_002dx_002ddarwin"></a>powerpc-*-darwin*</h3>
-
-<p>PowerPC running Darwin (Mac OS X kernel).
-
-   <p>Pre-installed versions of Mac OS X may not include any developer tools,
-meaning that you will not be able to build GCC from source.  Tool
-binaries are available at
-<a href="http://developer.apple.com/darwin/projects/compiler/">http://developer.apple.com/darwin/projects/compiler/</a> (free
-registration required).
-
-   <p>This version of GCC requires at least cctools-590.36.  The
-cctools-590.36 package referenced from
-<a href="http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html">http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html</a> will not work
-on systems older than 10.3.9 (aka darwin7.9.0).
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC34"></a><a name="powerpc_002dx_002delf"></a>powerpc-*-elf</h3>
-
-<p>PowerPC system in big endian mode, running System V.4.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC35"></a><a name="powerpc_002dx_002dlinux_002dgnu"></a>powerpc*-*-linux-gnu*</h3>
-
-<p>PowerPC system in big endian mode running Linux.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC36"></a><a name="powerpc_002dx_002dnetbsd"></a>powerpc-*-netbsd*</h3>
-
-<p>PowerPC system in big endian mode running NetBSD.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC37"></a><a name="powerpc_002dx_002deabisim"></a>powerpc-*-eabisim</h3>
-
-<p>Embedded PowerPC system in big endian mode for use in running under the
-PSIM simulator.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC38"></a><a name="powerpc_002dx_002deabi"></a>powerpc-*-eabi</h3>
-
-<p>Embedded PowerPC system in big endian mode.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC39"></a><a name="powerpcle_002dx_002delf"></a>powerpcle-*-elf</h3>
-
-<p>PowerPC system in little endian mode, running System V.4.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC40"></a><a name="powerpcle_002dx_002deabisim"></a>powerpcle-*-eabisim</h3>
-
-<p>Embedded PowerPC system in little endian mode for use in running under
-the PSIM simulator.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC41"></a><a name="powerpcle_002dx_002deabi"></a>powerpcle-*-eabi</h3>
-
-<p>Embedded PowerPC system in little endian mode.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC42"></a><a name="s390_002dx_002dlinux"></a>s390-*-linux*</h3>
-
-<p>S/390 system running GNU/Linux for S/390.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC43"></a><a name="s390x_002dx_002dlinux"></a>s390x-*-linux*</h3>
-
-<p>zSeries system (64-bit) running GNU/Linux for zSeries.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC44"></a><a name="s390x_002dibm_002dtpf"></a>s390x-ibm-tpf*</h3>
-
-<p>zSeries system (64-bit) running TPF.  This platform is
-supported as cross-compilation target only.
-
-   <p><hr /><!-- Please use Solaris 2 to refer to all release of Solaris, starting -->
-<!-- with 2.0 until 2.6, 7, 8, etc.  Solaris 1 was a marketing name for -->
-<!-- SunOS 4 releases which we don't use to avoid confusion.  Solaris -->
-<!-- alone is too unspecific and must be avoided. -->
-
-<h3 class="heading"><a name="TOC45"></a><a name="x_002dx_002dsolaris2"></a>*-*-solaris2*</h3>
-
-<p>Sun does not ship a C compiler with Solaris 2.  To bootstrap and install
-GCC you first have to install a pre-built compiler, see the
-<a href="binaries.html">binaries page</a> for details.
-
-   <p>The Solaris 2 <samp><span class="command">/bin/sh</span></samp> will often fail to configure
-<samp><span class="file">libstdc++-v3</span></samp>, <samp><span class="file">boehm-gc</span></samp> or <samp><span class="file">libjava</span></samp>.  We therefore
-recommend using the following initial sequence of commands
-
-<pre class="smallexample">        % CONFIG_SHELL=/bin/ksh
-        % export CONFIG_SHELL
-</pre>
-   <p>and proceed as described in <a href="configure.html">the configure instructions</a>. 
-In addition we strongly recommend specifying an absolute path to invoke
-<var>srcdir</var>/configure.
-
-   <p>Solaris 2 comes with a number of optional OS packages.  Some of these
-are needed to use GCC fully, namely <code>SUNWarc</code>,
-<code>SUNWbtool</code>, <code>SUNWesu</code>, <code>SUNWhea</code>, <code>SUNWlibm</code>,
-<code>SUNWsprot</code>, and <code>SUNWtoo</code>.  If you did not install all
-optional packages when installing Solaris 2, you will need to verify that
-the packages that GCC needs are installed.
-
-   <p>To check whether an optional package is installed, use
-the <samp><span class="command">pkginfo</span></samp> command.  To add an optional package, use the
-<samp><span class="command">pkgadd</span></samp> command.  For further details, see the Solaris 2
-documentation.
-
-   <p>Trying to use the linker and other tools in
-<samp><span class="file">/usr/ucb</span></samp> to install GCC has been observed to cause trouble. 
-For example, the linker may hang indefinitely.  The fix is to remove
-<samp><span class="file">/usr/ucb</span></samp> from your <samp><span class="env">PATH</span></samp>.
-
-   <p>The build process works more smoothly with the legacy Sun tools so, if you
-have <samp><span class="file">/usr/xpg4/bin</span></samp> in your <samp><span class="env">PATH</span></samp>, we recommend that you place
-<samp><span class="file">/usr/bin</span></samp> before <samp><span class="file">/usr/xpg4/bin</span></samp> for the duration of the build.
-
-   <p>We recommend the use of GNU binutils 2.14 or later, or the vendor tools
-(Sun <samp><span class="command">as</span></samp>, Sun <samp><span class="command">ld</span></samp>).  Note that your mileage may vary
-if you use a combination of the GNU tools and the Sun tools: while the
-combination GNU <samp><span class="command">as</span></samp> + Sun <samp><span class="command">ld</span></samp> should reasonably work,
-the reverse combination Sun <samp><span class="command">as</span></samp> + GNU <samp><span class="command">ld</span></samp> is known to
-cause memory corruption at runtime in some cases for C++ programs.
-
-   <p>The stock GNU binutils 2.15 release is broken on this platform because of a
-single bug.  It has been fixed on the 2.15 branch in the CVS repository. 
-You can obtain a working version by checking out the binutils-2_15-branch
-from the CVS repository or applying the patch
-<a href="http://sourceware.org/ml/binutils-cvs/2004-09/msg00036.html">http://sourceware.org/ml/binutils-cvs/2004-09/msg00036.html</a> to the
-release.
-
-   <p>We recommend the use of GNU binutils 2.16 or later in conjunction with GCC
-4.x, or the vendor tools (Sun <samp><span class="command">as</span></samp>, Sun <samp><span class="command">ld</span></samp>).  However,
-for Solaris 10 and above, an additional patch is required in order for the
-GNU linker to be able to cope with a new flavor of shared libraries.  You
-can obtain a working version by checking out the binutils-2_16-branch from
-the CVS repository or applying the patch
-<a href="http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html">http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html</a> to the
-release.
-
-   <p>Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
-newer: <samp><span class="command">g++</span></samp> will complain that types are missing.  These headers
-assume that omitting the type means <code>int</code>; this assumption worked for
-C89 but is wrong for C++, and is now wrong for C99 also.
-
-   <p><samp><span class="command">g++</span></samp> accepts such (invalid) constructs with the option
-<samp><span class="option">-fpermissive</span></samp>; it will assume that any missing type is <code>int</code>
-(as defined by C89).
-
-   <p>There are patches for Solaris 7 (108376-21 or newer for SPARC,
-108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC,
-108653-22 for Intel) that fix this bug.
-
-   <p>Sun bug 4927647 sometimes causes random spurious testsuite failures
-related to missing diagnostic output.  This bug doesn't affect GCC
-itself, rather it is a kernel bug triggered by the <samp><span class="command">expect</span></samp>
-program which is used only by the GCC testsuite driver.  When the bug
-causes the <samp><span class="command">expect</span></samp> program to miss anticipated output, extra
-testsuite failures appear.
-
-   <p>There are patches for Solaris 8 (117350-12 or newer for SPARC,
-117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
-SPARC, 117172-11 or newer for Intel) that address this problem.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC46"></a><a name="sparc_002dsun_002dsolaris2"></a>sparc-sun-solaris2*</h3>
-
-<p>When GCC is configured to use binutils 2.14 or later the binaries
-produced are smaller than the ones produced using Sun's native tools;
-this difference is quite significant for binaries containing debugging
-information.
-
-   <p>Starting with Solaris 7, the operating system is capable of executing
-64-bit SPARC V9 binaries.  GCC 3.1 and later properly supports
-this; the <samp><span class="option">-m64</span></samp> option enables 64-bit code generation. 
-However, if all you want is code tuned for the UltraSPARC CPU, you
-should try the <samp><span class="option">-mtune=ultrasparc</span></samp> option instead, which produces
-code that, unlike full 64-bit code, can still run on non-UltraSPARC
-machines.
-
-   <p>When configuring on a Solaris 7 or later system that is running a kernel
-that supports only 32-bit binaries, one must configure with
-<samp><span class="option">--disable-multilib</span></samp>, since we will not be able to build the
-64-bit target libraries.
-
-   <p>GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
-the GNU compiler (especially GCC 3.0.x versions), which lead to the
-miscompilation of the stage1 compiler and the subsequent failure of the
-bootstrap process.  A workaround is to use GCC 3.2.3 as an intermediary
-stage, i.e. to bootstrap that compiler with the base compiler and then
-use it to bootstrap the final compiler.
-
-   <p>GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
-and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
-failure in form of a miscompilation of the stage1 compiler by the Sun
-compiler.  This is Sun bug 4974440.  This is fixed with patch 112760-07.
-
-   <p>GCC 3.4 changed the default debugging format from STABS to DWARF-2 for
-32-bit code on Solaris 7 and later.  If you use the Sun assembler, this
-change apparently runs afoul of Sun bug 4910101 (which is referenced as
-a x86-only problem by Sun, probably because they do not use DWARF-2). 
-A symptom of the problem is that you cannot compile C++ programs like
-<samp><span class="command">groff</span></samp> 1.19.1 without getting messages similar to the following:
-
-<pre class="smallexample">     ld: warning: relocation error: R_SPARC_UA32: ...
-       external symbolic relocation against non-allocatable section
-       .debug_info cannot be processed at runtime: relocation ignored.
-</pre>
-   <p>To work around this problem, compile with <samp><span class="option">-gstabs+</span></samp> instead of
-plain <samp><span class="option">-g</span></samp>.
-
-   <p>When configuring the GNU Multiple Precision Library (GMP) or the MPFR
-library on a Solaris 7 or later system, the canonical target triplet
-must be specified as the <samp><span class="command">build</span></samp> parameter on the configure
-line.  This triplet can be obtained by invoking ./config.guess in
-the toplevel source directory of GCC (and not that of GMP or MPFR). 
-For example on a Solaris 7 system:
-
-<pre class="smallexample">        % ./configure --build=sparc-sun-solaris2.7 --prefix=xxx
-</pre>
-   <p><hr />
-
-<h3 class="heading"><a name="TOC47"></a><a name="sparc_002dsun_002dsolaris27"></a>sparc-sun-solaris2.7</h3>
-
-<p>Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in
-the dynamic linker.  This problem (Sun bug 4210064) affects GCC 2.8
-and later, including all EGCS releases.  Sun formerly recommended
-107058-01 for all Solaris 7 users, but around 1999-09-01 it started to
-recommend it only for people who use Sun's compilers.
-
-   <p>Here are some workarounds to this problem:
-     <ul>
-<li>Do not install Sun patch 107058-01 until after Sun releases a
-complete patch for bug 4210064.  This is the simplest course to take,
-unless you must also use Sun's C compiler.  Unfortunately 107058-01
-is preinstalled on some new Solaris 7-based hosts, so you may have to
-back it out.
-
-     <li>Copy the original, unpatched Solaris 7
-<samp><span class="command">/usr/ccs/bin/as</span></samp> into
-<samp><span class="command">/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as</span></samp>,
-adjusting the latter name to fit your local conventions and software
-version numbers.
-
-     <li>Install Sun patch 106950-03 (1999-05-25) or later.  Nobody with
-both 107058-01 and 106950-03 installed has reported the bug with GCC
-and Sun's dynamic linker.  This last course of action is riskiest,
-for two reasons.  First, you must install 106950 on all hosts that
-run code generated by GCC; it doesn't suffice to install it only on
-the hosts that run GCC itself.  Second, Sun says that 106950-03 is
-only a partial fix for bug 4210064, but Sun doesn't know whether the
-partial fix is adequate for GCC.  Revision -08 or later should fix
-the bug.  The current (as of 2004-05-23) revision is -24, and is included in
-the Solaris 7 Recommended Patch Cluster. 
-</ul>
-
-   <p>GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler,
-which causes a bootstrap failure when linking the 64-bit shared version of
-libgcc.  A typical error message is:
-
-<pre class="smallexample">     ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
-       symbol &lt;unknown&gt;:  offset 0xffffffff7ec133e7 is non-aligned.
-</pre>
-   <p>This bug has been fixed in the final 5.0 version of the assembler.
-
-   <p>A similar problem was reported for version Sun WorkShop 6 99/08/18 of the
-Sun assembler, which causes a bootstrap failure with GCC 4.0.0:
-
-<pre class="smallexample">     ld: fatal: relocation error: R_SPARC_DISP32:
-       file .libs/libstdc++.lax/libsupc++convenience.a/vterminate.o:
-         symbol &lt;unknown&gt;: offset 0xfccd33ad is non-aligned
-</pre>
-   <p>This bug has been fixed in more recent revisions of the assembler.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC48"></a><a name="sparc_002dx_002dlinux"></a>sparc-*-linux*</h3>
-
-<p>GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
-or newer on this platform.  All earlier binutils and glibc
-releases mishandled unaligned relocations on <code>sparc-*-*</code> targets.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC49"></a><a name="sparc64_002dx_002dsolaris2"></a>sparc64-*-solaris2*</h3>
-
-<p>When configuring the GNU Multiple Precision Library (GMP) or the
-MPFR library, the canonical target triplet must be specified as
-the <samp><span class="command">build</span></samp> parameter on the configure line.  For example
-on a Solaris 7 system:
-
-<pre class="smallexample">        % ./configure --build=sparc64-sun-solaris2.7 --prefix=xxx
-</pre>
-   <p>The following compiler flags must be specified in the configure
-step in order to bootstrap this target with the Sun compiler:
-
-<pre class="smallexample">        % CC="cc -xarch=v9 -xildoff" <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
-</pre>
-   <p><samp><span class="option">-xarch=v9</span></samp> specifies the SPARC-V9 architecture to the Sun toolchain
-and <samp><span class="option">-xildoff</span></samp> turns off the incremental linker.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC50"></a><a name="sparcv9_002dx_002dsolaris2"></a>sparcv9-*-solaris2*</h3>
-
-<p>This is a synonym for sparc64-*-solaris2*.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC51"></a><a name="x_002dx_002dvxworks"></a>*-*-vxworks*</h3>
-
-<p>Support for VxWorks is in flux.  At present GCC supports <em>only</em> the
-very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC. 
-We welcome patches for other architectures supported by VxWorks 5.5. 
-Support for VxWorks AE would also be welcome; we believe this is merely
-a matter of writing an appropriate &ldquo;configlette&rdquo; (see below).  We are
-not interested in supporting older, a.out or COFF-based, versions of
-VxWorks in GCC 3.
-
-   <p>VxWorks comes with an older version of GCC installed in
-<samp><var>$WIND_BASE</var><span class="file">/host</span></samp>; we recommend you do not overwrite it. 
-Choose an installation <var>prefix</var> entirely outside <var>$WIND_BASE</var>. 
-Before running <samp><span class="command">configure</span></samp>, create the directories <samp><var>prefix</var></samp>
-and <samp><var>prefix</var><span class="file">/bin</span></samp>.  Link or copy the appropriate assembler,
-linker, etc. into <samp><var>prefix</var><span class="file">/bin</span></samp>, and set your <var>PATH</var> to
-include that directory while running both <samp><span class="command">configure</span></samp> and
-<samp><span class="command">make</span></samp>.
-
-   <p>You must give <samp><span class="command">configure</span></samp> the
-<samp><span class="option">--with-headers=</span><var>$WIND_BASE</var><span class="option">/target/h</span></samp> switch so that it can
-find the VxWorks system headers.  Since VxWorks is a cross compilation
-target only, you must also specify <samp><span class="option">--target=</span><var>target</var></samp>. 
-<samp><span class="command">configure</span></samp> will attempt to create the directory
-<samp><var>prefix</var><span class="file">/</span><var>target</var><span class="file">/sys-include</span></samp> and copy files into it;
-make sure the user running <samp><span class="command">configure</span></samp> has sufficient privilege
-to do so.
-
-   <p>GCC's exception handling runtime requires a special &ldquo;configlette&rdquo;
-module, <samp><span class="file">contrib/gthr_supp_vxw_5x.c</span></samp>.  Follow the instructions in
-that file to add the module to your kernel build.  (Future versions of
-VxWorks will incorporate this module.)
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC52"></a><a name="x86_002d64_002dx_002dx"></a>x86_64-*-*, amd64-*-*</h3>
-
-<p>GCC supports the x86-64 architecture implemented by the AMD64 processor
-(amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD. 
-On GNU/Linux the default is a bi-arch compiler which is able to generate
-both 64-bit x86-64 and 32-bit x86 code (via the <samp><span class="option">-m32</span></samp> switch).
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC53"></a><a name="xtensa_002dx_002delf"></a>xtensa*-*-elf</h3>
-
-<p>This target is intended for embedded Xtensa systems using the
-&lsquo;<samp><span class="samp">newlib</span></samp>&rsquo; C library.  It uses ELF but does not support shared
-objects.  Designed-defined instructions specified via the
-Tensilica Instruction Extension (TIE) language are only supported
-through inline assembly.
-
-   <p>The Xtensa configuration information must be specified prior to
-building GCC.  The <samp><span class="file">include/xtensa-config.h</span></samp> header
-file contains the configuration information.  If you created your
-own Xtensa configuration with the Xtensa Processor Generator, the
-downloaded files include a customized copy of this header file,
-which you can use to replace the default header file.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC54"></a><a name="xtensa_002dx_002dlinux"></a>xtensa*-*-linux*</h3>
-
-<p>This target is for Xtensa systems running GNU/Linux.  It supports ELF
-shared objects and the GNU C library (glibc).  It also generates
-position-independent code (PIC) regardless of whether the
-<samp><span class="option">-fpic</span></samp> or <samp><span class="option">-fPIC</span></samp> options are used.  In other
-respects, this target is the same as the
-<a href="#xtensa*-*-elf">&lsquo;<samp><span class="samp">xtensa*-*-elf</span></samp>&rsquo;</a> target.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC55"></a><a name="windows"></a>Microsoft Windows</h3>
-
-<h4 class="subheading"><a name="TOC56"></a>Intel 16-bit versions</h4>
-
-<p>The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
-supported.
-
-   <p>However, the 32-bit port has limited support for Microsoft
-Windows 3.11 in the Win32s environment, as a target only.  See below.
-
-<h4 class="subheading"><a name="TOC57"></a>Intel 32-bit versions</h4>
-
-<p>The 32-bit versions of Windows, including Windows 95, Windows NT, Windows
-XP, and Windows Vista, are supported by several different target
-platforms.  These targets differ in which Windows subsystem they target
-and which C libraries are used.
-
-     <ul>
-<li>Cygwin <a href="#x-x-cygwin">*-*-cygwin</a>: Cygwin provides a user-space
-Linux API emulation layer in the Win32 subsystem. 
-<li>Interix <a href="#x-x-interix">*-*-interix</a>: The Interix subsystem
-provides native support for POSIX. 
-<li>MinGW <a href="#x-x-mingw">*-*-mingw</a>: MinGW is a native GCC port for
-the Win32 subsystem that provides a subset of POSIX. 
-<li>MKS i386-pc-mks: NuTCracker from MKS.  See
-<a href="http://www.mkssoftware.com/">http://www.mkssoftware.com/</a> for more information. 
-</ul>
-
-<h4 class="subheading"><a name="TOC58"></a>Intel 64-bit versions</h4>
-
-<p>GCC contains support for x86-64 using the mingw-w64
-runtime library, available from <a href="http://mingw-w64.sourceforge.net/">http://mingw-w64.sourceforge.net/</a>. 
-This library should be used with the target triple x86_64-pc-mingw32.
-
-   <p>Presently Windows for Itanium is not supported.
-
-<h4 class="subheading"><a name="TOC59"></a>Windows CE</h4>
-
-<p>Windows CE is supported as a target only on ARM (arm-wince-pe), Hitachi
-SuperH (sh-wince-pe), and MIPS (mips-wince-pe).
-
-<h4 class="subheading"><a name="TOC60"></a>Other Windows Platforms</h4>
-
-<p>GCC no longer supports Windows NT on the Alpha or PowerPC.
-
-   <p>GCC no longer supports the Windows POSIX subsystem.  However, it does
-support the Interix subsystem.  See above.
-
-   <p>Old target names including *-*-winnt and *-*-windowsnt are no longer used.
-
-   <p>PW32 (i386-pc-pw32) support was never completed, and the project seems to
-be inactive.  See <a href="http://pw32.sourceforge.net/">http://pw32.sourceforge.net/</a> for more information.
-
-   <p>UWIN support has been removed due to a lack of maintenance.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC61"></a><a name="x_002dx_002dcygwin"></a>*-*-cygwin</h3>
-
-<p>Ports of GCC are included with the
-<a href="http://www.cygwin.com/">Cygwin environment</a>.
-
-   <p>GCC will build under Cygwin without modification; it does not build
-with Microsoft's C++ compiler and there are no plans to make it do so.
-
-   <p>Cygwin can be compiled with i?86-pc-cygwin.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC62"></a><a name="x_002dx_002dinterix"></a>*-*-interix</h3>
-
-<p>The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
-and Subsystem for UNIX-based Applications (SUA).  Applications compiled
-with this target run in the Interix subsystem, which is separate from
-the Win32 subsystem.  This target was last known to work in GCC 3.3.
-
-   <p>For more information, see <a href="http://www.interix.com/">http://www.interix.com/</a>.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC63"></a><a name="x_002dx_002dmingw32"></a>*-*-mingw32</h3>
-
-<p>GCC will build with and support only MinGW runtime 3.12 and later. 
-Earlier versions of headers are incompatible with the new default semantics
-of <code>extern inline</code> in <code>-std=c99</code> and <code>-std=gnu99</code> modes.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC64"></a><a name="os2"></a>OS/2</h3>
-
-<p>GCC does not currently support OS/2.  However, Andrew Zabolotny has been
-working on a generic OS/2 port with pgcc.  The current code can be found
-at <a href="http://www.goof.com/pcg/os2/">http://www.goof.com/pcg/os2/</a>.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC65"></a><a name="older"></a>Older systems</h3>
-
-<p>GCC contains support files for many older (1980s and early
-1990s) Unix variants.  For the most part, support for these systems
-has not been deliberately removed, but it has not been maintained for
-several years and may suffer from bitrot.
-
-   <p>Starting with GCC 3.1, each release has a list of &ldquo;obsoleted&rdquo; systems. 
-Support for these systems is still present in that release, but
-<samp><span class="command">configure</span></samp> will fail unless the <samp><span class="option">--enable-obsolete</span></samp>
-option is given.  Unless a maintainer steps forward, support for these
-systems will be removed from the next release of GCC.
-
-   <p>Support for old systems as hosts for GCC can cause problems if the
-workarounds for compiler, library and operating system bugs affect the
-cleanliness or maintainability of the rest of GCC.  In some cases, to
-bring GCC up on such a system, if still possible with current GCC, may
-require first installing an old version of GCC which did work on that
-system, and using it to compile a more recent GCC, to avoid bugs in the
-vendor compiler.  Old releases of GCC 1 and GCC 2 are available in the
-<samp><span class="file">old-releases</span></samp> directory on the <a href="../mirrors.html">GCC mirror sites</a>.  Header bugs may generally be avoided using
-<samp><span class="command">fixincludes</span></samp>, but bugs or deficiencies in libraries and the
-operating system may still cause problems.
-
-   <p>Support for older systems as targets for cross-compilation is less
-problematic than support for them as hosts for GCC; if an enthusiast
-wishes to make such a target work again (including resurrecting any of
-the targets that never worked with GCC 2, starting from the last
-version before they were removed), patches
-<a href="../contribute.html">following the usual requirements</a> would be
-likely to be accepted, since they should not affect the support for more
-modern targets.
-
-   <p>For some systems, old versions of GNU binutils may also be useful,
-and are available from <samp><span class="file">pub/binutils/old-releases</span></samp> on
-<a href="http://sourceware.org/mirrors.html">sourceware.org mirror sites</a>.
-
-   <p>Some of the information on specific systems above relates to
-such older systems, but much of the information
-about GCC on such systems (which may no longer be applicable to
-current GCC) is to be found in the GCC texinfo manual.
-
-   <p><hr />
-
-<h3 class="heading"><a name="TOC66"></a><a name="elf"></a>all ELF targets (SVR4, Solaris 2, etc.)</h3>
-
-<p>C++ support is significantly better on ELF targets if you use the
-<a href="./configure.html#with-gnu-ld">GNU linker</a>; duplicate copies of
-inlines, vtables and template instantiations will be discarded
-automatically.
-
-   <p><hr />
-<p><a href="./index.html">Return to the GCC Installation page</a>
-
-<!-- ***Old documentation****************************************************** -->
-<!-- ***GFDL******************************************************************** -->
-<!-- *************************************************************************** -->
-<!-- Part 6 The End of the Document -->
-</body></html>
-
--- a/INSTALL/test.html	Mon May 24 12:48:09 2010 +0900
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,233 +0,0 @@
-<html lang="en">
-<head>
-<title>Installing GCC: Testing</title>
-<meta http-equiv="Content-Type" content="text/html">
-<meta name="description" content="Installing GCC: Testing">
-<meta name="generator" content="makeinfo 4.13">
-<link title="Top" rel="top" href="#Top">
-<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
-<!--
-Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
-1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
-2008 Free Software Foundation, Inc.
-
-   Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, the Front-Cover texts being (a) (see below), and
-with the Back-Cover Texts being (b) (see below).  A copy of the
-license is included in the section entitled "GNU Free Documentation License".
-
-(a) The FSF's Front-Cover Text is:
-
-     A GNU Manual
-
-(b) The FSF's Back-Cover Text is:
-
-     You have freedom to copy and modify this GNU Manual, like GNU
-     software.  Copies published by the Free Software Foundation raise
-     funds for GNU development.-->
-<meta http-equiv="Content-Style-Type" content="text/css">
-<style type="text/css"><!--
-  pre.display { font-family:inherit }
-  pre.format  { font-family:inherit }
-  pre.smalldisplay { font-family:inherit; font-size:smaller }
-  pre.smallformat  { font-family:inherit; font-size:smaller }
-  pre.smallexample { font-size:smaller }
-  pre.smalllisp    { font-size:smaller }
-  span.sc    { font-variant:small-caps }
-  span.roman { font-family:serif; font-weight:normal; } 
-  span.sansserif { font-family:sans-serif; font-weight:normal; } 
---></style>
-</head>
-<body>
-<h1 class="settitle">Installing GCC: Testing</h1>
-<a name="index-Testing-1"></a><a name="index-Installing-GCC_003a-Testing-2"></a><a name="index-Testsuite-3"></a>
-Before you install GCC, we encourage you to run the testsuites and to
-compare your results with results from a similar configuration that have
-been submitted to the
-<a href="http://gcc.gnu.org/ml/gcc-testresults/">gcc-testresults mailing list</a>. 
-Some of these archived results are linked from the build status lists
-at <a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>, although not everyone who
-reports a successful build runs the testsuites and submits the results. 
-This step is optional and may require you to download additional software,
-but it can give you confidence in your new GCC installation or point out
-problems before you install and start using your new GCC.
-
-   <p>First, you must have <a href="download.html">downloaded the testsuites</a>. 
-These are part of the full distribution, but if you downloaded the
-&ldquo;core&rdquo; compiler plus any front ends, you must download the testsuites
-separately.
-
-   <p>Second, you must have the testing tools installed.  This includes
-<a href="http://www.gnu.org/software/dejagnu/">DejaGnu</a>, Tcl, and Expect;
-the DejaGnu site has links to these.
-
-   <p>If the directories where <samp><span class="command">runtest</span></samp> and <samp><span class="command">expect</span></samp> were
-installed are not in the <samp><span class="env">PATH</span></samp>, you may need to set the following
-environment variables appropriately, as in the following example (which
-assumes that DejaGnu has been installed under <samp><span class="file">/usr/local</span></samp>):
-
-<pre class="smallexample">          TCL_LIBRARY = /usr/local/share/tcl8.0
-          DEJAGNULIBS = /usr/local/share/dejagnu
-</pre>
-   <p>(On systems such as Cygwin, these paths are required to be actual
-paths, not mounts or links; presumably this is due to some lack of
-portability in the DejaGnu code.)
-
-   <p>Finally, you can run the testsuite (which may take a long time):
-<pre class="smallexample">          cd <var>objdir</var>; make -k check
-</pre>
-   <p>This will test various components of GCC, such as compiler
-front ends and runtime libraries.  While running the testsuite, DejaGnu
-might emit some harmless messages resembling
-&lsquo;<samp><span class="samp">WARNING: Couldn't find the global config file.</span></samp>&rsquo; or
-&lsquo;<samp><span class="samp">WARNING: Couldn't find tool init file</span></samp>&rsquo; that can be ignored.
-
-   <p>If you are testing a cross-compiler, you may want to run the testsuite
-on a simulator as described at <a href="http://gcc.gnu.org/simtest-howto.html">http://gcc.gnu.org/simtest-howto.html</a>.
-
-<h3 class="section"><a name="TOC0"></a>How can you run the testsuite on selected tests?</h3>
-
-<p>In order to run sets of tests selectively, there are targets
-&lsquo;<samp><span class="samp">make check-gcc</span></samp>&rsquo; and &lsquo;<samp><span class="samp">make check-g++</span></samp>&rsquo;
-in the <samp><span class="file">gcc</span></samp> subdirectory of the object directory.  You can also
-just run &lsquo;<samp><span class="samp">make check</span></samp>&rsquo; in a subdirectory of the object directory.
-
-   <p>A more selective way to just run all <samp><span class="command">gcc</span></samp> execute tests in the
-testsuite is to use
-
-<pre class="smallexample">         make check-gcc RUNTESTFLAGS="execute.exp <var>other-options</var>"
-</pre>
-   <p>Likewise, in order to run only the <samp><span class="command">g++</span></samp> &ldquo;old-deja&rdquo; tests in
-the testsuite with filenames matching &lsquo;<samp><span class="samp">9805*</span></samp>&rsquo;, you would use
-
-<pre class="smallexample">         make check-g++ RUNTESTFLAGS="old-deja.exp=9805* <var>other-options</var>"
-</pre>
-   <p>The <samp><span class="file">*.exp</span></samp> files are located in the testsuite directories of the GCC
-source, the most important ones being <samp><span class="file">compile.exp</span></samp>,
-<samp><span class="file">execute.exp</span></samp>, <samp><span class="file">dg.exp</span></samp> and <samp><span class="file">old-deja.exp</span></samp>. 
-To get a list of the possible <samp><span class="file">*.exp</span></samp> files, pipe the
-output of &lsquo;<samp><span class="samp">make check</span></samp>&rsquo; into a file and look at the
-&lsquo;<samp><span class="samp">Running ...  .exp</span></samp>&rsquo; lines.
-
-<h3 class="section"><a name="TOC1"></a>Passing options and running multiple testsuites</h3>
-
-<p>You can pass multiple options to the testsuite using the
-&lsquo;<samp><span class="samp">--target_board</span></samp>&rsquo; option of DejaGNU, either passed as part of
-&lsquo;<samp><span class="samp">RUNTESTFLAGS</span></samp>&rsquo;, or directly to <samp><span class="command">runtest</span></samp> if you prefer to
-work outside the makefiles.  For example,
-
-<pre class="smallexample">         make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
-</pre>
-   <p>will run the standard <samp><span class="command">g++</span></samp> testsuites (&ldquo;unix&rdquo; is the target name
-for a standard native testsuite situation), passing
-&lsquo;<samp><span class="samp">-O3 -fmerge-constants</span></samp>&rsquo; to the compiler on every test, i.e.,
-slashes separate options.
-
-   <p>You can run the testsuites multiple times using combinations of options
-with a syntax similar to the brace expansion of popular shells:
-
-<pre class="smallexample">         ..."--target_board=arm-sim\{-mhard-float,-msoft-float\}\{-O1,-O2,-O3,\}"
-</pre>
-   <p>(Note the empty option caused by the trailing comma in the final group.) 
-The following will run each testsuite eight times using the &lsquo;<samp><span class="samp">arm-sim</span></samp>&rsquo;
-target, as if you had specified all possible combinations yourself:
-
-<pre class="smallexample">         --target_board=arm-sim/-mhard-float/-O1
-         --target_board=arm-sim/-mhard-float/-O2
-         --target_board=arm-sim/-mhard-float/-O3
-         --target_board=arm-sim/-mhard-float
-         --target_board=arm-sim/-msoft-float/-O1
-         --target_board=arm-sim/-msoft-float/-O2
-         --target_board=arm-sim/-msoft-float/-O3
-         --target_board=arm-sim/-msoft-float
-</pre>
-   <p>They can be combined as many times as you wish, in arbitrary ways.  This
-list:
-
-<pre class="smallexample">         ..."--target_board=unix/-Wextra\{-O3,-fno-strength\}\{-fomit-frame,\}"
-</pre>
-   <p>will generate four combinations, all involving &lsquo;<samp><span class="samp">-Wextra</span></samp>&rsquo;.
-
-   <p>The disadvantage to this method is that the testsuites are run in serial,
-which is a waste on multiprocessor systems.  For users with GNU Make and
-a shell which performs brace expansion, you can run the testsuites in
-parallel by having the shell perform the combinations and <samp><span class="command">make</span></samp>
-do the parallel runs.  Instead of using &lsquo;<samp><span class="samp">--target_board</span></samp>&rsquo;, use a
-special makefile target:
-
-<pre class="smallexample">         make -j<var>N</var> check-<var>testsuite</var>//<var>test-target</var>/<var>option1</var>/<var>option2</var>/...
-</pre>
-   <p>For example,
-
-<pre class="smallexample">         make -j3 check-gcc//sh-hms-sim/{-m1,-m2,-m3,-m3e,-m4}/{,-nofpu}
-</pre>
-   <p>will run three concurrent &ldquo;make-gcc&rdquo; testsuites, eventually testing all
-ten combinations as described above.  Note that this is currently only
-supported in the <samp><span class="file">gcc</span></samp> subdirectory.  (To see how this works, try
-typing <samp><span class="command">echo</span></samp> before the example given here.)
-
-<h3 class="section"><a name="TOC2"></a>Additional testing for Java Class Libraries</h3>
-
-<p>The Java runtime tests can be executed via &lsquo;<samp><span class="samp">make check</span></samp>&rsquo;
-in the <samp><var>target</var><span class="file">/libjava/testsuite</span></samp> directory in
-the build tree.
-
-   <p>The <a href="http://sourceware.org/mauve/">Mauve Project</a> provides
-a suite of tests for the Java Class Libraries.  This suite can be run
-as part of libgcj testing by placing the Mauve tree within the libjava
-testsuite at <samp><span class="file">libjava/testsuite/libjava.mauve/mauve</span></samp>, or by
-specifying the location of that tree when invoking &lsquo;<samp><span class="samp">make</span></samp>&rsquo;, as in
-&lsquo;<samp><span class="samp">make MAUVEDIR=~/mauve check</span></samp>&rsquo;.
-
-<h3 class="section"><a name="TOC3"></a>How to interpret test results</h3>
-
-<p>The result of running the testsuite are various <samp><span class="file">*.sum</span></samp> and <samp><span class="file">*.log</span></samp>
-files in the testsuite subdirectories.  The <samp><span class="file">*.log</span></samp> files contain a
-detailed log of the compiler invocations and the corresponding
-results, the <samp><span class="file">*.sum</span></samp> files summarize the results.  These summaries
-contain status codes for all tests:
-
-     <ul>
-<li>PASS: the test passed as expected
-<li>XPASS: the test unexpectedly passed
-<li>FAIL: the test unexpectedly failed
-<li>XFAIL: the test failed as expected
-<li>UNSUPPORTED: the test is not supported on this platform
-<li>ERROR: the testsuite detected an error
-<li>WARNING: the testsuite detected a possible problem
-</ul>
-
-   <p>It is normal for some tests to report unexpected failures.  At the
-current time the testing harness does not allow fine grained control
-over whether or not a test is expected to fail.  This problem should
-be fixed in future releases.
-
-<h3 class="section"><a name="TOC4"></a>Submitting test results</h3>
-
-<p>If you want to report the results to the GCC project, use the
-<samp><span class="file">contrib/test_summary</span></samp> shell script.  Start it in the <var>objdir</var> with
-
-<pre class="smallexample">         <var>srcdir</var>/contrib/test_summary -p your_commentary.txt \
-             -m gcc-testresults@gcc.gnu.org |sh
-</pre>
-   <p>This script uses the <samp><span class="command">Mail</span></samp> program to send the results, so
-make sure it is in your <samp><span class="env">PATH</span></samp>.  The file <samp><span class="file">your_commentary.txt</span></samp> is
-prepended to the testsuite summary and should contain any special
-remarks you have on your results or your build environment.  Please
-do not edit the testsuite result block or the subject line, as these
-messages may be automatically processed.
-
-   <p><hr />
-<p><a href="./index.html">Return to the GCC Installation page</a>
-
-<!-- ***Final install*********************************************************** -->
-<!-- ***Binaries**************************************************************** -->
-<!-- ***Specific**************************************************************** -->
-<!-- ***Old documentation****************************************************** -->
-<!-- ***GFDL******************************************************************** -->
-<!-- *************************************************************************** -->
-<!-- Part 6 The End of the Document -->
-</body></html>
-
--- a/NEWS	Mon May 24 12:48:09 2010 +0900
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,10555 +0,0 @@
-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-4.4/index.html
-                           GCC 4.4 Release Series
-
-   October 15, 2009
-
-   The [1]GNU project and the GCC developers are pleased to announce the
-   release of GCC 4.4.3.
-
-   This release is a bug-fix release, containing fixes for regressions in
-   GCC 4.4.1 relative to previous releases of GCC.
-
-Release History
-
-   GCC 4.4.3
-          January 21, 2010 ([2]changes)
-
-   GCC 4.4.2
-          October 15, 2009 ([3]changes)
-
-   GCC 4.4.1
-          July 22, 2009 ([4]changes)
-
-   GCC 4.4.0
-          April 21, 2009 ([5]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 [6]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 [7]amazing group of volunteers is
-   what makes GCC successful.
-
-   For additional information about GCC please refer to the [8]GCC project
-   web site or contact the [9]GCC development mailing list.
-
-   To obtain GCC please use [10]our mirror sites or [11]our SVN server.
-
-   Please send FSF & GNU inquiries & questions to [12]gnu@gnu.org. There
-   are also [13]other ways to contact the FSF.
-
-   These pages are maintained by [14]the GCC team.
-
-
-    For questions related to the use of GCC, please consult these web
-    pages and the [15]GCC manuals. If that fails, the
-    [16]gcc-help@gcc.gnu.org mailing list might help.
-    Please send comments on these web pages and the development of GCC to
-    our developer mailing list at [17]gcc@gnu.org or [18]gcc@gcc.gnu.org.
-    All of our lists have [19]public archives.
-
-   Copyright (C) Free Software Foundation, Inc., 51 Franklin St, Fifth
-   Floor, Boston, MA 02110, USA.
-
-   Verbatim copying and distribution of this entire article is permitted
-   in any medium, provided this notice is preserved.
-   Last modified 2010-01-21 [20]Valid XHTML 1.0
-
-References
-
-   1. http://www.gnu.org/
-   2. http://gcc.gnu.org/gcc-4.4/changes.html
-   3. http://gcc.gnu.org/gcc-4.4/changes.html
-   4. http://gcc.gnu.org/gcc-4.4/changes.html
-   5. http://gcc.gnu.org/gcc-4.4/changes.html
-   6. http://gcc.gnu.org/gcc-4.4/buildstat.html
-   7. http://gcc.gnu.org/onlinedocs/gcc/Contributors.html
-   8. http://gcc.gnu.org/index.html
-   9. mailto:gcc@gcc.gnu.org
-  10. http://gcc.gnu.org/mirrors.html
-  11. http://gcc.gnu.org/svn.html
-  12. mailto:gnu@gnu.org
-  13. http://www.gnu.org/home.html#ContactInfo
-  14. http://gcc.gnu.org/about.html
-  15. http://gcc.gnu.org/onlinedocs/
-  16. mailto:gcc-help@gcc.gnu.org
-  17. mailto:gcc@gnu.org
-  18. mailto:gcc@gcc.gnu.org
-  19. http://gcc.gnu.org/lists.html
-  20. http://validator.w3.org/check/referer
-======================================================================
-http://gcc.gnu.org/gcc-4.4/changes.html
-                           GCC 4.4 Release Series
-                      Changes, New Features, and Fixes
-
-   The latest release in the 4.4 release series is [1]GCC 4.4.3.
-
-Caveats
-
-     * __builtin_stdarg_start has been completely removed from GCC.
-       Support for <varargs.h> had been deprecated since GCC 4.0. Use
-       __builtin_va_start as a replacement.
-     * Some of the errors issued by the C++ front end that could be
-       downgraded to warnings in previous releases by using -fpermissive
-       are now warnings by default. They can be converted into errors by
-       using -pedantic-errors.
-     * Use of the cpp assertion extension will now emit a warning when
-       -Wdeprecated or -pedantic is used. This extension has been
-       deprecated for many years, but never warned about.
-     * Packed bit-fields of type char were not properly bit-packed on many
-       targets prior to GCC 4.4. On these targets, the fix in GCC 4.4
-       causes an ABI change. For example there is no longer a 4-bit
-       padding between field a and b in this structure:
-    struct foo
-    {
-      char a:4;
-      char b:8;
-    } __attribute__ ((packed));
-       There is a new warning to help identify fields that are affected:
-    foo.c:5: note: Offset of packed bit-field 'b' has changed in GCC 4.4
-       The warning can be disabled with -Wno-packed-bitfield-compat.
-     * On ARM EABI targets, the C++ mangling of the va_list type has been
-       changed to conform to the current revision of the EABI. This does
-       not affect the libstdc++ library included with GCC.
-     * The SCOUNT and POS bits of the MIPS DSP control register are now
-       treated as global. Previous versions of GCC treated these fields as
-       call-clobbered instead.
-     * The MIPS port no longer recognizes the h asm constraint. It was
-       necessary to remove this constraint in order to avoid generating
-       unpredictable code sequences.
-       One of the main uses of the h constraint was to extract the high
-       part of a multiplication on 64-bit targets. For example:
-    asm ("dmultu\t%1,%2" : "=h" (result) : "r" (x), "r" (y));
-       You can now achieve the same effect using 128-bit types:
-    typedef unsigned int uint128_t __attribute__((mode(TI)));
-    result = ((uint128_t) x * y) >> 64;
-       The second sequence is better in many ways. For example, if x and y
-       are constants, the compiler can perform the multiplication at
-       compile time. If x and y are not constants, the compiler can
-       schedule the runtime multiplication better than it can schedule an
-       asm statement.
-     * Support for a number of older systems and recently unmaintained or
-       untested target ports of GCC has been declared obsolete in GCC 4.4.
-       Unless there is activity to revive them, the next release of GCC
-       will have their sources permanently removed.
-       The following ports for individual systems on particular
-       architectures have been obsoleted:
-          + Generic a.out on IA32 and m68k (i[34567]86-*-aout*,
-            m68k-*-aout*)
-          + Generic COFF on ARM, H8300, IA32, m68k and SH (arm-*-coff*,
-            armel-*-coff*, h8300-*-*, i[34567]86-*-coff*, m68k-*-coff*,
-            sh-*-*). This does not affect other more specific targets
-            using the COFF object format on those architectures, or the
-            more specific H8300 and SH targets (h8300-*-rtems*,
-            h8300-*-elf*, sh-*-elf*, sh-*-symbianelf*, sh-*-linux*,
-            sh-*-netbsdelf*, sh-*-rtems*, sh-wrs-vxworks).
-          + 2BSD on PDP-11 (pdp11-*-bsd)
-          + AIX 4.1 and 4.2 on PowerPC (rs6000-ibm-aix4.[12]*,
-            powerpc-ibm-aix4.[12]*)
-          + Tuning support for Itanium1 (Merced) variants. Note that code
-            tuned for Itanium2 should also run correctly on Itanium1.
-     * The protoize and unprotoize utilities have been obsoleted and will
-       be removed in GCC 4.5. These utilities have not been installed by
-       default since GCC 3.0.
-     * Support has been removed for all the [2]configurations obsoleted in
-       GCC 4.3.
-     * Unknown -Wno-* options are now silently ignored by GCC if no other
-       diagnostics are issued. If other diagnostics are issued, then GCC
-       warns about the unknown options.
-     * More information on porting to GCC 4.4 from previous versions of
-       GCC can be found in the [3]porting guide for this release.
-
-General Optimizer Improvements
-
-     * A new command-line switch -findirect-inlining has been added. When
-       turned on it allows the inliner to also inline indirect calls that
-       are discovered to have known targets at compile time thanks to
-       previous inlining.
-     * A new command-line switch -ftree-switch-conversion has been added.
-       This new pass turns simple initializations of scalar variables in
-       switch statements into initializations from a static array, given
-       that all the values are known at compile time and the ratio between
-       the new array size and the original switch branches does not exceed
-       the parameter --param switch-conversion-max-branch-ratio (default
-       is eight).
-     * A new command-line switch -ftree-builtin-call-dce has been added.
-       This optimization eliminates unnecessary calls to certain builtin
-       functions when the return value is not used, in cases where the
-       calls can not be eliminated entirely because the function may set
-       errno. This optimization is on by default at -O2 and above.
-     * A new command-line switch -fconserve-stack directs the compiler to
-       minimize stack usage even if it makes the generated code slower.
-       This affects inlining decisions.
-     * When the assembler supports it, the compiler will now emit unwind
-       information using assembler .cfi directives. This makes it possible
-       to use such directives in inline assembler code. The new option
-       -fno-dwarf2-cfi-asm directs the compiler to not use .cfi
-       directives.
-     * The [4]Graphite branch has been merged. This merge has brought in a
-       new framework for loop optimizations based on a polyhedral
-       intermediate representation. These optimizations apply to all the
-       languages supported by GCC. The following new code transformations
-       are available in GCC 4.4:
-          + -floop-interchange performs loop interchange transformations
-            on loops. Interchanging two nested loops switches the inner
-            and outer loops. For example, given a loop like:
-          DO J = 1, M
-            DO I = 1, N
-              A(J, I) = A(J, I) * C
-            ENDDO
-          ENDDO
-
-            loop interchange will transform the loop as if the user had
-            written:
-          DO I = 1, N
-            DO J = 1, M
-              A(J, I) = A(J, I) * C
-            ENDDO
-          ENDDO
-
-            which can be beneficial when N is larger than the caches,
-            because in Fortran, the elements of an array are stored in
-            memory contiguously by column, and the original loop iterates
-            over rows, potentially creating at each access a cache miss.
-          + -floop-strip-mine performs loop strip mining transformations
-            on loops. Strip mining splits a loop into two nested loops.
-            The outer loop has strides equal to the strip size and the
-            inner loop has strides of the original loop within a strip.
-            For example, given a loop like:
-          DO I = 1, N
-            A(I) = A(I) + C
-          ENDDO
-
-            loop strip mining will transform the loop as if the user had
-            written:
-          DO II = 1, N, 4
-            DO I = II, min (II + 3, N)
-              A(I) = A(I) + C
-            ENDDO
-          ENDDO
-
-          + -floop-block performs loop blocking transformations on loops.
-            Blocking strip mines each loop in the loop nest such that the
-            memory accesses of the element loops fit inside caches. For
-            example, given a loop like:
-          DO I = 1, N
-            DO J = 1, M
-              A(J, I) = B(I) + C(J)
-            ENDDO
-          ENDDO
-
-            loop blocking will transform the loop as if the user had
-            written:
-          DO II = 1, N, 64
-            DO JJ = 1, M, 64
-              DO I = II, min (II + 63, N)
-                DO J = JJ, min (JJ + 63, M)
-                  A(J, I) = B(I) + C(J)
-                ENDDO
-              ENDDO
-            ENDDO
-          ENDDO
-
-            which can be beneficial when M is larger than the caches,
-            because the innermost loop will iterate over a smaller amount
-            of data that can be kept in the caches.
-     * A new register allocator has replaced the old one. It is called
-       integrated register allocator (IRA) because coalescing, register
-       live range splitting, and hard register preferencing are done
-       on-the-fly during coloring. It also has better integration with the
-       reload pass. IRA is a regional register allocator which uses modern
-       Chaitin-Briggs coloring instead of Chow's priority coloring used in
-       the old register allocator. More info about IRA internals and
-       options can be found in the GCC manuals.
-     * A new instruction scheduler and software pipeliner, based on the
-       selective scheduling approach, has been added. The new pass
-       performs instruction unification, register renaming, substitution
-       through register copies, and speculation during scheduling. The
-       software pipeliner is able to pipeline non-countable loops. The new
-       pass is targeted at scheduling-eager in-order platforms. In GCC 4.4
-       it is available for the Intel Itanium platform working by default
-       as the second scheduling pass (after register allocation) at the
-       -O3 optimization level.
-     * When using -fprofile-generate with a multi-threaded program, the
-       profile counts may be slightly wrong due to race conditions. The
-       new -fprofile-correction option directs the compiler to apply
-       heuristics to smooth out the inconsistencies. By default the
-       compiler will give an error message when it finds an inconsistent
-       profile.
-     * The new -fprofile-dir=PATH option permits setting the directory
-       where profile data files are stored when using -fprofile-generate
-       and friends, and the directory used when reading profile data files
-       using -fprofile-use and friends.
-
-New warning options
-
-     * The new -Wframe-larger-than=NUMBER option directs GCC to emit a
-       warning if any stack frame is larger than NUMBER bytes. This may be
-       used to help ensure that code fits within a limited amount of stack
-       space.
-     * The new -Wno-mudflap option disables warnings about constructs
-       which can not be instrumented when using -fmudflap.
-
-New Languages and Language specific improvements
-
-     * Version 3.0 of the [5]OpenMP specification is now supported for the
-       C, C++, and Fortran compilers.
-     * New character data types, per [6]TR 19769: New character types in
-       C, are now supported for the C compiler in -std=gnu99 mode, as
-       __CHAR16_TYPE__ and __CHAR32_TYPE__, and for the C++ compiler in
-       -std=c++0x and -std=gnu++0x modes, as char16_t and char32_t too.
-
-  C family
-
-     * A new optimize attribute was added to allow programmers to change
-       the optimization level and particular optimization options for an
-       individual function. You can also change the optimization options
-       via the GCC optimize pragma for functions defined after the pragma.
-       The GCC push_options pragma and the GCC pop_options pragma allow
-       you temporarily save and restore the options used. The GCC
-       reset_options pragma restores the options to what was specified on
-       the command line.
-     * Uninitialized warnings do not require enabling optimization
-       anymore, that is, -Wuninitialized can be used together with -O0.
-       Nonetheless, the warnings given by -Wuninitialized will probably be
-       more accurate if optimization is enabled.
-     * -Wparentheses now warns about expressions such as (!x | y) and (!x
-       & y). Using explicit parentheses, such as in ((!x) | y), silences
-       this warning.
-     * -Wsequence-point now warns within if, while,do while and for
-       conditions, and within for begin/end expressions.
-     * A new option -dU is available to dump definitions of preprocessor
-       macros that are tested or expanded.
-
-  C++
-
-     * [7]Improved experimental support for the upcoming ISO C++ standard,
-       C++0x. Including support for auto, inline namespaces, generalized
-       initializer lists, defaulted and deleted functions, new character
-       types, and scoped enums.
-     * Those errors that may be downgraded to warnings to build legacy
-       code now mention -fpermissive when -fdiagnostics-show-option is
-       enabled.
-     * -Wconversion now warns if the result of a static_cast to enumeral
-       type is unspecified because the value is outside the range of the
-       enumeral type.
-     * -Wuninitialized now warns if a non-static reference or non-static
-       const member appears in a class without constructors.
-     * G++ now properly implements value-initialization, so objects with
-       an initializer of () and an implicitly defined default constructor
-       will be zero-initialized before the default constructor is called.
-
-    Runtime Library (libstdc++)
-
-     * [8]Improved experimental support for the upcoming ISO C++ standard,
-       C++0x, including:
-          + Support for <chrono>, <condition_variable>, <cstdatomic>,
-            <forward_list>, <initializer_list>, <mutex>, <ratio>,
-            <system_error>, and <thread>.
-          + unique_ptr, <algorithm> additions, exception propagation, and
-            support for the new character types in <string> and <limits>.
-          + Existing facilities now exploit initializer lists, defaulted
-            and deleted functions, and the newly implemented core C++0x
-            features.
-          + Some standard containers are more efficient together with
-            stateful allocators, i.e., no allocator is constructed on the
-            fly at element construction time.
-     * Experimental support for non-standard pointer types in containers.
-     * The long standing libstdc++/30928 has been fixed for targets
-       running glibc 2.10 or later.
-     * As usual, many small and larger bug fixes, in particular quite a
-       few corner cases in <locale>.
-
-  Fortran
-
-     * GNU Fortran now employs libcpp directly instead of using cc1 as an
-       external preprocessor. The [9]-cpp option was added to allow manual
-       invocation of the preprocessor without relying on filename
-       extensions.
-     * The [10]-Warray-temporaries option warns about array temporaries
-       generated by the compiler, as an aid to optimization.
-     * The [11]-fcheck-array-temporaries option has been added, printing a
-       notification at run time, when an array temporary had to be created
-       for an function argument. Contrary to -Warray-temporaries the
-       warning is only printed if the array is noncontiguous.
-     * Improved generation of DWARF debugging symbols
-     * If using an intrinsic not part of the selected standard (via -std=
-       and -fall-intrinsics) gfortran will now treat it as if this
-       procedure were declared EXTERNAL and try to link to a user-supplied
-       procedure. -Wintrinsics-std will warn whenever this happens. The
-       now-useless option -Wnonstd-intrinsic was removed.
-     * The flag -falign-commons has been added to control the alignment of
-       variables in COMMON blocks, which is enabled by default in line
-       with previous GCC version. Using -fno-align-commons one can force
-       commons to be contiguous in memory as required by the Fortran
-       standard, however, this slows down the memory access. The option
-       -Walign-commons, which is enabled by default, warns when padding
-       bytes were added for alignment. The proper solution is to sort the
-       common objects by decreasing storage size, which avoids the
-       alignment problems.
-     * Fortran 2003 support has been extended:
-          + Wide characters (ISO 10646, UCS-4, kind=4) and UTF-8 I/O is
-            now supported (except internal reads from/writes to wide
-            strings). [12]-fbackslash now supports also \unnnn and
-            \Unnnnnnnn to enter Unicode characters.
-          + Asynchronous I/O (implemented as synchronous I/O) and the
-            decimal=, size=, sign=, pad=, blank=, and delim= specifiers
-            are now supported in I/O statements.
-          + Support for Fortran 2003 structure constructors and for array
-            constructor with typespec has been added.
-          + Procedure Pointers (but not yet as component in derived types
-            and as function results) are now supported.
-          + Abstract types, type extension, and type-bound procedures
-            (both PROCEDURE and GENERIC but not as operators). Note: As
-            CLASS/polymorphyic types are not implemented, type-bound
-            procedures with PASS accept as non-standard extension TYPE
-            arguments.
-     * Fortran 2008 support has been added:
-          + The -std=f2008 option and support for the file extensions
-            .f2008 and .F2008 has been added.
-          + The g0 format descriptor is now supported.
-          + The Fortran 2008 mathematical intrinsics ASINH, ACOSH, ATANH,
-            ERF, ERFC, GAMMA, LOG_GAMMA, BESSEL_*, HYPOT, and ERFC_SCALED
-            are now available (some of them existed as GNU extension
-            before). Note: The hyperbolic functions are not yet supporting
-            complex arguments and the three- argument version of BESSEL_*N
-            is not available.
-          + The bit intrinsics LEADZ and TRAILZ have been added.
-
-  Java (GCJ)
-
-  Ada
-
-     * The Ada runtime now supports multilibs on many platforms including
-       x86_64, SPARC and PowerPC. Their build is enabled by default.
-
-New Targets and Target Specific Improvements
-
-  ARM
-
-     * GCC now supports optimizing for the Cortex-A9, Cortex-R4 and
-       Cortex-R4F processors and has many other improvements to
-       optimization for ARM processors.
-     * GCC now supports the VFPv3 variant with 16 double-precision
-       registers with -mfpu=vfpv3-d16. The option -mfpu=vfp3 has been
-       renamed to -mfpu=vfpv3.
-     * GCC now supports the -mfix-cortex-m3-ldrd option to work around an
-       erratum on Cortex-M3 processors.
-     * GCC now supports the __sync_* atomic operations for ARM EABI
-       GNU/Linux.
-     * The section anchors optimization is now enabled by default when
-       optimizing for ARM.
-     * GCC now uses a new EABI-compatible profiling interface for EABI
-       targets. This requires a function __gnu_mcount_nc, which is
-       provided by GNU libc versions 2.8 and later.
-
-  AVR
-
-     * The -mno-tablejump option has been deprecated because it has the
-       same effect as the -fno-jump-tables option.
-     * Added support for these new AVR devices:
-          + ATA6289
-          + ATtiny13A
-          + ATtiny87
-          + ATtiny167
-          + ATtiny327
-          + ATmega8C1
-          + ATmega16C1
-          + ATmega32C1
-          + ATmega8M1
-          + ATmega16M1
-          + ATmega32M1
-          + ATmega32U4
-          + ATmega16HVB
-          + ATmega4HVD
-          + ATmega8HVD
-          + ATmega64C1
-          + ATmega64M1
-          + ATmega16U4
-          + ATmega32U6
-          + ATmega128RFA1
-          + AT90PWM81
-          + AT90SCR100
-          + M3000F
-          + M3000S
-          + M3001B
-
-  IA-32/x86-64
-
-     * Support for Intel AES built-in functions and code generation is
-       available via -maes.
-     * Support for Intel PCLMUL built-in function and code generation is
-       available via -mpclmul.
-     * Support for Intel AVX built-in functions and code generation is
-       available via -mavx.
-     * Automatically align the stack for local variables with alignment
-       requirement.
-     * GCC can now utilize the SVML library for vectorizing calls to a set
-       of C99 functions if -mveclibabi=svml is specified and you link to
-       an SVML ABI compatible library.
-     * On x86-64, the ABI has been changed in the following cases to
-       conform to the x86-64 ABI:
-          + Passing/returning structures with flexible array member:
-  struct foo
-    {
-      int i;
-      int flex[];
-    };
-          + Passing/returning structures with complex float member:
-  struct foo
-    {
-      int i;
-      __complex__ float f;
-    };
-          + Passing/returning unions with long double member:
-  union foo
-    {
-      int x;
-      long double ld;
-    };
-       Code built with previous versions of GCC that uses any of these is
-       not compatible with code built with GCC 4.4.0 or later.
-     * A new target attribute was added to allow programmers to change the
-       target options like -msse2 or -march=k8 for an individual function.
-       You can also change the target options via the GCC target pragma
-       for functions defined after the pragma.
-     * GCC can now be configured with options --with-arch-32,
-       --with-arch-64, --with-cpu-32, --with-cpu-64, --with-tune-32 and
-       --with-tune-64 to control the default optimization separately for
-       32-bit and 64-bit modes.
-
-  IA-32/IA64
-
-     * Support for __float128 (TFmode) IEEE quad type and corresponding
-       TCmode IEEE complex quad type is available via the soft-fp library
-       on IA-32/IA64 targets. This includes basic arithmetic operations
-       (addition, subtraction, negation, multiplication and division) on
-       __float128 real and TCmode complex values, the full set of IEEE
-       comparisons between __float128 values, conversions to and from
-       float, double and long double floating point types, as well as
-       conversions to and from signed or unsigned integer, signed or
-       unsigned long integer and signed or unsigned quad (TImode, IA64
-       only) integer types. Additionally, all operations generate the full
-       set of IEEE exceptions and support the full set of IEEE rounding
-       modes.
-
-  M68K/ColdFire
-
-     * GCC now supports instruction scheduling for ColdFire V1, V3 and V4
-       processors. (Scheduling support for ColdFire V2 processors was
-       added in GCC 4.3.)
-     * GCC now supports the -mxgot option to support programs requiring
-       many GOT entries on ColdFire.
-     * The m68k-*-linux-gnu target now builds multilibs by default.
-
-  MIPS
-
-     * MIPS Technologies have extended the original MIPS SVR4 ABI to
-       include support for procedure linkage tables (PLTs) and copy
-       relocations. These extensions allow GNU/Linux executables to use a
-       significantly more efficient code model than the one defined by the
-       original ABI.
-       GCC support for this code model is available via a new command-line
-       option, -mplt. There is also a new configure-time option,
-       --with-mips-plt, to make -mplt the default.
-       The new code model requires support from the assembler, the linker,
-       and the runtime C library. This support is available in binutils
-       2.19 and GLIBC 2.9.
-     * GCC can now generate MIPS16 code for 32-bit GNU/Linux executables
-       and 32-bit GNU/Linux shared libraries. This feature requires GNU
-       binutils 2.19 or above.
-     * Support for RMI's XLR processor is now available through the
-       -march=xlr and -mtune=xlr options.
-     * 64-bit targets can now perform 128-bit multiplications inline,
-       instead of relying on a libgcc function.
-     * Native GNU/Linux toolchains now support -march=native and
-       -mtune=native, which select the host processor.
-     * GCC now supports the R10K, R12K, R14K and R16K processors. The
-       canonical -march= and -mtune= names for these processors are
-       r10000, r12000, r14000 and r16000 respectively.
-     * GCC can now work around the side effects of speculative execution
-       on R10K processors. Please see the documentation of the
-       -mr10k-cache-barrier option for details.
-     * Support for the MIPS64 Release 2 instruction set has been added.
-       The option -march=mips64r2 enables generation of these
-       instructions.
-     * GCC now supports Cavium Networks' Octeon processor. This support is
-       available through the -march=octeon and -mtune=octeon options.
-     * GCC now supports STMicroelectronics' Loongson 2E/2F processors. The
-       canonical -march= and -mtune= names for these processors are
-       loongson2e and loongson2f.
-
-  picochip
-
-   Picochip is a 16-bit processor. A typical picoChip contains over 250
-   small cores, each with small amounts of memory. There are three
-   processor variants (STAN, MEM and CTRL) with different instruction sets
-   and memory configurations and they can be chosen using the -mae option.
-
-   This port is intended to be a "C" only port.
-
-  Power Architecture and PowerPC
-
-     * GCC now supports the e300c2, e300c3 and e500mc processors.
-     * GCC now supports Xilinx processors with a single-precision FPU.
-     * Decimal floating point is now supported for e500 processors.
-
-  S/390, zSeries and System z9/z10
-
-     * Support for the IBM System z10 EC/BC processor has been added. When
-       using the -march=z10 option, the compiler will generate code making
-       use of instructions provided by the General-Instruction-Extension
-       Facility and the Execute-Extension Facility.
-
-  VxWorks
-
-     * GCC now supports the thread-local storage mechanism used on
-       VxWorks.
-
-  Xtensa
-
-     * GCC now supports thread-local storage (TLS) for Xtensa processor
-       configurations that include the Thread Pointer option. TLS also
-       requires support from the assembler and linker; this support is
-       provided in the GNU binutils beginning with version 2.19.
-
-Documentation improvements
-
-Other significant improvements
-
-GCC 4.4.1
-
-   This is the [13]list of problem reports (PRs) from GCC's bug tracking
-   system that are known to be fixed in the 4.4.1 release. This list might
-   not be complete (that is, it is possible that some PRs that have been
-   fixed are not listed here).
-
-GCC 4.4.2
-
-   This is the [14]list of problem reports (PRs) from GCC's bug tracking
-   system that are known to be fixed in the 4.4.2 release. This list might
-   not be complete (that is, it is possible that some PRs that have been
-   fixed are not listed here).
-
-GCC 4.4.3
-
-   This is the [15]list of problem reports (PRs) from GCC's bug tracking
-   system that are known to be fixed in the 4.4.3 release. This list might
-   not be complete (that is, it is possible that some PRs that have been
-   fixed are not listed here).
-
-   Please send FSF & GNU inquiries & questions to [16]gnu@gnu.org. There
-   are also [17]other ways to contact the FSF.
-
-   These pages are maintained by [18]the GCC team.
-
-
-    For questions related to the use of GCC, please consult these web
-    pages and the [19]GCC manuals. If that fails, the
-    [20]gcc-help@gcc.gnu.org mailing list might help.
-    Please send comments on these web pages and the development of GCC to
-    our developer mailing list at [21]gcc@gnu.org or [22]gcc@gcc.gnu.org.
-    All of our lists have [23]public archives.
-
-   Copyright (C) Free Software Foundation, Inc., 51 Franklin St, Fifth
-   Floor, Boston, MA 02110, USA.
-
-   Verbatim copying and distribution of this entire article is permitted
-   in any medium, provided this notice is preserved.
-   Last modified 2010-01-21 [24]Valid XHTML 1.0
-
-References
-
-   1. http://gcc.gnu.org/gcc-4.4/changes.html#4.4.3
-   2. http://gcc.gnu.org/gcc-4.3/changes.html#obsoleted
-   3. http://gcc.gnu.org/gcc-4.4/porting_to.html
-   4. http://gcc.gnu.org/wiki/Graphite
-   5. http://openmp.org/wp/openmp-specifications/
-   6. http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1040.pdf
-   7. http://gcc.gnu.org/gcc-4.4/cxx0x_status.html
-   8. http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#id476343
-   9. http://gcc.gnu.org/onlinedocs/gfortran/Preprocessing-Options.html
-  10. http://gcc.gnu.org/onlinedocs/gfortran/Error-and-Warning-Options.html#index-g_t_0040code_007bWarray-temporaries_007d-125
-  11. http://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfcheck-array-temporaries_007d-221
-  12. http://gcc.gnu.org/onlinedocs/gfortran/Fortran-Dialect-Options.html#index-g_t_0040code_007bbackslash_007d-34
-  13. http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.1
-  14. http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.2
-  15. http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.3
-  16. mailto:gnu@gnu.org
-  17. http://www.gnu.org/home.html#ContactInfo
-  18. http://gcc.gnu.org/about.html
-  19. http://gcc.gnu.org/onlinedocs/
-  20. mailto:gcc-help@gcc.gnu.org
-  21. mailto:gcc@gnu.org
-  22. mailto:gcc@gcc.gnu.org
-  23. http://gcc.gnu.org/lists.html
-  24. http://validator.w3.org/check/referer
-======================================================================
-http://gcc.gnu.org/gcc-4.3/index.html
-                           GCC 4.3 Release Series
-
-   January 24, 2009
-
-   The [1]GNU project and the GCC developers are pleased to announce the
-   release of GCC 4.3.4.
-
-   This release is a bug-fix release, containing fixes for regressions in
-   GCC 4.3.3 relative to previous releases of GCC.
-
-Release History
-
-   GCC 4.3.4
-          August 4, 2009 ([2]changes)
-
-   GCC 4.3.3
-          January 24, 2009 ([3]changes)
-
-   GCC 4.3.2
-          August 27, 2008 ([4]changes)
-
-   GCC 4.3.1
-          June 6, 2008 ([5]changes)
-
-   GCC 4.3.0
-          March 5, 2008 ([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 or [12]our SVN server.
-
-   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 developer mailing list at [18]gcc@gnu.org or [19]gcc@gcc.gnu.org.
-    All of our lists have [20]public archives.
-
-   Copyright (C) Free Software Foundation, Inc., 51 Franklin St, Fifth
-   Floor, Boston, MA 02110, USA.
-
-   Verbatim copying and distribution of this entire article is permitted
-   in any medium, provided this notice is preserved.
-   Last modified 2009-10-15 [21]Valid XHTML 1.0
-
-References
-
-   1. http://www.gnu.org/
-   2. http://gcc.gnu.org/gcc-4.3/changes.html
-   3. http://gcc.gnu.org/gcc-4.3/changes.html
-   4. http://gcc.gnu.org/gcc-4.3/changes.html
-   5. http://gcc.gnu.org/gcc-4.3/changes.html
-   6. http://gcc.gnu.org/gcc-4.3/changes.html
-   7. http://gcc.gnu.org/gcc-4.3/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://gcc.gnu.org/svn.html
-  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://gcc.gnu.org/lists.html
-  21. http://validator.w3.org/check/referer
-======================================================================
-http://gcc.gnu.org/gcc-4.3/changes.html
-                           GCC 4.3 Release Series
-                      Changes, New Features, and Fixes
-
-   The latest release in the 4.3 release series is [1]GCC 4.3.4.
-
-Caveats
-
-     * GCC requires the [2]GMP and [3]MPFR libraries for building all the
-       various front-end languages it supports. See the [4]prerequisites
-       page for version requirements.
-     * ColdFire targets now treat long double as having the same format as
-       double. In earlier versions of GCC, they used the 68881 long double
-       format instead.
-     * The m68k-uclinux target now uses the same calling conventions as
-       m68k-linux-gnu. You can select the original calling conventions by
-       configuring for m68k-uclinuxoldabi instead. Note that
-       m68k-uclinuxoldabi also retains the original 80-bit long double on
-       ColdFire targets.
-     * The -fforce-mem option has been removed because it has had no
-       effect in the last few GCC releases.
-     * The i386 -msvr3-shlib option has been removed since it is no longer
-       used.
-     * Fastcall for i386 has been changed not to pass aggregate arguments
-       in registers, following Microsoft compilers.
-     * Support for the AOF assembler has been removed from the ARM back
-       end; this affects only the targets arm-semi-aof and armel-semi-aof,
-       which are no longer recognized. We removed these targets without a
-       deprecation period because we discovered that they have been
-       unusable since GCC 4.0.0.
-     * Support for the TMS320C3x/C4x processor (targets c4x-* and tic4x-*)
-       has been removed. This support had been deprecated since GCC 4.0.0.
-     * Support for a number of older systems and recently unmaintained or
-       untested target ports of GCC has been declared obsolete in GCC 4.3.
-       Unless there is activity to revive them, the next release of GCC
-       will have their sources permanently removed.
-       All GCC ports for the following processor architectures have been
-       declared obsolete:
-          + Morpho MT (mt-*)
-       The following aliases for processor architectures have been
-       declared obsolete. Users should use the indicated generic target
-       names instead, with compile-time options such as -mcpu or
-       configure-time options such as --with-cpu to control the
-       configuration more precisely.
-          + strongarm*-*-*, ep9312*-*-*, xscale*-*-* (use arm*-*-*
-            instead).
-          + parisc*-*-* (use hppa*-*-* instead).
-          + m680[012]0-*-* (use m68k-*-* instead).
-       All GCC ports for the following operating systems have been
-       declared obsolete:
-          + BeOS (*-*-beos*)
-          + kaOS (*-*-kaos*)
-          + GNU/Linux using the a.out object format (*-*-linux*aout*)
-          + GNU/Linux using version 1 of the GNU C Library
-            (*-*-linux*libc1*)
-          + Solaris versions before Solaris 7 (*-*-solaris2.[0-6],
-            *-*-solaris2.[0-6].*)
-          + Miscellaneous System V (*-*-sysv*)
-          + WindISS (*-*-windiss*)
-       Also, those for some individual systems on particular architectures
-       have been obsoleted:
-          + UNICOS/mk on DEC Alpha (alpha*-*-unicosmk*)
-          + CRIS with a.out object format (cris-*-aout)
-          + BSD 4.3 on PA-RISC (hppa1.1-*-bsd*)
-          + OSF/1 on PA-RISC (hppa1.1-*-osf*)
-          + PRO on PA-RISC (hppa1.1-*-pro*)
-          + Sequent PTX on IA32 (i[34567]86-sequent-ptx4*,
-            i[34567]86-sequent-sysv4*)
-          + SCO Open Server 5 on IA32 (i[34567]86-*-sco3.2v5*)
-          + UWIN on IA32 (i[34567]86-*-uwin*) (support for UWIN as a host
-            was previously [5]removed in 2001, leaving only the support
-            for UWIN as a target now being deprecated)
-          + ChorusOS on PowerPC (powerpc-*-chorusos*)
-          + All VAX configurations apart from NetBSD and OpenBSD
-            (vax-*-bsd*, vax-*-sysv*, vax-*-ultrix*)
-     * The [6]-Wconversion option has been modified. Its purpose now is to
-       warn for implicit conversions that may alter a value. This new
-       behavior is available for both C and C++. Warnings about
-       conversions between signed and unsigned integers can be disabled by
-       using -Wno-sign-conversion. In C++, they are disabled by default
-       unless -Wsign-conversion is explicitly requested. The old behavior
-       of -Wconversion, that is, warn for prototypes causing a type
-       conversion that is different from what would happen to the same
-       argument in the absence of a prototype, has been moved to a new
-       option -Wtraditional-conversion, which is only available for C.
-     * The -m386, -m486, -mpentium and -mpentiumpro tuning options have
-       been removed because they were deprecated for more than 3 GCC major
-       releases. Use -mtune=i386, -mtune=i486, -mtune=pentium or
-       -mtune=pentiumpro as a replacement.
-     * The -funsafe-math-optimizations option now automatically turns on
-       -fno-trapping-math in addition to -fno-signed-zeros, as it enables
-       reassociation and thus may introduce or remove traps.
-     * The -ftree-vectorize option is now on by default under -O3. In
-       order to generate code for a SIMD extension, it has to be enabled
-       as well: use -maltivec for PowerPC platforms and -msse/-msse2 for
-       i?86 and x86_64.
-     * More information on porting to GCC 4.3 from previous versions of
-       GCC can be found in the [7]porting guide for this release.
-
-General Optimizer Improvements
-
-     * The GCC middle-end has been integrated with the [8]MPFR library.
-       This allows GCC to evaluate and replace at compile-time calls to
-       built-in math functions having constant arguments with their
-       mathematically equivalent results. In making use of [9]MPFR, GCC
-       can generate correct results regardless of the math library
-       implementation or floating point precision of the host platform.
-       This also allows GCC to generate identical results regardless of
-       whether one compiles in native or cross-compile configurations to a
-       particular target. The following built-in functions take advantage
-       of this new capability: acos, acosh, asin, asinh, atan2, atan,
-       atanh, cbrt, cos, cosh, drem, erf, erfc, exp10, exp2, exp, expm1,
-       fdim, fma, fmax, fmin, gamma_r, hypot, j0, j1, jn, lgamma_r, log10,
-       log1p, log2, log, pow10, pow, remainder, remquo, sin, sincos, sinh,
-       tan, tanh, tgamma, y0, y1 and yn. The float and long double
-       variants of these functions (e.g. sinf and sinl) are also handled.
-       The sqrt and cabs functions with constant arguments were already
-       optimized in prior GCC releases. Now they also use [10]MPFR.
-     * A new forward propagation pass on RTL was added. The new pass
-       replaces several slower transformations, resulting in compile-time
-       improvements as well as better code generation in some cases.
-     * A new command-line switch -frecord-gcc-switches has been added to
-       GCC, although it is only enabled for some targets. The switch
-       causes the command line that was used to invoke the compiler to be
-       recorded into the object file that is being created. The exact
-       format of this recording is target and binary file format
-       dependent, but it usually takes the form of a note section
-       containing ASCII text. The switch is related to the -fverbose-asm
-       switch, but that one only records the information in the assembler
-       output file as comments, so the information never reaches the
-       object file.
-     * The inliner heuristic is now aware of stack frame consumption. New
-       command-line parameters --param large-stack-frame and --param
-       large-stack-frame-growth can be used to limit stack frame size
-       growth caused by inlining.
-     * During feedback directed optimizations, the expected block size the
-       memcpy, memset and bzero functions operate on is discovered and for
-       cases of commonly used small sizes, specialized inline code is
-       generated.
-     * __builtin_expect no longer requires its argument to be a compile
-       time constant.
-     * Interprocedural optimization was reorganized to work on functions
-       in SSA form. This enables more precise and cheaper dataflow
-       analysis and makes writing interprocedural optimizations easier.
-       The following improvements have been implemented on top of this
-       framework:
-          + Pre-inline optimization: Selected local optimization passes
-            are run before the inliner (and other interprocedural passes)
-            are executed. This significantly improves the accuracy of code
-            growth estimates used by the inliner and reduces the overall
-            memory footprint for large compilation units.
-          + Early inlining (a simple bottom-up inliner pass inlining only
-            functions whose body is smaller than the expected call
-            overhead) is now executed with the early optimization passes,
-            thus inlining already optimized function bodies into an
-            unoptimized function that is subsequently optimized by early
-            optimizers. This enables the compiler to quickly eliminate
-            abstraction penalty in C++ programs.
-          + Interprocedural constant propagation now operate on SSA form
-            increasing accuracy of the analysis.
-     * A new internal representation for GIMPLE statements has been
-       contributed, resulting in compile-time memory savings.
-     * The vectorizer was enhanced to support vectorization of outer
-       loops, intra-iteration parallelism (loop-aware SLP), vectorization
-       of strided accesses and loops with multiple data-types. Run-time
-       dependency testing using loop versioning was added. The cost model,
-       turned on by -fvect-cost-model, was developed.
-
-New Languages and Language specific improvements
-
-     * We have added new command-line options
-       -finstrument-functions-exclude-function-list and
-       -finstrument-functions-exclude-file-list. They provide more control
-       over which functions are annotated by the -finstrument-functions
-       option.
-
-  C family
-
-     * Implicit conversions between generic vector types are now only
-       permitted when the two vectors in question have the same number of
-       elements and compatible element types. (Note that the restriction
-       involves compatible element types, not implicitly-convertible
-       element types: thus, a vector type with element type int may not be
-       implicitly converted to a vector type with element type unsigned
-       int.) This restriction, which is in line with specifications for
-       SIMD architectures such as AltiVec, may be relaxed using the flag
-       -flax-vector-conversions. This flag is intended only as a
-       compatibility measure and should not be used for new code.
-     * -Warray-bounds has been added and is now enabled by default for
-       -Wall . It produces warnings for array subscripts that can be
-       determined at compile time to be always out of bounds.
-       -Wno-array-bounds will disable the warning.
-     * The constructor and destructor function attributes now accept
-       optional priority arguments which control the order in which the
-       constructor and destructor functions are run.
-     * New [11]command-line options -Wtype-limits,
-       -Wold-style-declaration, -Wmissing-parameter-type, -Wempty-body,
-       -Wclobbered and -Wignored-qualifiers have been added for finer
-       control of the diverse warnings enabled by -Wextra.
-     * A new function attribute alloc_size has been added to mark up
-       malloc style functions. For constant sized allocations this can be
-       used to find out the size of the returned pointer using the
-       __builtin_object_size() function for buffer overflow checking and
-       similar. This supplements the already built-in malloc and calloc
-       constant size handling.
-     * Integer constants written in binary are now supported as a GCC
-       extension. They consist of a prefix 0b or 0B, followed by a
-       sequence of 0 and 1 digits.
-     * A new predefined macro __COUNTER__ has been added. It expands to
-       sequential integral values starting from 0. In conjunction with the
-       ## operator, this provides a convenient means to generate unique
-       identifiers.
-     * A new command-line option -fdirectives-only has been added. It
-       enables a special preprocessing mode which improves the performance
-       of applications like distcc and ccache.
-     * Fixed-point data types and operators have been added. They are
-       based on Chapter 4 of the Embedded-C specification (n1169.pdf).
-       Currently, only MIPS targets are supported.
-     * Decimal floating-point arithmetic based on draft ISO/IEC TR 24732,
-       N1241, is now supported as a GCC extension to C for targets
-       i[34567]86-*-linux-gnu, powerpc*-*-linux-gnu, s390*-ibm-linux-gnu,
-       and x86_64-*-linux-gnu. The feature introduces new data types
-       _Decimal32, _Decimal64, and _Decimal128 with constant suffixes DF,
-       DD, and DL.
-
-  C++
-
-     * [12]Experimental support for the upcoming ISO C++ standard, C++0x.
-     * -Wc++0x-compat has been added and is now enabled by default for
-       -Wall. It produces warnings for constructs whose meaning differs
-       between ISO C++ 1998 and C++0x.
-     * The -Wparentheses option now works for C++ as it does for C. It
-       warns if parentheses are omitted when operators with confusing
-       precedence are nested. It also warns about ambiguous else
-       statements. Since -Wparentheses is enabled by -Wall, this may cause
-       additional warnings with existing C++ code which uses -Wall. These
-       new warnings may be disabled by using -Wall -Wno-parentheses.
-     * The -Wmissing-declarations now works for C++ as it does for C.
-     * The -fvisibility-ms-compat flag was added, to make it easier to
-       port larger projects using shared libraries from Microsoft's Visual
-       Studio to ELF and Mach-O systems.
-     * C++ attribute handling has been overhauled for template arguments
-       (ie dependent types). In particular, __attribute__((aligned(T)));
-       works for C++ types.
-
-    Runtime Library (libstdc++)
-
-     * [13]Experimental support for the upcoming ISO C++ standard, C++0x.
-     * Support for TR1 mathematical special functions and regular
-       expressions. ([14]Implementation status of TR1)
-     * Default what implementations give more elaborate exception strings
-       for bad_cast, bad_typeid, bad_exception, and bad_alloc.
-     * Header dependencies have been streamlined, reducing unnecessary
-       includes and pre-processed bloat.
-     * Variadic template implementations of items in <tuple> and
-       <functional>.
-     * An experimental [15]parallel mode has been added. This is a
-       parallel implementation of many C++ Standard library algorithms,
-       like std::accumulate, std::for_each, std::transform, or std::sort,
-       to give but four examples. These algorithms can be substituted for
-       the normal (sequential) libstdc++ algorithms on a piecemeal basis,
-       or all existing algorithms can be transformed via the
-       -D_GLIBCXX_PARALLEL macro.
-     * Debug mode versions of classes in <unordered_set> and
-       <unordered_map>.
-     * Formal deprecation of <ext/hash_set> and <ext/hash_map>, which are
-       now <backward/hash_set> and <backward/hash_map>. This code:
-    #include <ext/hash_set>
-    __gnu_cxx::hash_set<int> s;
-
-       Can be transformed (in order of preference) to:
-    #include <tr1/unordered_set>
-    std::tr1::unordered_set<int> s;
-
-       or
-    #include <backward/hash_set>
-    __gnu_cxx::hash_set<int> s;
-
-       Similar transformations apply to __gnu_cxx::hash_map,
-       __gnu_cxx::hash_multimap, __gnu_cxx::hash_set,
-       __gnu_cxx::hash_multiset.
-
-  Fortran
-
-     * Due to the fact that the [16]GMP and [17]MPFR libraries are
-       required for all languages, Fortran is no longer special in this
-       regard and is available by default.
-     * The [18]-fexternal-blas option has been added, which generates
-       calls to BLAS routines for intrinsic matrix operations such as
-       matmul rather than using the built-in algorithms.
-     * Support to give a backtrace (compiler flag -fbacktrace or
-       environment variable GFORTRAN_ERROR_BACKTRACE; on glibc systems
-       only) or a core dump (-fdump-core, GFORTRAN_ERROR_DUMPCORE) when a
-       run-time error occured.
-     * GNU Fortran now defines __GFORTRAN__ when it runs the C
-       preprocessor (CPP).
-     * The [19]-finit-local-zero, -finit-real, -finit-integer,
-       -finit-character, and -finit-logical options have been added, which
-       can be used to initialize local variables.
-     * The intrinsic procedures [20]GAMMA and [21]LGAMMA have been added,
-       which calculate the Gamma function and its logarithm. Use EXTERNAL
-       gamma if you want to use your own gamma function.
-     * GNU Fortran now regards the backslash character as literal (as
-       required by the Fortran 2003 standard); using [22]-fbackslash GNU
-       Fortran interprets backslashes as C-style escape characters.
-     * The [23]interpretation of binary, octal and hexadecimal (BOZ)
-       literal constants has been changed. Before they were always
-       interpreted as integer; now they are bit-wise transferred as
-       argument of INT, REAL, DBLE and CMPLX as required by the Fortran
-       2003 standard, and for real and complex variables in DATA
-       statements or when directly assigned to real and complex variables.
-       Everywhere else and especially in expressions they are still
-       regarded as integer constants.
-     * Fortran 2003 support has been extended:
-          + Intrinsic statements IMPORT, PROTECTED, VALUE and VOLATILE
-          + Pointer intent
-          + Intrinsic module ISO_ENV_FORTRAN
-          + Interoperability with C (ISO C Bindings)
-          + ABSTRACT INTERFACES and PROCEDURE statements (without POINTER
-            attribute)
-          + Fortran 2003 BOZ
-
-  Java (GCJ)
-
-     * gcj now uses the Eclipse Java compiler for its Java parsing needs.
-       This enables the use of all 1.5 language features, and fixes most
-       existing front end bugs.
-     * libgcj now supports all 1.5 language features which require runtime
-       support: foreach, enum, annotations, generics, and auto-boxing.
-     * We've made many changes to the tools shipped with gcj.
-          + The old jv-scan tool has been removed. This tool never really
-            worked properly. There is no replacement.
-          + gcjh has been rewritten. Some of its more obscure options no
-            longer work, but are still recognized in an attempt at
-            compatibility. gjavah is a new program with similar
-            functionality but different command-line options.
-          + grmic and grmiregistry have been rewritten. grmid has been
-            added.
-          + gjar replaces the old fastjar.
-          + gjarsigner (used for signing jars), gkeytool (used for key
-            management), gorbd (for CORBA), gserialver (computes
-            serialization UIDs), and gtnameserv (also for CORBA) are now
-            installed.
-     * The ability to dump the contents of the java run time heap to a
-       file for off-line analysis has been added. The heap dumps may be
-       analyzed with the new gc-analyze tool. They may be generated on
-       out-of-memory conditions or on demand and are controlled by the new
-       run time class gnu.gcj.util.GCInfo.
-     * java.util.TimeZone can now read files from /usr/share/zoneinfo to
-       provide correct, updated, timezone information. This means that
-       packagers no longer have to update libgcj when a time zone change
-       is published.
-
-New Targets and Target Specific Improvements
-
-  IA-32/x86-64
-
-     * Tuning for Intel Core 2 processors is available via -mtune=core2
-       and -march=core2.
-     * Tuning for AMD Geode processors is available via -mtune=geode and
-       -march=geode.
-     * Code generation of block move (memcpy) and block set (memset) was
-       rewritten. GCC can now pick the best algorithm (loop, unrolled
-       loop, instruction with rep prefix or a library call) based on the
-       size of the block being copied and the CPU being optimized for. A
-       new option -minline-stringops-dynamically has been added. With this
-       option string operations of unknown size are expanded such that
-       small blocks are copied by in-line code, while for large blocks a
-       library call is used. This results in faster code than
-       -minline-all-stringops when the library implementation is capable
-       of using cache hierarchy hints. The heuristic choosing the
-       particular algorithm can be overwritten via -mstringop-strategy.
-       Newly also memset of values different from 0 is inlined.
-     * GCC no longer places the cld instruction before string operations.
-       Both i386 and x86-64 ABI documents mandate the direction flag to be
-       clear at the entry of a function. It is now invalid to set the flag
-       in asm statement without reseting it afterward.
-     * Support for SSSE3 built-in functions and code generation are
-       available via -mssse3.
-     * Support for SSE4.1 built-in functions and code generation are
-       available via -msse4.1.
-     * Support for SSE4.2 built-in functions and code generation are
-       available via -msse4.2.
-     * Both SSE4.1 and SSE4.2 support can be enabled via -msse4.
-     * A new set of options -mpc32, -mpc64 and -mpc80 have been added to
-       allow explicit control of x87 floating point precision.
-     * Support for __float128 (TFmode) IEEE quad type and corresponding
-       TCmode IEEE complex quad type is available via the soft-fp library
-       on x86_64 targets. This includes basic arithmetic operations
-       (addition, subtraction, negation, multiplication and division) on
-       __float128 real and TCmode complex values, the full set of IEEE
-       comparisons between __float128 values, conversions to and from
-       float, double and long double floating point types, as well as
-       conversions to and from signed or unsigned integer, signed or
-       unsigned long integer and signed or unsigned quad (TImode) integer
-       types. Additionally, all operations generate the full set of IEEE
-       exceptions and support the full set of IEEE rounding modes.
-     * GCC can now utilize the ACML library for vectorizing calls to a set
-       of C99 functions on x86_64 if -mveclibabi=acml is specified and you
-       link to an ACML ABI compatible library.
-
-  ARM
-
-     * Compiler and Library support for Thumb-2 and the ARMv7 architecture
-       has been added.
-
-  CRIS
-
-    New features
-
-     * Compiler and Library support for the CRIS v32 architecture, as
-       found in Axis Communications ETRAX FS and ARTPEC-3 chips, has been
-       added.
-
-    Configuration changes
-
-     * The cris-*-elf target now includes support for CRIS v32, including
-       libraries, through the -march=v32 option.
-     * A new crisv32-*-elf target defaults to generate code for CRIS v32.
-     * A new crisv32-*-linux* target defaults to generate code for CRIS
-       v32.
-     * The cris-*-aout target has been obsoleted.
-
-    Improved support for built-in functions
-
-     * GCC can now use the lz and swapwbr instructions to implement the
-       __builtin_clz, __builtin_ctz and __builtin_ffs family of functions.
-     * __builtin_bswap32 is now implemented using the swapwb instruction,
-       when available.
-
-  m68k and ColdFire
-
-    New features
-
-     * Support for several new ColdFire processors has been added. You can
-       generate code for them using the new -mcpu option.
-     * All targets now support ColdFire processors.
-     * m68k-uclinux targets have improved support for C++ constructors and
-       destructors, and for shared libraries.
-     * It is now possible to set breakpoints on the first or last line of
-       a function, even if there are no statements on that line.
-
-    Optimizations
-
-     * Support for sibling calls has been added.
-     * More use is now made of the ColdFire mov3q instruction.
-     * __builtin_clz is now implemented using the ff1 ColdFire
-       instruction, when available.
-     * GCC now honors the -m68010 option. 68010 code now uses clr rather
-       than move to zero volatile memory.
-     * 68020 targets and above can now use symbol(index.size*scale)
-       addresses for indexed array accesses. Earlier compilers would
-       always load the symbol into a base register first.
-
-    Configuration changes
-
-     * All m68k and ColdFire targets now allow the default processor to be
-       set at configure time using --with-cpu.
-     * A --with-arch configuration option has been added. This option
-       allows you to restrict a target to ColdFire or non-ColdFire
-       processors.
-
-    Preprocessor macros
-
-     * An __mcfv*__ macro is now defined for all ColdFire targets.
-       (Earlier versions of GCC only defined __mcfv4e__.)
-     * __mcf_cpu_*, __mcf_family_* and __mcffpu__ macros have been added.
-     * All targets now define __mc68010 and __mc68010__ when generating
-       68010 code.
-
-    Command-line changes
-
-     * New command-line options -march, -mcpu, -mtune and -mhard-float
-       have been added. These options apply to both m68k and ColdFire
-       targets.
-     * -mno-short, -mno-bitfield and -mno-rtd are now accepted as negative
-       versions of -mshort, etc.
-     * -fforce-addr has been removed. It is now ignored by the compiler.
-
-    Other improvements
-
-     * ColdFire targets now try to maintain a 4-byte-aligned stack where
-       possible.
-     * m68k-uclinux targets now try to avoid situations that lead to the
-       load-time error: BINFMT_FLAT: reloc outside program.
-
-  MIPS
-
-    Changes to existing configurations
-
-     * libffi and libjava now support all three GNU/Linux ABIs: o32, n32
-       and n64. Every GNU/Linux configuration now builds these libraries
-       by default.
-     * GNU/Linux configurations now generate -mno-shared code unless
-       overridden by -fpic, -fPIC, -fpie or -fPIE.
-     * mipsisa32*-linux-gnu configurations now generate hard-float code by
-       default, just like other mipsisa32* and mips*-linux-gnu
-       configurations. You can build a soft-float version of any
-       mips*-linux-gnu configuration by passing --with-float=soft to
-       configure.
-     * mips-wrs-vxworks now supports run-time processes (RTPs).
-
-    Changes to existing command-line options
-
-     * The -march and -mtune options no longer accept 24k as a processor
-       name. Please use 24kc, 24kf2_1 or 24kf1_1 instead.
-     * The -march and -mtune options now accept 24kf2_1, 24kef2_1 and
-       34kf2_1 as synonyms for 24kf, 24kef and 34kf respectively. The
-       options also accept 24kf1_1, 24kef1_1 and 34kf1_1 as synonyms for
-       24kx, 24kex and 34kx.
-
-    New configurations
-
-   GCC now supports the following configurations:
-     * mipsisa32r2*-linux-gnu*, which generates MIPS32 revision 2 code by
-       default. Earlier releases also recognized this configuration, but
-       they treated it in the same way as mipsisa32*-linux-gnu*. Note that
-       you can customize any mips*-linux-gnu* configuration to a
-       particular ISA or processor by passing an appropriate --with-arch
-       option to configure.
-     * mipsisa*-sde-elf*, which provides compatibility with MIPS
-       Technologies' SDE toolchains. The configuration uses the SDE
-       libraries by default, but you can use it like other newlib-based
-       ELF configurations by passing --with-newlib to configure. It is the
-       only configuration besides mips64vr*-elf* to build MIPS16 as well
-       as non-MIPS16 libraries.
-     * mipsisa*-elfoabi*, which is similar to the general mipsisa*-elf*
-       configuration, but uses the o32 and o64 ABIs instead of the 32-bit
-       and 64-bit forms of the EABI.
-
-    New processors and application-specific extensions
-
-     * Support for the SmartMIPS ASE is available through the new
-       -msmartmips option.
-     * Support for revision 2 of the DSP ASE is available through the new
-       -mdspr2 option. A new preprocessor macro called __mips_dsp_rev
-       indicates the revision of the ASE in use.
-     * Support for the 4KS and 74K families of processors is available
-       through the -march and -mtune options.
-
-    Improved support for built-in functions
-
-     * GCC can now use load-linked, store-conditional and sync
-       instructions to implement atomic built-in functions such as
-       __sync_fetch_and_add. The memory reference must be 4 bytes wide for
-       32-bit targets and either 4 or 8 bytes wide for 64-bit targets.
-     * GCC can now use the clz and dclz instructions to implement the
-       __builtin_ctz and __builtin_ffs families of functions.
-     * There is a new __builtin___clear_cache function for flushing the
-       instruction cache. GCC expands this function inline on MIPS32
-       revision 2 targets, otherwise it calls the function specified by
-       -mcache-flush-func.
-
-    MIPS16 improvements
-
-     * GCC can now compile objects that contain a mixture of MIPS16 and
-       non-MIPS16 code. There are two new attributes, mips16 and nomips16,
-       for specifying which mode a function should use.
-     * A new option called -minterlink-mips16 makes non-MIPS16 code
-       link-compatible with MIPS16 code.
-     * After many bug fixes, the long-standing MIPS16 -mhard-float support
-       should now work fairly reliably.
-     * GCC can now use the MIPS16e save and restore instructions.
-     * -fsection-anchors now works in MIPS16 mode. MIPS16 code compiled
-       with -G0 -fsection-anchors is often smaller than code compiled with
-       -G8. However, please note that you must usually compile all objects
-       in your application with the same -G option; see the documentation
-       of -G for details.
-     * A new option called-mcode-readable specifies which instructions are
-       allowed to load from the code segment. -mcode-readable=yes is the
-       default and says that any instruction may load from the code
-       segment. The other alternatives are -mcode-readable=pcrel, which
-       says that only PC-relative MIPS16 instructions may load from the
-       code segment, and -mcode-readable=no, which says that no
-       instruction may do so. Please see the documentation for more
-       details, including example uses.
-
-    Small-data improvements
-
-   There are three new options for controlling small data:
-     * -mno-extern-sdata, which disables small-data accesses for
-       externally-defined variables. Code compiled with -Gn
-       -mno-extern-sdata will be link-compatible with any -G setting
-       between -G0 and -Gn inclusive.
-     * -mno-local-sdata, which disables the use of small-data sections for
-       data that is not externally visible. This option can be a useful
-       way of reducing small-data usage in less performance-critical parts
-       of an application.
-     * -mno-gpopt, which disables the use of the $gp register while still
-       honoring the -G limit when placing externally-visible data. This
-       option implies -mno-extern-sdata and -mno-local-sdata and it can be
-       useful in situations where $gp does not necessarily hold the
-       expected value.
-
-    Miscellaneous improvements
-
-     * There is a new option called -mbranch-cost for tweaking the
-       perceived cost of branches.
-     * If GCC is configured to use a version of GAS that supports the
-       .gnu_attribute directive, it will use that directive to record
-       certain properties of the output code. .gnu_attribute is new to GAS
-       2.18.
-     * There are two new function attributes, near and far, for overriding
-       the command-line setting of -mlong-calls on a function-by-function
-       basis.
-     * -mfp64, which previously required a 64-bit target, now works with
-       MIPS32 revision 2 targets as well. The mipsisa*-elfoabi* and
-       mipsisa*-sde-elf* configurations provide suitable library support.
-     * GCC now recognizes the -mdmx and -mmt options and passes them down
-       to the assembler. It does nothing else with the options at present.
-
-  SPU (Synergistic Processor Unit) of the Cell Broadband Engine Architecture
-  (BEA)
-
-     * Support has been added for this new architecture.
-
-  RS6000 (POWER/PowerPC)
-
-     * Support for the PowerPC 750CL paired-single instructions has been
-       added with a new powerpc-*-linux*paired* target configuration. It
-       is enabled by an associated -mpaired option and can be accessed
-       using new built-in functions.
-     * Support for auto-detecting architecture and system configuration to
-       auto-select processor optimization tuning.
-     * Support for VMX on AIX 5.3 has been added.
-     * Support for AIX Version 6.1 has been added.
-
-  S/390, zSeries and System z9
-
-     * Support for the IBM System z9 EC/BC processor (z9 GA3) has been
-       added. When using the -march=z9-ec option, the compiler will
-       generate code making use of instructions provided by the decimal
-       floating point facility and the floating point conversion facility
-       (pfpo). Besides the instructions used to implement decimal floating
-       point operations these facilities also contain instructions to move
-       between general purpose and floating point registers and to modify
-       and copy the sign-bit of floating point values.
-     * When the -march=z9-ec option is used the new
-       -mhard-dfp/-mno-hard-dfp options can be used to specify whether the
-       decimal floating point hardware instructions will be used or not.
-       If none of them is given the hardware support is enabled by
-       default.
-     * The -mstack-guard option can now be omitted when using stack
-       checking via -mstack-size in order to let GCC choose a sensible
-       stack guard value according to the frame size of each function.
-     * Various changes to improve performance of generated code have been
-       implemented, including:
-          + The condition code set by an add logical with carry
-            instruction is now available for overflow checks like: a + b +
-            carry < b.
-          + The test data class instruction is now used to implement
-            sign-bit and infinity checks of binary and decimal floating
-            point numbers.
-
-  Xtensa
-
-     * Stack unwinding for exception handling now uses by default a
-       specialized version of DWARF unwinding. This is not
-       binary-compatible with the setjmp/longjmp (sjlj) unwinding used for
-       Xtensa with previous versions of GCC.
-     * For Xtensa processors that include the Conditional Store option,
-       the built-in functions for atomic memory access are now implemented
-       using S32C1I instructions.
-     * If the Xtensa NSA option is available, GCC will use it to implement
-       the __builtin_ctz and __builtin_clz functions.
-
-Documentation improvements
-
-     * Existing libstdc++ documentation has been edited and restructured
-       into a single DocBook XML manual. The results can be viewed online
-       [24]here.
-
-Other significant improvements
-
-     * The compiler's --help command-line option has been extended so that
-       it now takes an optional set of arguments. These arguments restrict
-       the information displayed to specific classes of command-line
-       options, and possibly only a subset of those options. It is also
-       now possible to replace the descriptive text associated with each
-       displayed option with an indication of its current value, or for
-       binary options, whether it has been enabled or disabled.
-       Here are some examples. The following will display all the options
-       controlling warning messages:
-      --help=warnings
-
-       Whereas this will display all the undocumented, target specific
-       options:
-      --help=target,undocumented
-
-       This sequence of commands will display the binary optimizations
-       that are enabled by -O3:
-      gcc -c -Q -O3 --help=optimizers > /tmp/O3-opts
-      gcc -c -Q -O2 --help=optimizers > /tmp/O2-opts
-      diff /tmp/O2-opts /tmp/O3-opts | grep enabled
-
-     * The configure options --with-pkgversion and --with-bugurl have been
-       added. These allow distributors of GCC to include a
-       distributor-specific string in manuals and --version output and to
-       specify the URL for reporting bugs in their versions of GCC.
-
-GCC 4.3.1
-
-   This is the [25]list of problem reports (PRs) from GCC's bug tracking
-   system that are known to be fixed in the 4.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).
-
-Target Specific Changes
-
-  IA-32/x86-64
-
-    ABI changes
-
-     * Starting with GCC 4.3.1, decimal floating point variables are
-       aligned to their natural boundaries when they are passed on the
-       stack for i386.
-
-    Command-line changes
-
-     * Starting with GCC 4.3.1, the -mcld option has been added to
-       automatically generate a cld instruction in the prologue of
-       functions that use string instructions. This option is used for
-       backward compatibility on some operating systems and can be enabled
-       by default for 32-bit x86 targets by configuring GCC with the
-       --enable-cld configure option.
-
-GCC 4.3.2
-
-   This is the [26]list of problem reports (PRs) from GCC's bug tracking
-   system that are known to be fixed in the 4.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).
-
-GCC 4.3.3
-
-   This is the [27]list of problem reports (PRs) from GCC's bug tracking
-   system that are known to be fixed in the 4.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).
-
-GCC 4.3.4
-
-   This is the [28]list of problem reports (PRs) from GCC's bug tracking
-   system that are known to be fixed in the 4.3.4 release. This list might
-   not be complete (that is, it is possible that some PRs that have been
-   fixed are not listed here).
-
-   Please send FSF & GNU inquiries & questions to [29]gnu@gnu.org. There
-   are also [30]other ways to contact the FSF.
-
-   These pages are maintained by [31]the GCC team.
-
-
-    For questions related to the use of GCC, please consult these web
-    pages and the [32]GCC manuals. If that fails, the
-    [33]gcc-help@gcc.gnu.org mailing list might help.
-    Please send comments on these web pages and the development of GCC to
-    our developer mailing list at [34]gcc@gnu.org or [35]gcc@gcc.gnu.org.
-    All of our lists have [36]public archives.
-
-   Copyright (C) Free Software Foundation, Inc., 51 Franklin St, Fifth
-   Floor, Boston, MA 02110, USA.
-
-   Verbatim copying and distribution of this entire article is permitted
-   in any medium, provided this notice is preserved.
-   Last modified 2009-08-13 [37]Valid XHTML 1.0
-
-References
-
-   1. http://gcc.gnu.org/gcc-4.3/changes.html#4.3.4
-   2. http://gmplib.org/
-   3. http://www.mpfr.org/
-   4. http://gcc.gnu.org/install/prerequisites.html
-   5. http://gcc.gnu.org/ml/gcc-announce/2001/msg00000.html
-   6. http://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#Warning-Options
-   7. http://gcc.gnu.org/gcc-4.3/porting_to.html
-   8. http://www.mpfr.org/
-   9. http://www.mpfr.org/
-  10. http://www.mpfr.org/
-  11. http://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html
-  12. http://gcc.gnu.org/gcc-4.3/cxx0x_status.html
-  13. http://gcc.gnu.org/gcc-4.3/cxx0x_status.html
-  14. http://gcc.gnu.org/onlinedocs/libstdc++/manual/bk01pt01ch01.html#m anual.intro.status.standard.tr1
-  15. http://gcc.gnu.org/onlinedocs/libstdc++/manual/parallel_mode.html
-  16. http://gmplib.org/
-  17. http://www.mpfr.org/
-  18. http://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html#Code-Gen-Options
-  19. http://gcc.gnu.org/onlinedocs/gfortran/Code-Gen-Options.html#index-g_t_0040code_007bfinit-local-zero_007d-167
-  20. http://gcc.gnu.org/onlinedocs/gcc-4.3.0/gfortran/GAMMA.html
-  21. http://gcc.gnu.org/onlinedocs/gcc-4.3.0/gfortran/LGAMMA.html
-  22. http://gcc.gnu.org/onlinedocs/gfortran/Fortran-Dialect-Options.html
-  23. http://gcc.gnu.org/onlinedocs/gfortran/BOZ-literal-constants.html
-  24. http://gcc.gnu.org/onlinedocs/libstdc++/
-  25. http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.1
-  26. http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.2
-  27. http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.3
-  28. http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.4
-  29. mailto:gnu@gnu.org
-  30. http://www.gnu.org/home.html#ContactInfo
-  31. http://gcc.gnu.org/about.html
-  32. http://gcc.gnu.org/onlinedocs/
-  33. mailto:gcc-help@gcc.gnu.org
-  34. mailto:gcc@gnu.org
-  35. mailto:gcc@gcc.gnu.org
-  36. http://gcc.gnu.org/lists.html
-  37. http://validator.w3.org/check/referer
-======================================================================
-http://gcc.gnu.org/gcc-4.2/index.html
-                           GCC 4.2 Release Series
-
-   May 19, 2008
-
-   The [1]GNU project and the GCC developers are pleased to announce the
-   release of GCC 4.2.4.
-
-   This release is a bug-fix release, containing fixes for regressions in
-   GCC 4.2.3 relative to previous releases of GCC.
-
-Release History
-
-   GCC 4.2.4
-          May 19, 2008 ([2]changes)
-
-   GCC 4.2.3
-          February 1, 2008 ([3]changes)
-
-   GCC 4.2.2
-          October 7, 2007 ([4]changes)
-
-   GCC 4.2.1
-          July 18, 2007 ([5]changes)
-
-   GCC 4.2.0
-          May 13, 2007 ([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 or [12]our SVN server.
-
-   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 developer mailing list at [18]gcc@gnu.org or [19]gcc@gcc.gnu.org.
-    All of our lists have [20]public archives.
-
-   Copyright (C) Free Software Foundation, Inc., 51 Franklin St, Fifth
-   Floor, Boston, MA 02110, USA.
-
-   Verbatim copying and distribution of this entire article is permitted
-   in any medium, provided this notice is preserved.
-   Last modified 2008-10-04 [21]Valid XHTML 1.0
-
-References
-
-   1. http://www.gnu.org/
-   2. http://gcc.gnu.org/gcc-4.2/changes.html
-   3. http://gcc.gnu.org/gcc-4.2/changes.html
-   4. http://gcc.gnu.org/gcc-4.2/changes.html
-   5. http://gcc.gnu.org/gcc-4.2/changes.html
-   6. http://gcc.gnu.org/gcc-4.2/changes.html
-   7. http://gcc.gnu.org/gcc-4.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://gcc.gnu.org/svn.html
-  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://gcc.gnu.org/lists.html
-  21. http://validator.w3.org/check/referer
-======================================================================
-http://gcc.gnu.org/gcc-4.2/changes.html
-                           GCC 4.2 Release Series
-                      Changes, New Features, and Fixes
-
-Caveats
-
-     * GCC no longer accepts the -fshared-data option. This option has had
-       no effect in any GCC 4 release; the targets to which the option
-       used to apply had been removed before GCC 4.0.
-
-General Optimizer Improvements
-
-     * New command-line options specify the possible relationships among
-       parameters and between parameters and global data. For example,
-       -fargument-noalias-anything specifies that arguments do not alias
-       any other storage.
-       Each language will automatically use whatever option is required by
-       the language standard. You should not need to use these options
-       yourself.
-
-New Languages and Language specific improvements
-
-     * [1]OpenMP is now supported for the C, C++ and Fortran compilers.
-     * New command-line options -fstrict-overflow and -Wstrict-overflow
-       have been added. -fstrict-overflow tells the compiler that it may
-       assume that the program follows the strict signed overflow
-       semantics permitted for the language: for C and C++ this means that
-       the compiler may assume that signed overflow does not occur. For
-       example, a loop like
-      for (i = 1; i > 0; i *= 2)
-
-       is presumably intended to continue looping until i overflows. With
-       -fstrict-overflow, the compiler may assume that signed overflow
-       will not occur, and transform this into an infinite loop.
-       -fstrict-overflow is turned on by default at -O2, and may be
-       disabled via -fno-strict-overflow. The -Wstrict-overflow option may
-       be used to warn about cases where the compiler assumes that signed
-       overflow will not occur. It takes five different levels:
-       -Wstrict-overflow=1 to 5. See the [2]documentation for details.
-       -Wstrict-overflow=1 is enabled by -Wall.
-     * The new command-line option -fno-toplevel-reorder directs GCC to
-       emit top-level functions, variables, and asm statements in the same
-       order that they appear in the input file. This is intended to
-       support existing code which relies on a particular ordering (for
-       example, code which uses top-level asm statements to switch
-       sections). For new code, it is generally better to use function and
-       variable attributes. The -fno-toplevel-reorder option may be used
-       for most cases which currently use -fno-unit-at-a-time. The
-       -fno-unit-at-a-time option will be removed in some future version
-       of GCC. If you know of a case which requires -fno-unit-at-a-time
-       which is not fixed by -fno-toplevel-reorder, please open a bug
-       report.
-
-  C family
-
-     * The pragma redefine_extname will now macro expand its tokens for
-       compatibility with SunPRO.
-     * In the next release of GCC, 4.3, -std=c99 or -std=gnu99 will direct
-       GCC to handle inline functions as specified in the C99 standard. In
-       preparation for this, GCC 4.2 will warn about any use of non-static
-       inline functions in gnu99 or c99 mode. This new warning may be
-       disabled with the new gnu_inline function attribute or the new
-       -fgnu89-inline command-line option. Also, GCC 4.2 and later will
-       define one of the preprocessor macros __GNUC_GNU_INLINE__ or
-       __GNUC_STDC_INLINE__ to indicate the semantics of inline functions
-       in the current compilation.
-     * A new command-line option -Waddress has been added to warn about
-       suspicious uses of memory addresses as, for example, using the
-       address of a function in a conditional expression, and comparisons
-       against the memory address of a string literal. This warning is
-       enabled by -Wall.
-
-  C++
-
-     * C++ visibility handling has been overhauled.
-       Restricted visiblity is propagated from classes to members, from
-       functions to local statics, and from templates and template
-       arguments to instantiations, unless the latter has explicitly
-       declared visibility.
-       The visibility attribute for a class must come between the
-       class-key and the name, not after the closing brace.
-       Attributes are now allowed for enums and elaborated-type-specifiers
-       that only declare a type.
-       Members of the anonymous namespace are now local to a particular
-       translation unit, along with any other declarations which use them,
-       though they are still treated as having external linkage for
-       language semantics.
-     * The (undocumented) extension which permitted templates with default
-       arguments to be bound to template template parameters with fewer
-       parameters has been removed. For example:
-        template <template <typename> class C>
-        void f(C<double>) {}
-
-        template <typename T, typename U = int>
-        struct S {};
-
-        template void f(S<double>);
-
-       is no longer accepted by G++. The reason this code is not accepted
-       is that S is a template with two parameters; therefore, it cannot
-       be bound to C which has only one parameter.
-     * The <?, >?, <?=, and >?= operators, deprecated in previous GCC
-       releases, have been removed.
-     * The command-line option -fconst-strings, deprecated in previous GCC
-       releases, has been removed.
-     * The configure variable enable-__cxa_atexit is now enabled by
-       default for more targets. Enabling this variable is necessary in
-       order for static destructors to be executed in the correct order,
-       but it depends upon the presence of a non-standard C library in the
-       target library in order to work. The variable is now enabled for
-       more targets which are known to have suitable C libraries.
-     * -Wextra will produce warnings for if statements with a semicolon as
-       the only body, to catch code like:
-         if (a);
-            return 1;
-         return 0;
-
-       To suppress the warning in valid cases, use { } instead.
-     * The C++ frontend now also produces strict aliasing warnings when
-       -fstrict-aliasing -Wstrict-aliasing is in effect.
-
-    Runtime Library (libstdc++)
-
-     * Added support for TR1 <random>, <complex>, and C compatibility
-       headers. In addition, a lock-free version of shared_ptr was
-       contributed as part of Phillip Jordan's Google Summer of Code
-       project on lock-free containers. ([3]Implementation status of TR1)
-     * In association with the Summer of Code work on lock-free
-       containers, the interface for atomic builtins was adjusted,
-       creating simpler alternatives for non-threaded code paths. Also,
-       usage was consolidated and all elements were moved from namespace
-       std to namespace__gnu_cxx. Affected interfaces are the functions
-       __exchange_and_add, __atomic_add, and the objects __mutex,
-       __recursive_mutex, and __scoped_lock.
-     * Support for versioning weak symbol names via namespace association
-       was added. However, as this changes the names of exported symbols,
-       this is turned off by default in the current ABI. Intrepid users
-       can enable this feature by using
-       --enable-symvers=gnu-versioned-namespace during configuration.
-     * Revised, simplified, and expanded policy-based associative
-       containers, including data types for tree and trie forms
-       (basic_tree, tree, trie), lists (list_update), and both
-       collision-chaining and probing hash-based containers
-       (basic_hash_table, cc_hash_table, gp_hash_table). More details per
-       the [4]documentation.
-     * The implementation of the debug mode was modified, whereby the
-       debug namespaces were nested inside of namespace std and namespace
-       __gnu_cxx in order to resolve some long standing corner cases
-       involving name lookup. Debug functionality from the policy-based
-       data structures was consolidated and enabled with the single macro,
-       _GLIBCXX_DEBUG. See PR 26142 for more information.
-     * Added extensions for type traits: __conditional_type,
-       __numeric_traits, __add_unsigned, __removed_unsigned, __enable_if.
-     * Added a typelist implementation for compile-time meta-programming.
-       Elements for typelist construction and operation can be found
-       within namespace __gnu_cxx::typelist.
-     * Added a new allocator, __gnu_cxx::throw_allocator, for testing
-       exception-safety.
-     * Enabled library-wide visibility control, allowing -fvisibility to
-       be used.
-     * Consolidated all nested namespaces and the conversion of
-       __gnu_internal implementation-private details to anonymous
-       namespaces whenever possible.
-     * Implemented LWG resolutions DR 431 and DR 538.
-
-  Fortran
-
-     * Support for allocatable components has been added (TR 15581 and
-       Fortran 2003).
-     * Support for the Fortran 2003 streaming IO extension has been added.
-     * The GNU Fortran compiler now uses 4-byte record markers by default
-       for unformatted files to be compatible with g77 and most other
-       compilers. The implementation allows for records greater than 2 GB
-       and is compatible with several other compilers. Older versions of
-       gfortran used 8-byte record markers by default (on most systems).
-       In order to change the length of the record markers, e.g. to read
-       unformatted files created by older gfortran versions, the
-       [5]-frecord-marker=8 option can be used.
-
-  Java (GCJ)
-
-     * A new command-line option -static-libgcj has been added for targets
-       that use a linker compatible with GNU Binutils. As its name
-       implies, this causes libgcj to be linked statically. In some cases
-       this causes the resulting executable to start faster and use less
-       memory than if the shared version of libgcj were used. However
-       caution should be used as it can also cause essential parts of the
-       library to be omitted. Some of these issues are discussed in:
-       [6]http://gcc.gnu.org/wiki/Statically_linking_libgcj
-     * fastjar is no longer bundled with GCC. To build libgcj, you will
-       need either InfoZIP (both zip and unzip) or an external jar
-       program. In the former case, the GCC build will install a jar shell
-       script that is based on InfoZIP and provides the same functionality
-       as fastjar.
-
-New Targets and Target Specific Improvements
-
-  IA-32/x86-64
-
-     * -mtune=generic can now be used to generate code running well on
-       common x86 chips. This includes AMD Athlon, AMD Opteron, Intel
-       Pentium-M, Intel Pentium 4 and Intel Core 2.
-     * -mtune=native and -march=native will produce code optimized for the
-       host architecture as detected using the cpuid instruction.
-     * Added a new command-line option -fstackrealign and and
-       __attribute__ ((force_align_arg_pointer)) to realign the stack at
-       runtime. This allows functions compiled with a vector-aligned stack
-       to be invoked from legacy objects that keep only word-alignment.
-
-  SPARC
-
-     * The default CPU setting has been changed from V7 to V9 in 32-bit
-       mode on Solaris 7 and above. This is already the case in 64-bit
-       mode. It can be overridden by specifying --with-cpu at configure
-       time.
-     * Back-end support of built-in functions for atomic memory access has
-       been implemented.
-     * Support for the Sun UltraSPARC T1 (Niagara) processor has been
-       added.
-
-  M32C
-
-     * Various bug fixes have made some functions (notably, functions
-       returning structures) incompatible with previous releases.
-       Recompiling all libraries is recommended. Note that code quality
-       has considerably improved since 4.1, making a recompile even more
-       beneficial.
-
-  MIPS
-
-     * Added support for the Broadcom SB-1A core.
-
-  IA-64
-
-     * Added support for IA-64 data and control speculation. By default
-       speculation is enabled only during second scheduler pass. A number
-       of machine flags was introduced to control the usage of speculation
-       for both scheduler passes.
-
-  HPPA
-
-     * Added Java language support (libffi and libjava) for 32-bit HP-UX
-       11 target.
-
-Obsolete Systems
-
-Documentation improvements
-
-  PDF Documentation
-
-     * A make pdf target has been added to the top-level makefile,
-       enabling automated production of PDF documentation files.
-       (Front-ends external to GCC should modify their Make-lang.in file
-       to add a lang.pdf: target.)
-
-Other significant improvements
-
-  Build system improvements
-
-     * All the components of the compiler are now bootstrapped by default.
-       This improves the resilience to bugs in the system compiler or
-       binary compatibility problems, as well as providing better testing
-       of GCC 4.2 itself. In addition, if you build the compiler from a
-       combined tree, the assembler, linker, etc. will also be
-       bootstrapped (i.e. built with themselves).
-       You can disable this behavior, and go back to the pre-GCC 4.2 set
-       up, by configuring GCC with --disable-bootstrap.
-     * The rules that configure follows to find target tools resemble more
-       closely the locations that the built compiler will search. In
-       addition, you can use the new configure option --with-target-tools
-       to specify where to find the target tools used during the build,
-       without affecting what the built compiler will use.
-       This can be especially useful when building packages of GCC. For
-       example, you may want to build GCC with GNU as or ld, even if the
-       resulting compiler to work with the native assembler and linker. To
-       do so, you can use --with-target-tools to point to the native
-       tools.
-
-  Incompatible changes to the build system
-
-     * Front-ends external to GCC should modify their Make-lang.in file to
-       replace double-colon rules (e.g. dvi::) with normal rules (like
-       lang.dvi:). Front-end makefile hooks do not use double-colon rules
-       anymore.
-     * Up to GCC 4.1, a popular way to specify the target tools used
-       during the build was to create directories named gas, binutils,
-       etc. in the build tree, and create links to the tools from there.
-       This does not work any more when the compiler is bootstrapped. The
-       new configure option --with-target-tools provides a better way to
-       achieve the same effect, and works for all native and cross
-       settings.
-
-   Please send FSF & GNU inquiries & questions to [7]gnu@gnu.org. There
-   are also [8]other ways to contact the FSF.
-
-   These pages are maintained by [9]the GCC team.
-
-
-    For questions related to the use of GCC, please consult these web
-    pages and the [10]GCC manuals. If that fails, the
-    [11]gcc-help@gcc.gnu.org mailing list might help.
-    Please send comments on these web pages and the development of GCC to
-    our developer mailing list at [12]gcc@gnu.org or [13]gcc@gcc.gnu.org.
-    All of our lists have [14]public archives.
-
-   Copyright (C) Free Software Foundation, Inc., 51 Franklin St, Fifth
-   Floor, Boston, MA 02110, USA.
-
-   Verbatim copying and distribution of this entire article is permitted
-   in any medium, provided this notice is preserved.
-   Last modified 2009-11-08 [15]Valid XHTML 1.0
-
-References
-
-   1. http://gcc.gnu.org/projects/gomp/
-   2. http://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html
-   3. http://gcc.gnu.org/onlinedocs/libstdc++/manual/bk01pt01ch01.html#manual.intro.status.standard.tr1
-   4. http://gcc.gnu.org/onlinedocs/libstdc++/ext/pb_ds/index.html
-   5. http://gcc.gnu.org/onlinedocs/gfortran/Runtime-Options.html
-   6. http://gcc.gnu.org/wiki/Statically_linking_libgcj
-   7. mailto:gnu@gnu.org
-   8. http://www.gnu.org/home.html#ContactInfo
-   9. http://gcc.gnu.org/about.html
-  10. http://gcc.gnu.org/onlinedocs/
-  11. mailto:gcc-help@gcc.gnu.org
-  12. mailto:gcc@gnu.org
-  13. mailto:gcc@gcc.gnu.org
-  14. http://gcc.gnu.org/lists.html
-  15. http://validator.w3.org/check/referer
-======================================================================
-http://gcc.gnu.org/gcc-4.1/index.html
-                           GCC 4.1 Release Series
-
-   February 13, 2007
-
-   The [1]GNU project and the GCC developers are pleased to announce the
-   release of GCC 4.1.2.
-
-   This release is a bug-fix release, containing fixes for regressions in
-   GCC 4.1.1 relative to previous releases of GCC.
-
-Release History
-
-   GCC 4.1.2
-          February 13, 2007 ([2]changes)
-
-   GCC 4.1.1
-          May 24, 2006 ([3]changes)
-
-   GCC 4.1.0
-          February 28, 2006 ([4]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 [5]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 [6]amazing group of volunteers is
-   what makes GCC successful.
-
-   For additional information about GCC please refer to the [7]GCC project
-   web site or contact the [8]GCC development mailing list.
-
-   To obtain GCC please use [9]our mirror sites or [10]our SVN 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 developer mailing list at [16]gcc@gnu.org or [17]gcc@gcc.gnu.org.
-    All of our lists have [18]public archives.
-
-   Copyright (C) Free Software Foundation, Inc., 51 Franklin St, Fifth
-   Floor, Boston, MA 02110, USA.
-
-   Verbatim copying and distribution of this entire article is permitted
-   in any medium, provided this notice is preserved.
-   Last modified 2008-10-04 [19]Valid XHTML 1.0
-
-References
-
-   1. http://www.gnu.org/
-   2. http://gcc.gnu.org/gcc-4.1/changes.html#4.1.2
-   3. http://gcc.gnu.org/gcc-4.1/changes.html
-   4. http://gcc.gnu.org/gcc-4.1/changes.html
-   5. http://gcc.gnu.org/gcc-4.1/buildstat.html
-   6. http://gcc.gnu.org/onlinedocs/gcc/Contributors.html
-   7. http://gcc.gnu.org/index.html
-   8. mailto:gcc@gcc.gnu.org
-   9. http://gcc.gnu.org/mirrors.html
-  10. http://gcc.gnu.org/svn.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://gcc.gnu.org/lists.html
-  19. http://validator.w3.org/check/referer
-======================================================================
-http://gcc.gnu.org/gcc-4.1/changes.html
-                           GCC 4.1 Release Series
-                      Changes, New Features, and Fixes
-
-   The latest release in the 4.1 release series is [1]GCC 4.1.2.
-
-Caveats
-
-General Optimizer Improvements
-
-     * GCC now has infrastructure for inter-procedural optimizations and
-       the following inter-procedural optimizations are implemented:
-          + Profile guided inlining. When doing profile feedback guided
-            optimization, GCC can now use the profile to make better
-            informed decisions on whether inlining of a function is
-            profitable or not. This means that GCC will no longer inline
-            functions at call sites that are not executed very often, and
-            that functions at hot call sites are more likely to be
-            inlined.
-            A new parameter min-inline-recursive-probability is also now
-            available to throttle recursive inlining of functions with
-            small average recursive depths.
-          + Discovery of pure and const functions, a form of side-effects
-            analysis. While older GCC releases could also discover such
-            special functions, the new IPA-based pass runs earlier so that
-            the results are available to more optimizers. The pass is also
-            simply more powerful than the old one.
-          + Analysis of references to static variables and type escape
-            analysis, also forms of side-effects analysis. The results of
-            these passes allow the compiler to be less conservative about
-            call-clobbered variables and references. This results in more
-            redundant loads being eliminated and in making static
-            variables candidates for register promotion.
-          + Improvement of RTL-based alias analysis. The results of type
-            escape analysis are fed to the RTL type-based alias analyzer,
-            allowing it to disambiguate more memory references.
-          + Interprocedural constant propagation and function versioning.
-            This pass looks for functions that are always called with the
-            same constant value for one or more of the function arguments,
-            and propagates those constants into those functions.
-          + GCC will now eliminate static variables whose usage was
-            optimized out.
-          + -fwhole-program --combine can now be used to make all
-            functions in program static allowing whole program
-            optimization. As an exception, the main function and all
-            functions marked with the new externally_visible attribute are
-            kept global so that programs can link with runtime libraries.
-     * GCC can now do a form of partial dead code elimination (PDCE) that
-       allows code motion of expressions to the paths where the result of
-       the expression is actually needed. This is not always a win, so the
-       pass has been limited to only consider profitable cases. Here is an
-       example:
-    int foo (int *, int *);
-    int
-    bar (int d)
-    {
-      int a, b, c;
-      b = d + 1;
-      c = d + 2;
-      a = b + c;
-      if (d)
-        {
-          foo (&b, &c);
-          a = b + c;
-        }
-      printf ("%d\n", a);
-    }
-
-       The a = b + c can be sunk to right before the printf. Normal code
-       sinking will not do this, it will sink the first one above into the
-       else-branch of the conditional jump, which still gives you two
-       copies of the code.
-     * GCC now has a value range propagation pass. This allows the
-       compiler to eliminate bounds checks and branches. The results of
-       the pass can also be used to accurately compute branch
-       probabilities.
-     * The pass to convert PHI nodes to straight-line code (a form of
-       if-conversion for GIMPLE) has been improved significantly. The two
-       most significant improvements are an improved algorithm to
-       determine the order in which the PHI nodes are considered, and an
-       improvement that allow the pass to consider if-conversions of basic
-       blocks with more than two predecessors.
-     * Alias analysis improvements. GCC can now differentiate between
-       different fields of structures in Tree-SSA's virtual operands form.
-       This lets stores/loads from non-overlapping structure fields not
-       conflict. A new algorithm to compute points-to sets was contributed
-       that can allows GCC to see now that p->a and p->b, where p is a
-       pointer to a structure, can never point to the same field.
-     * Various enhancements to auto-vectorization:
-          + Incrementally preserve SSA form when vectorizing.
-          + Incrementally preserve loop-closed form when vectorizing.
-          + Improvements to peeling for alignment: generate better code
-            when the misalignment of an access is known at compile time,
-            or when different accesses are known to have the same
-            misalignment, even if the misalignment amount itself is
-            unknown.
-          + Consider dependence distance in the vectorizer.
-          + Externalize generic parts of data reference analysis to make
-            this analysis available to other passes.
-          + Vectorization of conditional code.
-          + Reduction support.
-     * GCC can now partition functions in sections of hot and cold code.
-       This can significantly improve performance due to better
-       instruction cache locality. This feature works best together with
-       profile feedback driven optimization.
-     * A new pass to avoid saving of unneeded arguments to the stack in
-       vararg functions if the compiler can prove that they will not be
-       needed.
-     * Transition of basic block profiling to tree level implementation
-       has been completed. The new implementation should be considerably
-       more reliable (hopefully avoiding profile mismatch errors when
-       using -fprofile-use or -fbranch-probabilities) and can be used to
-       drive higher level optimizations, such as inlining.
-       The -ftree-based-profiling command-line option was removed and
-       -fprofile-use now implies disabling old RTL level loop optimizer
-       (-fno-loop-optimize). Speculative prefetching optimization
-       (originally enabled by -fspeculative-prefetching) was removed.
-
-New Languages and Language specific improvements
-
-  C and Objective-C
-
-     * The old Bison-based C and Objective-C parser has been replaced by a
-       new, faster hand-written recursive-descent parser.
-
-  Ada
-
-     * The build infrastructure for the Ada runtime library and tools has
-       been changed to be better integrated with the rest of the build
-       infrastructure of GCC. This should make doing cross builds of Ada a
-       bit easier.
-
-  C++
-
-     * ARM-style name-injection of friend declarations is no longer the
-       default. For example:
-          struct S {
-            friend void f();
-          };
-
-          void g() { f(); }
-       will not be accepted; instead a declaration of f will need to be
-       present outside of the scope of S. The new -ffriend-injection
-       option will enable the old behavior.
-     * The (undocumented) extension which permitted templates with default
-       arguments to be bound to template template parameters with fewer
-       parameters has been deprecated, and will be removed in the next
-       major release of G++. For example:
-       template <template <typename> class C>
-       void f(C<double>) {}
-
-       template <typename T, typename U = int>
-       struct S {};
-
-       template void f(S<double>);
-
-       makes use of the deprecated extension. The reason this code is not
-       valid ISO C++ is that S is a template with two parameters;
-       therefore, it cannot be bound to C which has only one parameter.
-
-    Runtime Library (libstdc++)
-
-     * Optimization work:
-          + A new implementation of std::search_n is provided, better
-            performing in case of random access iterators.
-          + Added further efficient specializations of istream functions,
-            i.e., character array and string extractors.
-          + Other smaller improvements throughout.
-     * Policy-based associative containers, designed for high-performance,
-       flexibility and semantic safety are delivered in ext/pb_assoc.
-     * A versatile string class, __gnu_cxx::__versa_string, providing
-       facilities conforming to the standard requirements for
-       basic_string, is delivered in <ext/vstring.h>. In particular:
-          + Two base classes are provided: the default one avoids
-            reference counting and is optimized for short strings; the
-            alternate one, still uses it while improving in a few low
-            level areas (e.g., alignment). See vstring_fwd.h for some
-            useful typedefs.
-          + Various algorithms have been rewritten (e.g., replace), the
-            code streamlined and simple optimizations added.
-          + Option 3 of DR 431 is implemented for both available bases,
-            thus improving the support for stateful allocators.
-     * As usual, many bugs have been fixed (e.g., libstdc++/13583,
-       libstdc++/23953) and LWG resolutions put into effect for the first
-       time (e.g., DR 280, DR 464, N1780 recommendations for DR 233, TR1
-       Issue 6.19). The implementation status of TR1 is now tracked in the
-       docs in tr1.html.
-
-  Objective-C++
-
-     * A new language front end for Objective-C++ has been added. This
-       language allows users to mix the object oriented features of
-       Objective-C with those of C++.
-
-  Java (GCJ)
-
-     * Core library (libgcj) updates based on GNU Classpath 0.15 - 0.19
-       features (plus some 0.20 bug-fixes)
-          + Networking
-               o The java.net.HttpURLConnection implementation no longer
-                 buffers the entire response body in memory. This means
-                 that response bodies larger than available memory can now
-                 be handled.
-          + (N)IO
-               o NIO FileChannel.map implementation, fast bulk put
-                 implementation for DirectByteBuffer (speeds up this
-                 method 10x).
-               o FileChannel.lock() and FileChannel.force() implemented.
-          + XML
-               o gnu.xml fix for nodes created outside a namespace
-                 context.
-               o Add support for output indenting and
-                 cdata-section-elements output instruction in
-                 xml.transform.
-               o xml.xpath corrections for cases where elements/attributes
-                 might have been created in non-namespace-aware mode.
-                 Corrections to handling of XSL variables and minor
-                 conformance updates.
-          + AWT
-               o GNU JAWT implementation, the AWT Native Interface, which
-                 allows direct access to native screen resources from
-                 within a Canvas's paint method. GNU Classpath Examples
-                 comes with a Demo, see libjava/classpath/examples/README.
-               o awt.datatransfer updated to 1.5 with support for
-                 FlavorEvents. The gtk+ awt peers now allow copy/paste of
-                 text, images, URIs/files and serialized objects with
-                 other applications and tracking clipboard change events
-                 with gtk+ 2.6 (for gtk+ 2.4 only text and serialized
-                 objects are supported). A GNU Classpath Examples
-                 datatransfer Demo was added to show the new
-                 functionality.
-               o Split gtk+ awt peers event handling in two threads and
-                 improve gdk lock handling (solves several awt lock ups).
-               o Speed up awt Image loading.
-               o Better gtk+ scrollbar peer implementation when using gtk+
-                 >= 2.6.
-               o Handle image loading errors correctly for gdkpixbuf and
-                 MediaTracker.
-               o Better handle GDK lock. Properly prefix gtkpeer native
-                 functions (cp_gtk).
-               o GdkGraphics2D has been updated to use Cairo 0.5.x or
-                 higher.
-               o BufferedImage and GtkImage rewrites. All image drawing
-                 operations should now work correctly (flipping requires
-                 gtk+ >= 2.6)
-               o Future Graphics2D, image and text work is documented at:
-                 [2]http://developer.classpath.org/mediation/ClasspathGrap
-                 hicsImagesText
-               o When gtk+ 2.6 or higher is installed the default log
-                 handler will produce stack traces whenever a WARNING,
-                 CRITICAL or ERROR message is produced.
-          + Free Swing
-               o The RepaintManager has been reworked for more efficient
-                 painting, especially for large GUIs.
-               o The layout manager OverlayLayout has been implemented,
-                 the BoxLayout has been rewritten to make use of the
-                 SizeRequirements utility class and caching for more
-                 efficient layout.
-               o Improved accessibility support.
-               o Significant progress has been made in the implementation
-                 of the javax.swing.plaf.metal package, with most UI
-                 delegates in a working state now. Please test this with
-                 your own applications and provide feedback that will help
-                 us to improve this package.
-               o The GUI demo (gnu.classpath.examples.swing.Demo) has been
-                 extended to highlight various features in our Free Swing
-                 implementation. And it includes a look and feel switcher
-                 for Metal (default), Ocean and GNU themes.
-               o The javax.swing.plaf.multi package is now implemented.
-               o Editing and several key actions for JTree and JTable were
-                 implemented.
-               o Lots of icons and look and feel improvements for Free
-                 Swing basic and metal themes were added. Try running the
-                 GNU Classpath Swing Demo in examples
-                 (gnu.classpath.examples.swing.Demo) with:
-                 -Dswing.defaultlaf=javax.swing.plaf.basic.BasicLookAndFee
-                 l or
-                 -Dswing.defaultlaf=javax.swing.plaf.metal.MetalLookAndFee
-                 l
-               o Start of styled text capabilites for java.swing.text.
-               o DefaultMutableTreeNode pre-order, post-order, depth-first
-                 and breadth-first traversal enumerations implemented.
-               o JInternalFrame colors and titlebar draw properly.
-               o JTree is working up to par (icons, selection and keyboard
-                 traversal).
-               o JMenus were made more compatible in visual and
-                 programmatic behavior.
-               o JTable changeSelection and multiple selections
-                 implemented.
-               o JButton and JToggleButton change states work properly
-                 now.
-               o JFileChooser fixes.
-               o revalidate() and repaint() fixes which make Free Swing
-                 much more responsive.
-               o MetalIconFactory implemented.
-               o Free Swing Top-Level Compatibility. JFrame, JDialog,
-                 JApplet, JInternalFrame, and JWindow are now 1.5
-                 compatible in the sense that you can call add() and
-                 setLayout() directly on them, which will have the same
-                 effect as calling getContentPane().add() and
-                 getContentPane().setLayout().
-               o The JTree interface has been completed. JTrees now
-                 recognizes mouse clicks and selections work.
-               o BoxLayout works properly now.
-               o Fixed GrayFilter to actually work.
-               o Metal SplitPane implemented.
-               o Lots of Free Swing text and editor stuff work now.
-          + Free RMI and Corba
-               o Andrew Watson, Vice President and Technical Director of
-                 the Object Management Group, has officially assigned us
-                 20 bit Vendor Minor Code Id: 0x47430 ("GC") that will
-                 mark remote classpath-specific system exceptions.
-                 Obtaining the VMCID means that GNU Classpath now is a
-                 recogniseable type of node in a highly interoperable
-                 CORBA world.
-               o GNU Classpath now includes the first working draft to
-                 support the RMI over IIOP protocol. The current
-                 implementation is capable of remote invocations,
-                 transferring various Serializables and Externalizables
-                 via RMI-IIOP protocol. It can flatten graphs and, at
-                 least for the simple cases, is interoperable with 1.5
-                 JDKs.
-               o org.omg.PortableInterceptor and related functionality in
-                 other packages is now implemented:
-                    # The sever and client interceptors work as required
-                      since 1.4.
-                    # The IOR interceptor works as needed for 1.5.
-               o The org.omg.DynamicAny package is completed and passes
-                 the prepared tests.
-               o The Portable Object Adapter should now support the output
-                 of the recent IDL to java compilers. These compilers now
-                 generate servants and not CORBA objects as before, making
-                 the output depend on the existing POA implementation.
-                 Completing POA means that such code can already be tried
-                 to run on Classpath. Our POA is tested for the following
-                 usager scenarios:
-                    # POA converts servant to the CORBA object.
-                    # Servant provides to the CORBA object.
-                    # POA activates new CORBA object with the given Object
-                      Id (byte array) that is later accessible for the
-                      servant.
-                    # During the first call, the ServantActivator provides
-                      servant for this and all subsequent calls on the
-                      current object.
-                    # During each call, the ServantLocator provides
-                      servant for this call only.
-                    # ServantLocator or ServantActivator forwards call to
-                      another server.
-                    # POA has a single servant, responsible for all
-                      objects.
-                    # POA has a default servant, but some objects are
-                      explicitly connected to they specific servants.
-                 The POA is verified using tests from the former
-                 cost.omg.org.
-               o The CORBA implementation is now a working prototype that
-                 should support features up to 1.3 inclusive. We invite
-                 groups writing CORBA dependent applications to try
-                 Classpath implementation, reporting any possible bugs.
-                 The CORBA prototype is interoperable with Sun's
-                 implementation v 1.4, transferring object references,
-                 primitive types, narrow and wide strings, arrays,
-                 structures, trees, abstract interfaces and value types
-                 (feature of CORBA 2.3) between these two platforms.
-                 Remote exceptions are transferred and handled correctly.
-                 The stringified object references (IORs) from various
-                 sources are parsed as required. The transient (for
-                 current session) and permanent (till jre restart)
-                 redirections work. Both Little and Big Endian encoded
-                 messages are accepted. The implementation is verified
-                 using tests from the former cost.omg.org. The current
-                 release includes working examples (see the examples
-                 directory), demonstrating the client-server
-                 communication, using either CORBA Request or IDL-based
-                 stub (usually generated by a IDL to java compiler). These
-                 examples also show how to use the Classpath CORBA naming
-                 service. The IDL to java compiler is not yet written, but
-                 as our library must be compatible, it naturally accepts
-                 the output of other idlj implementations.
-          + Misc
-               o Updated TimeZone data against Olson tzdata2005l.
-               o Make zip and jar packages UTF-8 clean.
-               o "native" code builds and compiles (warning free) on
-                 Darwin and Solaris.
-               o java.util.logging.FileHandler now rotates files.
-               o Start of a generic JDWP framework in gnu/classpath/jdwp.
-                 This is unfinished, but feedback (at classpath@gnu.org)
-                 from runtime hackers is greatly appreciated. Although
-                 most of the work is currently being done around gcj/gij
-                 we want this framework to be as VM neutral as possible.
-                 Early design is described in:
-                 [3]http://gcc.gnu.org/ml/java/2005-05/msg00260.html
-               o QT4 AWT peers, enable by giving configure
-                 --enable-qt-peer. Included, but not ready for production
-                 yet. They are explicitly disabled and not supported. But
-                 if you want to help with the development of these new
-                 features we are interested in feedback. You will have to
-                 explicitly enable them to try them out (and they will
-                 most likely contain bugs).
-               o Documentation fixes all over the place. See
-                 [4]http://developer.classpath.org/doc/
-
-New Targets and Target Specific Improvements
-
-  IA-32/x86-64
-
-     * The x86-64 medium model (that allows building applications whose
-       data segment exceeds 4GB) was redesigned to match latest ABI draft.
-       New implementation split large datastructures into separate segment
-       improving performance of accesses to small datastructures and also
-       allows linking of small model libraries into medium model programs
-       as long as the libraries are not accessing the large datastructures
-       directly. Medium model is also supported in position independent
-       code now.
-       The ABI change results in partial incompatibility among medium
-       model objects. Linking medium model libraries (or objects) compiled
-       with new compiler into medium model program compiled with older
-       will likely result in exceeding ranges of relocations.
-       Binutils 2.16.91 or newer are required for compiling medium model
-       now.
-
-  RS6000 (POWER/PowerPC)
-
-     * The AltiVec vector primitives in <altivec.h> are now implemented in
-       a way that puts a smaller burden on the preprocessor, instead
-       processing the "overloading" in the front ends. This should benefit
-       compilation speed on AltiVec vector code.
-     * AltiVec initializers now are generated more efficiently.
-     * The popcountb instruction available on POWER5 now is generated.
-     * The floating point round to integer instructions available on
-       POWER5+ now is generated.
-     * Floating point divides can be synthesized using the floating point
-       reciprocal estimate instructions.
-     * Double precision floating point constants are initialized as single
-       precision values if they can be represented exactly.
-
-  S/390, zSeries and System z9
-
-     * Support for the IBM System z9 109 processor has been added. When
-       using the -march=z9-109 option, the compiler will generate code
-       making use of instructions provided by the extended immediate
-       facility.
-     * Support for 128-bit IEEE floating point has been added. When using
-       the -mlong-double-128 option, the compiler will map the long double
-       data type to 128-bit IEEE floating point. Using this option
-       constitutes an ABI change, and requires glibc support.
-     * Various changes to improve performance of generated code have been
-       implemented, including:
-          + In functions that do not require a literal pool, register %r13
-            (which is traditionally reserved as literal pool pointer), can
-            now be freely used for other purposes by the compiler.
-          + More precise tracking of register use allows the compiler to
-            generate more efficient function prolog and epilog code in
-            certain cases.
-          + The SEARCH STRING, COMPARE LOGICAL STRING, and MOVE STRING
-            instructions are now used to implement C string functions.
-          + The MOVE CHARACTER instruction with single byte overlap is now
-            used to implement the memset function with non-zero fill byte.
-          + The LOAD ZERO instructions are now used where appropriate.
-          + The INSERT CHARACTERS UNDER MASK, STORE CHARACTERS UNDER MASK,
-            and INSERT IMMEDIATE instructions are now used more frequently
-            to optimize bitfield operations.
-          + The BRANCH ON COUNT instruction is now used more frequently.
-            In particular, the fact that a loop contains a subroutine call
-            no longer prevents the compiler from using this instruction.
-          + The compiler is now aware that all shift and rotate
-            instructions implicitly truncate the shift count to six bits.
-     * Back-end support for the following generic features has been
-       implemented:
-          + The full set of [5]built-in functions for atomic memory
-            access.
-          + The -fstack-protector feature.
-          + The optimization pass avoiding unnecessary stores of incoming
-            argument registers in functions with variable argument list.
-
-  SPARC
-
-     * The default code model in 64-bit mode has been changed from
-       Medium/Anywhere to Medium/Middle on Solaris.
-     * TLS support is disabled by default on Solaris prior to release 10.
-       It can be enabled on TLS-capable Solaris 9 versions (4/04 release
-       and later) by specifying --enable-tls at configure time.
-
-  MorphoSys
-
-     * Support has been added for this new architecture.
-
-Obsolete Systems
-
-Documentation improvements
-
-Other significant improvements
-
-     * GCC can now emit code for protecting applications from
-       stack-smashing attacks. The protection is realized by buffer
-       overflow detection and reordering of stack variables to avoid
-       pointer corruption.
-     * Some built-in functions have been fortified to protect them against
-       various buffer overflow (and format string) vulnerabilities.
-       Compared to the mudflap bounds checking feature, the safe builtins
-       have far smaller overhead. This means that programs built using
-       safe builtins should not experience any measurable slowdown.
-
-GCC 4.1.2
-
-   This is the [6]list of problem reports (PRs) from GCC's bug tracking
-   system that are known to be fixed in the 4.1.2 release. This list might
-   not be complete (that is, it is possible that some PRs that have been
-   fixed are not listed here).
-
-   When generating code for a shared library, GCC now recognizes that
-   global functions may be replaced when the program runs. Therefore, it
-   is now more conservative in deducing information from the bodies of
-   functions. For example, in this example:
-    void f() {}
-    void g() {
-     try { f(); }
-     catch (...) {
-       cout << "Exception";
-     }
-    }
-
-   G++ would previously have optimized away the catch clause, since it
-   would have concluded that f cannot throw exceptions. Because users may
-   replace f with another function in the main body of the program, this
-   optimization is unsafe, and is no longer performed. If you wish G++ to
-   continue to optimize as before, you must add a throw() clause to the
-   declaration of f to make clear that it does not throw exceptions.
-
-   Please send FSF & GNU inquiries & questions to [7]gnu@gnu.org. There
-   are also [8]other ways to contact the FSF.
-
-   These pages are maintained by [9]the GCC team.
-
-
-    For questions related to the use of GCC, please consult these web
-    pages and the [10]GCC manuals. If that fails, the
-    [11]gcc-help@gcc.gnu.org mailing list might help.
-    Please send comments on these web pages and the development of GCC to
-    our developer mailing list at [12]gcc@gnu.org or [13]gcc@gcc.gnu.org.
-    All of our lists have [14]public archives.
-
-   Copyright (C) Free Software Foundation, Inc., 51 Franklin St, Fifth
-   Floor, Boston, MA 02110, USA.
-
-   Verbatim copying and distribution of this entire article is permitted
-   in any medium, provided this notice is preserved.
-   Last modified 2009-01-25 [15]Valid XHTML 1.0
-
-References
-
-   1. http://gcc.gnu.org/gcc-4.1/changes.html#4.1.2
-   2. http://developer.classpath.org/mediation/ClasspathGraphicsImagesText
-   3. http://gcc.gnu.org/ml/java/2005-05/msg00260.html
-   4. http://developer.classpath.org/doc/
-   5. http://gcc.gnu.org/onlinedocs/gcc-4.1.0/gcc/Atomic-Builtins.html
-   6. http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.1.2
-   7. mailto:gnu@gnu.org
-   8. http://www.gnu.org/home.html#ContactInfo
-   9. http://gcc.gnu.org/about.html
-  10. http://gcc.gnu.org/onlinedocs/
-  11. mailto:gcc-help@gcc.gnu.org
-  12. mailto:gcc@gnu.org
-  13. mailto:gcc@gcc.gnu.org
-  14. http://gcc.gnu.org/lists.html
-  15. http://validator.w3.org/check/referer
-======================================================================
-http://gcc.gnu.org/gcc-4.0/index.html
-                           GCC 4.0 Release Series
-
-   January 31, 2007
-
-   The [1]GNU project and the GCC developers are pleased to announce the
-   release of GCC 4.0.4.
-
-   This release is a bug-fix release, containing fixes for regressions in
-   GCC 4.0.3 relative to previous releases of GCC.
-
-Release History
-
-   GCC 4.0.4
-          January 31, 2007 ([2]changes)
-
-   GCC 4.0.3
-          March 10, 2006 ([3]changes)
-
-   GCC 4.0.2
-          September 28, 2005 ([4]changes)
-
-   GCC 4.0.1
-          July 7, 2005 ([5]changes)
-
-   GCC 4.0.0
-          April 20, 2005 ([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, or [12]our SVN server.
-
-   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 developer mailing list at [18]gcc@gnu.org or [19]gcc@gcc.gnu.org.
-    All of our lists have [20]public archives.
-
-   Copyright (C) Free Software Foundation, Inc., 51 Franklin St, Fifth
-   Floor, Boston, MA 02110, USA.
-
-   Verbatim copying and distribution of this entire article is permitted
-   in any medium, provided this notice is preserved.
-   Last modified 2008-07-26 [21]Valid XHTML 1.0
-
-References
-
-   1. http://www.gnu.org/
-   2. http://gcc.gnu.org/gcc-4.0/changes.html#4.0.4
-   3. http://gcc.gnu.org/gcc-4.0/changes.html#4.0.3
-   4. http://gcc.gnu.org/gcc-4.0/changes.html#4.0.2
-   5. http://gcc.gnu.org/gcc-4.0/changes.html#4.0.1
-   6. http://gcc.gnu.org/gcc-4.0/changes.html
-   7. http://gcc.gnu.org/gcc-4.0/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://gcc.gnu.org/svn.html
-  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://gcc.gnu.org/lists.html
-  21. http://validator.w3.org/check/referer
-======================================================================
-http://gcc.gnu.org/gcc-4.0/changes.html
-                           GCC 4.0 Release Series
-                      Changes, New Features, and Fixes
-
-   The latest release in the 4.0 release series is [1]GCC 4.0.4.
-
-Caveats
-
-     * GCC now generates location lists by default when compiling with
-       debug info and optimization.
-          + GDB 6.0 and older crashes when it sees location lists. GDB 6.1
-            or later is needed to debug binaries containing location
-            lists.
-          + When you are trying to view a value of a variable in a part of
-            a function where it has no location (for example when the
-            variable is no longer used and thus its location was used for
-            something else) GDB will say that it is not available.
-       You can disable generating location lists by -fno-var-tracking.
-     * GCC no longer accepts the -fwritable-strings option. Use named
-       character arrays when you need a writable string.
-     * The options -freduce-all-givs and -fmove-all-movables have been
-       discontinued. They were used to circumvent a shortcoming in the
-       heuristics of the old loop optimization code with respect to common
-       Fortran constructs. The new (tree) loop optimizer works differently
-       and doesn't need those work-arounds.
-     * The graph-coloring register allocator, formerly enabled by the
-       option -fnew-ra, has been discontinued.
-     * -I- has been deprecated. -iquote is meant to replace the need for
-       this option.
-     * The MIPS -membedded-pic and -mrnames options have been removed.
-     * All MIPS targets now require the GNU assembler. In particular, IRIX
-       configurations can no longer use the MIPSpro assemblers, although
-       they do still support the MIPSpro linkers.
-     * The SPARC option -mflat has been removed.
-     * English-language diagnostic messages will now use Unicode quotation
-       marks in UTF-8 locales. (Non-English messages already used the
-       quotes appropriate for the language in previous releases.) If your
-       terminal does not support UTF-8 but you are using a UTF-8 locale
-       (such locales are the default on many GNU/Linux systems) then you
-       should set LC_CTYPE=C in the environment to disable that locale.
-       Programs that parse diagnostics and expect plain ASCII
-       English-language messages should set LC_ALL=C. See [2]Markus Kuhn's
-       explanation of Unicode quotation marks for more information.
-     * The specs file is no longer installed on most platforms. Most users
-       will be totally unaffected. However, if you are accustomed to
-       editing the specs file yourself, you will now have to use the
-       -dumpspecs option to generate the specs file, and then edit the
-       resulting file.
-
-General Optimizer Improvements
-
-     * The [3]tree ssa branch has been merged. This merge has brought in a
-       completely new optimization framework based on a higher level
-       intermediate representation than the existing RTL representation.
-       Numerous new code transformations based on the new framework are
-       available in GCC 4.0, including:
-          + Scalar replacement of aggregates
-          + Constant propagation
-          + Value range propagation
-          + Partial redundancy elimination
-          + Load and store motion
-          + Strength reduction
-          + Dead store elimination
-          + Dead and unreachable code elimination
-          + [4]Autovectorization
-          + Loop interchange
-          + Tail recursion by accumulation
-       Many of these passes outperform their counterparts from previous
-       GCC releases.
-     * [5]Swing Modulo Scheduling (SMS). An RTL level instruction
-       scheduling optimization intended for loops that perform heavy
-       computations.
-
-New Languages and Language specific improvements
-
-  C family
-
-     * The sentinel attribute has been added to GCC. This function
-       attribute allows GCC to warn when variadic functions such as execl
-       are not NULL terminated. See the GCC manual for a complete
-       description of its behavior.
-     * Given __attribute__((alias("target"))) it is now an error if target
-       is not a symbol, defined in the same translation unit. This also
-       applies to aliases created by #pragma weak alias=target. This is
-       because it's meaningless to define an alias to an undefined symbol.
-       On Solaris, the native assembler would have caught this error, but
-       GNU as does not.
-
-  C and Objective-C
-
-     * The -Wstrict-aliasing=2 option has been added. This warning catches
-       all unsafe cases, but it may also give a warning for some cases
-       that are safe.
-     * The cast-as-lvalue, conditional-expression-as-lvalue and
-       compound-expression-as-lvalue extensions, which were deprecated in
-       3.3.4 and 3.4, have been removed.
-     * The -fwritable-strings option, which was deprecated in 3.4, has
-       been removed.
-     * #pragma pack() semantics have been brought closer to those used by
-       other compilers. This also applies to C++.
-     * Taking the address of a variable with register storage is invalid
-       in C. GCC now issues an error instead of a warning.
-     * Arrays of incomplete element type are invalid in C. GCC now issues
-       an error for such arrays. Declarations such as extern struct s x[];
-       (where struct s has not been defined) can be moved after the
-       definition of struct s. Function parameters declared as arrays of
-       incomplete type can instead be declared as pointers.
-
-  C++
-
-     * When compiling without optimizations (-O0), the C++ frontend is
-       much faster than in any previous versions of GCC. Independent
-       testers have measured speed-ups up to 25% in real-world production
-       code, compared to the 3.4 family (which was already the fastest
-       version to date). Upgrading from older versions might show even
-       bigger improvements.
-     * ELF visibility attributes can now be applied to a class type, so
-       that it affects every member function of a class at once, without
-       having to specify each individually:
-class __attribute__ ((visibility("hidden"))) Foo
-{
-   int foo1();
-   void foo2();
-};
-       The syntax is deliberately similar to the __declspec() system used
-       by Microsoft Windows based compilers, allowing cross-platform
-       projects to easily reuse their existing macro system for denoting
-       exports and imports. By explicitly marking internal classes never
-       used outside a binary as hidden, one can completely avoid PLT
-       indirection overheads during their usage by the compiler. You can
-       find out more about the advantages of this at
-       [6]http://people.redhat.com/drepper/dsohowto.pdf
-     * The -fvisibility-inlines-hidden option has been added which marks
-       all inlineable functions as having hidden ELF visibility, thus
-       removing their symbol and typeinfo from the exported symbol table
-       of the output ELF binary. Using this option can reduce the exported
-       symbol count of template-heavy code by up to 40% with no code
-       change at all, thus notably improving link and load times for the
-       binary as well as a reduction in size of up to 10%. Also, check the
-       new [7]-fvisibility option.
-     * The compiler now uses the library interface specified by the [8]C++
-       ABI for thread-safe initialization of function-scope static
-       variables. Most users should leave this alone, but embedded
-       programmers may want to disable this by specifying
-       -fno-threadsafe-statics for a small savings in code size.
-     * Taking the address of an explicit register variable is no longer
-       supported. Note that C++ allows taking the address of variables
-       with register storage so this will continue to compile with a
-       warning. For example, assuming that r0 is a machine register:
-register int foo asm ("r0");
-register int bar;
-&foo; // error, no longer accepted
-&bar; // OK, with a warning
-     * G++ has an undocumented extension to virtual function covariancy
-       rules that allowed the overrider to return a type that was
-       implicitly convertable to the overridden function's return type.
-       For instance a function returning void * could be overridden by a
-       function returning T *. This is now deprecated and will be removed
-       in a future release.
-     * The G++ minimum and maximum operators (<? and >?) and their
-       compound forms (<?=) and >?=) have been deprecated and will be
-       removed in a future version. Code using these operators should be
-       modified to use std::min and std::max instead.
-     * Declaration of nested classes of class templates as friends are
-       supported:
-template <typename T> struct A {
-  class B {};
-};
-class C {
-  template <typename T> friend class A<T>::B;
-};
-       This complements the feature member functions of class templates as
-       friends introduced in GCC 3.4.0.
-     * When declaring a friend class using an unqualified name, classes
-       outside the innermost non-class scope are not searched:
-class A;
-namespace N {
-  class B {
-    friend class A;   // Refer to N::A which has not been declared yet
-                      // because name outside namespace N are not searched
-    friend class ::A; // Refer to ::A
-  };
-}
-       Hiding the friend name until declaration is still not implemented.
-     * Friends of classes defined outside their namespace are correctly
-       handled:
-namespace N {
-  class A;
-}
-class N::A {
-  friend class B; // Refer to N::B in GCC 4.0.0
-                  // but ::B in earlier versions of GCC
-};
-
-    Runtime Library (libstdc++)
-
-     * Optimization work:
-          + Added efficient specializations of istream functions for char
-            and wchar_t.
-          + Further performance tuning of strings, in particular wrt
-            single-char append and getline.
-          + iter_swap - and therefore most of the mutating algorithms -
-            now makes an unqualified call to swap when the value_type of
-            the two iterators is the same.
-     * A large subset of the features in Technical Report 1 (TR1 for
-       short) is experimentally delivered (i.e., no guarantees about the
-       implementation are provided. In particular it is not promised that
-       the library will remain link-compatible when code using TR1 is
-       used):
-          + General utilities such as reference_wrapper and shared_ptr.
-          + Function objects, i.e., result_of, mem_fn, bind, function.
-          + Support for metaprogramming.
-          + New containers such as tuple, array, unordered_set,
-            unordered_map, unordered_multiset, unordered_multimap.
-     * As usual, many bugs have been fixed and LWG resolutions implemented
-       for the first time (e.g., DR 409).