diff options
Diffstat (limited to 'gcc-4.8/INSTALL')
| -rw-r--r-- | gcc-4.8/INSTALL/binaries.html | 4 | ||||
| -rw-r--r-- | gcc-4.8/INSTALL/build.html | 12 | ||||
| -rw-r--r-- | gcc-4.8/INSTALL/configure.html | 48 | ||||
| -rw-r--r-- | gcc-4.8/INSTALL/download.html | 4 | ||||
| -rw-r--r-- | gcc-4.8/INSTALL/finalinstall.html | 8 | ||||
| -rw-r--r-- | gcc-4.8/INSTALL/gfdl.html | 38 | ||||
| -rw-r--r-- | gcc-4.8/INSTALL/index.html | 8 | ||||
| -rw-r--r-- | gcc-4.8/INSTALL/old.html | 14 | ||||
| -rw-r--r-- | gcc-4.8/INSTALL/prerequisites.html | 6 | ||||
| -rw-r--r-- | gcc-4.8/INSTALL/specific.html | 84 | ||||
| -rw-r--r-- | gcc-4.8/INSTALL/test.html | 20 |
11 files changed, 123 insertions, 123 deletions
diff --git a/gcc-4.8/INSTALL/binaries.html b/gcc-4.8/INSTALL/binaries.html index 9ffb75b38..ccd8b3d43 100644 --- a/gcc-4.8/INSTALL/binaries.html +++ b/gcc-4.8/INSTALL/binaries.html @@ -3,7 +3,7 @@ <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"> +<meta name="generator" content="makeinfo 4.12"> <link title="Top" rel="top" href="#Top"> <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage"> <!-- @@ -100,7 +100,7 @@ Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10. 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. +links to GNU Fortran binaries for several platforms. </ul> <p><hr /> diff --git a/gcc-4.8/INSTALL/build.html b/gcc-4.8/INSTALL/build.html index aaae4c4d2..0b5eed579 100644 --- a/gcc-4.8/INSTALL/build.html +++ b/gcc-4.8/INSTALL/build.html @@ -3,7 +3,7 @@ <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"> +<meta name="generator" content="makeinfo 4.12"> <link title="Top" rel="top" href="#Top"> <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage"> <!-- @@ -142,7 +142,7 @@ bootstrap4</span></samp>’ 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. +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_TFLAGS</code> to this end. @@ -170,7 +170,7 @@ the one you are building on: for example, you could build a <samp><span class="option">--enable-bootstrap</span></samp> to the configure script. <p><code>BUILD_CONFIG</code> can be used to bring in additional customization -to the build. It can be set to a whitespace-separated list of names. +to the build. It can be set to a whitespace-separated list of names. For each such <code>NAME</code>, top-level <samp><span class="file">config/</span><code>NAME</code><span class="file">.mk</span></samp> will be included by the top-level <samp><span class="file">Makefile</span></samp>, bringing in any settings it contains. The default <code>BUILD_CONFIG</code> can be set using the @@ -325,7 +325,7 @@ 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 4.0 or later). +compiler (GCC version 4.0 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. @@ -355,11 +355,11 @@ bootstrap the compiler with profile feedback, use <code>make profiledbootstrap</ <p>When ‘<samp><span class="samp">make profiledbootstrap</span></samp>’ 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. +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. +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. diff --git a/gcc-4.8/INSTALL/configure.html b/gcc-4.8/INSTALL/configure.html index 2b3a265c5..9e6e556e0 100644 --- a/gcc-4.8/INSTALL/configure.html +++ b/gcc-4.8/INSTALL/configure.html @@ -3,7 +3,7 @@ <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"> +<meta name="generator" content="makeinfo 4.12"> <link title="Top" rel="top" href="#Top"> <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage"> <!-- @@ -121,7 +121,7 @@ when configuring a cross compiler; examples of valid targets would be m68k-elf, 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>. +implies that the host defaults to <var>target</var>. </ul> <h3 class="heading"><a name="TOC2"></a>Options specification</h3> @@ -383,7 +383,7 @@ 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). +the target as well). </ul> <p>You may want to use <samp><span class="option">--with-as</span></samp> if no assembler @@ -471,7 +471,7 @@ these are handled by <samp><span class="option">--with-endian</span></samp>. processors. The multilib for the secondary endian remains enabled. <p>As a special case, if an entry in the list starts with a <code>!</code> -(exclamation point), then it is added to the list of excluded multilibs. +(exclamation point), then it is added to the list of excluded multilibs. Entries of this sort should be compatible with ‘<samp><span class="samp">MULTILIB_EXCLUDES</span></samp>’ (once the leading <code>!</code> has been stripped). @@ -495,7 +495,7 @@ respectively. If <var>list</var> is empty, then there will be no multilibs and only the default run-time library will be enabled. <p>If <samp><span class="option">--with-multilib-list</span></samp> is not given, then only 32-bit and -64-bit run-time libraries will be enabled. +64-bit run-time libraries will be enabled. </dl> <br><dt><code>--with-endian=</code><var>endians</var><dd>Specify what endians to use. @@ -511,7 +511,7 @@ Currently only implemented for sh*-*-*. <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. +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 @@ -579,11 +579,11 @@ enables <samp><span class="option">-msse2</span></samp> or ‘<samp><span cl This option is only supported on i386 and x86-64 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. +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). +systems that support conditional traps). <br><dt><code>breaks</code><dd>Division by zero checks use the break instruction. </dl> @@ -609,7 +609,7 @@ 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. +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 @@ -619,7 +619,7 @@ only available on systems with GNU libc. When enabled, this will cause currently only available on systems with GNU libc on certain targets. <br><dt><code>--enable-target-optspace</code><dd>Specify that target -libraries should be optimized for code space instead of code speed. +libraries should be optimized for code space instead of code speed. This is the default for the m32r platform. <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 @@ -649,9 +649,9 @@ 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. +even if the target and host triplets are different. This is possible when the host can run code compiled for -the target (e.g. host is i686-linux, target is i486-linux). +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>. @@ -686,8 +686,8 @@ their runtime libraries should be built. For a list of valid values for </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>go</code>, <code>java</code>, <code>objc</code>, <code>obj-c++</code>. -Building the Ada compiler has special requirements, see below. +<code>go</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, Go and Objective-C++ are not default languages; the rest are. @@ -729,13 +729,13 @@ 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. +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. +you are building a bi-arch or multi-arch binutils in a combined tree. On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64), -defaulted to o32. +defaulted to o32. Currently, this option only affects sparc-linux, powerpc-linux, x86-linux, mips-linux and s390-linux. @@ -859,7 +859,7 @@ 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. +<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. @@ -958,7 +958,7 @@ default, and may be disabled using <samp><span class="option">--disable-lto</spa <br><dt><code>--with-plugin-ld=</code><var>pathname</var><dd>Enable an alternate linker to be used at link-time optimization (LTO) link time when <samp><span class="option">-fuse-linker-plugin</span></samp> is enabled. This linker should have plugin support such as gold starting with -version 2.20 or GNU ld starting with version 2.21. +version 2.20 or GNU ld starting with version 2.21. See <samp><span class="option">-fuse-linker-plugin</span></samp> for details. <br><dt><code>--enable-canonical-system-headers</code><dt><code>--disable-canonical-system-headers</code><dd>Enable system header path canonicalization for <samp><span class="file">libcpp</span></samp>. This can @@ -974,7 +974,7 @@ environments. Enabled by default, and may be disabled using <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. +(a subset of) the root filesystem of the target operating system. Target system headers, libraries and run-time object files will be searched for in there. More specifically, this acts as if <samp><span class="option">--sysroot=</span><var>dir</var></samp> was added to the default options of the built @@ -1012,7 +1012,7 @@ option then the compiler will search that directory within <var>dirname</var> fo native system headers rather than the default <samp><span class="file">/usr/include</span></samp>. <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. +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 @@ -1040,7 +1040,7 @@ omitted from <samp><span class="file">libgcc.a</span></samp> on the assumption t being used as the target C library. This causes float support functions like <code>__addsf3</code> to be omitted from <samp><span class="file">libgcc.a</span></samp> on the assumption that it will be provided by <samp><span class="file">libm.a</span></samp>. For more -technical details, cf. <a href="http://gcc.gnu.org/PR54461">PR54461</a>. +technical details, cf. <a href="http://gcc.gnu.org/PR54461">PR54461</a>. This option is only supported for the AVR target. It is not supported for RTEMS configurations, which currently use newlib. The option is supported since version 4.7.2 and is the default in 4.8.0 and newer. @@ -1059,7 +1059,7 @@ native tools in <samp><span class="file">/usr/bin</span></samp>. <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. +tools. </dl> <h4 class="subheading"><a name="TOC4"></a>Java-Specific Options</h4> @@ -1223,7 +1223,7 @@ 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. +only run on Microsoft Windows NT and above. </dl> </dl> diff --git a/gcc-4.8/INSTALL/download.html b/gcc-4.8/INSTALL/download.html index 01a0b0b83..5eb846647 100644 --- a/gcc-4.8/INSTALL/download.html +++ b/gcc-4.8/INSTALL/download.html @@ -3,7 +3,7 @@ <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"> +<meta name="generator" content="makeinfo 4.12"> <link title="Top" rel="top" href="#Top"> <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage"> <!-- @@ -50,7 +50,7 @@ for information on how to obtain GCC. <p>The source distribution includes the C, C++, Objective-C, Fortran, Java, and Ada (in the case of GCC 3.1 and later) compilers, as well as -runtime libraries for C++, Objective-C, Fortran, and Java. +runtime libraries for C++, Objective-C, Fortran, and Java. For previous versions these were downloadable as separate components such as the core GCC distribution, which included the C language front end and shared components, and language-specific distributions including the diff --git a/gcc-4.8/INSTALL/finalinstall.html b/gcc-4.8/INSTALL/finalinstall.html index 0428124b0..18ba78262 100644 --- a/gcc-4.8/INSTALL/finalinstall.html +++ b/gcc-4.8/INSTALL/finalinstall.html @@ -3,7 +3,7 @@ <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"> +<meta name="generator" content="makeinfo 4.12"> <link title="Top" rel="top" href="#Top"> <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage"> <!-- @@ -94,11 +94,11 @@ using the <code>DESTDIR</code> feature. </pre> <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>. +<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. +that you successfully built and installed GCC. Include the following information: <ul> @@ -132,7 +132,7 @@ 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. +will include a link to the archived copy of your message. </ul> <p>We'd also like to know if the diff --git a/gcc-4.8/INSTALL/gfdl.html b/gcc-4.8/INSTALL/gfdl.html index 089e3d4fe..10fdaa3bb 100644 --- a/gcc-4.8/INSTALL/gfdl.html +++ b/gcc-4.8/INSTALL/gfdl.html @@ -3,7 +3,7 @@ <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"> +<meta name="generator" content="makeinfo 4.12"> <link title="Top" rel="top" href="#Top"> <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage"> <!-- @@ -56,7 +56,7 @@ license is included in the section entitled "GNU Free Documentation License". <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. +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. @@ -123,7 +123,7 @@ 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. +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 “Transparent” is called “Opaque”. @@ -190,7 +190,7 @@ 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. +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. @@ -205,7 +205,7 @@ 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. +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 @@ -267,7 +267,7 @@ 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 “History” section. +it was based on. These may be placed in the “History” 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. @@ -331,7 +331,7 @@ 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. +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. @@ -369,14 +369,14 @@ derivative works of the Document. 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. +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. +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 @@ -478,20 +478,20 @@ provided the MMC is eligible for relicensing. 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.3 - 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 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.3 + 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 “with...Texts.” 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 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 diff --git a/gcc-4.8/INSTALL/index.html b/gcc-4.8/INSTALL/index.html index 695f088d2..29e6ee076 100644 --- a/gcc-4.8/INSTALL/index.html +++ b/gcc-4.8/INSTALL/index.html @@ -3,7 +3,7 @@ <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"> +<meta name="generator" content="makeinfo 4.12"> <link title="Top" rel="top" href="#Top"> <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage"> <!-- @@ -41,7 +41,7 @@ license is included in the section entitled "GNU Free Documentation License". <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>. +<a href="http://gcc.gnu.org/install/">http://gcc.gnu.org/install/</a>. It refers to the current development sources, instructions for specific released versions are included with the sources. @@ -53,12 +53,12 @@ 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>. +<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>. +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. diff --git a/gcc-4.8/INSTALL/old.html b/gcc-4.8/INSTALL/old.html index 97b62770d..4d814038f 100644 --- a/gcc-4.8/INSTALL/old.html +++ b/gcc-4.8/INSTALL/old.html @@ -3,7 +3,7 @@ <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"> +<meta name="generator" content="makeinfo 4.12"> <link title="Top" rel="top" href="#Top"> <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage"> <!-- @@ -115,7 +115,7 @@ Here are the possible CPU types: hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860, i960, ip2k, m32r, m68000, m68k, m88k, mcore, mips, mipsel, mips64, mips64el, mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle, romp, rs6000, sh, sparc, -sparclite, sparc64, v850, vax, we32k. +sparclite, sparc64, v850, vax, we32k. </blockquote> <p>Here are the recognized company names. As you can see, customary @@ -127,7 +127,7 @@ 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. +sequent, sgi, sony, sun, tti, unicom, wrs. </blockquote> <p>The company name is meaningful only to disambiguate when the rest of @@ -143,7 +143,7 @@ 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. +vxworks, winnt, xenix. </blockquote> <p class="noindent">You can omit the system type; then <samp><span class="file">configure</span></samp> guesses the @@ -163,7 +163,7 @@ are obsolete. <p>If you specify an impossible combination such as ‘<samp><span class="samp">i860-dg-vms</span></samp>’, 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. +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. @@ -186,11 +186,11 @@ 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. +sun4, symmetry, tower-32, tower. </blockquote> <p class="noindent">Remember that a machine name specifies both the cpu type and the company -name. +name. <hr /> <p><a href="./index.html">Return to the GCC Installation page</a> diff --git a/gcc-4.8/INSTALL/prerequisites.html b/gcc-4.8/INSTALL/prerequisites.html index 4879f9286..00e60df71 100644 --- a/gcc-4.8/INSTALL/prerequisites.html +++ b/gcc-4.8/INSTALL/prerequisites.html @@ -3,7 +3,7 @@ <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"> +<meta name="generator" content="makeinfo 4.12"> <link title="Top" rel="top" href="#Top"> <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage"> <!-- @@ -117,7 +117,7 @@ and up works. <p>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 generating manpages from Texinfo manuals. Used by various scripts to generate some files included in SVN (mainly Unicode-related and rarely changing) from source tables. @@ -174,7 +174,7 @@ installed in your default library search path. 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> as <samp><span class="file">cloog-0.18.0.tar.gz</span></samp>. 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. +be used if CLooG is not installed in your default library search path. CLooG needs to be built against ISL 0.11.1. Use <samp><span class="option">--with-isl=system</span></samp> to direct CLooG to pick up an already installed ISL, otherwise it will use ISL 0.11.1 as bundled with CLooG. CLooG needs to be configured to use GMP diff --git a/gcc-4.8/INSTALL/specific.html b/gcc-4.8/INSTALL/specific.html index caf81b60b..f4cbbe229 100644 --- a/gcc-4.8/INSTALL/specific.html +++ b/gcc-4.8/INSTALL/specific.html @@ -3,7 +3,7 @@ <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"> +<meta name="generator" content="makeinfo 4.12"> <link title="Top" rel="top" href="#Top"> <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage"> <!-- @@ -47,7 +47,7 @@ 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 have to. +information have to. <ul> <li><a href="#alpha-x-x">alpha*-*-*</a> @@ -169,7 +169,7 @@ and <code>arm-*-rtemseabi</code>. <h3 class="heading"><a name="TOC4"></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. +applications. There are no standard Unix configurations. See “AVR Options” in the main manual for the list of supported MCU types. @@ -194,7 +194,7 @@ can also be obtained from: <h3 class="heading"><a name="TOC5"></a><a name="bfin"></a>Blackfin</h3> -<p>The Blackfin processor, an Analog Devices DSP. +<p>The Blackfin processor, an Analog Devices DSP. See “Blackfin Options” in the main manual <p>More information, and a version of binutils with support for this processor, @@ -204,7 +204,7 @@ is available at <a href="http://blackfin.uclinux.org">http://blackfin.uclinux.or <h3 class="heading"><a name="TOC6"></a><a name="cr16"></a>CR16</h3> -<p>The CR16 CompactRISC architecture is a 16-bit architecture. This architecture is +<p>The CR16 CompactRISC architecture is a 16-bit architecture. This architecture is used in embedded applications. <p>See “CR16 Options” in the main manual for a list of CR16-specific options. @@ -256,7 +256,7 @@ and includes all the necessary compilation tools and libraries. <h3 class="heading"><a name="TOC9"></a><a name="epiphany_002dx_002delf"></a>epiphany-*-elf</h3> -<p>Adapteva Epiphany. +<p>Adapteva Epiphany. This configuration is intended for embedded systems. <p><hr /> @@ -339,7 +339,7 @@ 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. +architecture specified for the target machine when configuring. PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when the target is a ‘<samp><span class="samp">hppa1*</span></samp>’ machine. @@ -350,7 +350,7 @@ 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. +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 @@ -402,20 +402,20 @@ 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. +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 ‘<samp><span class="samp">hppa[1-2]*-hp-hpux11*</span></samp>’ target generates code -for the 32-bit PA-RISC runtime architecture and uses the HP linker. +for the 32-bit PA-RISC runtime architecture and uses the HP linker. The ‘<samp><span class="samp">hppa64-hp-hpux11*</span></samp>’ 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. +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. @@ -450,7 +450,7 @@ 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. +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. @@ -494,7 +494,7 @@ libstdc++-v3 documentation. <h3 class="heading"><a name="TOC16"></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. +<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 @@ -505,7 +505,7 @@ found on <a href="http://www.bitwizard.nl/sig11/">www.bitwizard.nl</a>. <h3 class="heading"><a name="TOC17"></a><a name="ix86_002dx_002dsolaris29"></a>i?86-*-solaris2.9</h3> -<p>The Sun assembler in Solaris 9 has several bugs and limitations. +<p>The Sun assembler in Solaris 9 has several bugs and limitations. While GCC works around them, several features are missing, so it is <!-- FIXME: which ones? --> recommended to use the GNU assembler instead. There is no bundled @@ -564,9 +564,9 @@ 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. +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. @@ -580,7 +580,7 @@ the option <samp><span class="option">--with-gnu-as</span></samp> may be necessa <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. +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. @@ -589,7 +589,7 @@ removed and the system libunwind library will always be used. <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>Support for AIX version 3 and older was discontinued in GCC 3.4. Support for AIX version 4.2 and older was discontinued in GCC 4.5. <p>“out of memory” bootstrap failures may indicate a problem with @@ -686,7 +686,7 @@ executable. <p>AIX 4.3 utilizes a “large format” 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. +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 “not a COFF file”. 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> @@ -736,28 +736,28 @@ applications. There are no standard Unix configurations. <h3 class="heading"><a name="TOC23"></a><a name="lm32_002dx_002delf"></a>lm32-*-elf</h3> -<p>Lattice Mico32 processor. +<p>Lattice Mico32 processor. This configuration is intended for embedded systems. <p><hr /> <h3 class="heading"><a name="TOC24"></a><a name="lm32_002dx_002duclinux"></a>lm32-*-uclinux</h3> -<p>Lattice Mico32 processor. +<p>Lattice Mico32 processor. This configuration is intended for embedded systems running uClinux. <p><hr /> <h3 class="heading"><a name="TOC25"></a><a name="m32c_002dx_002delf"></a>m32c-*-elf</h3> -<p>Renesas M32C processor. +<p>Renesas M32C processor. This configuration is intended for embedded systems. <p><hr /> <h3 class="heading"><a name="TOC26"></a><a name="m32r_002dx_002delf"></a>m32r-*-elf</h3> -<p>Renesas M32R processor. +<p>Renesas M32R processor. This configuration is intended for embedded systems. <p><hr /> @@ -801,14 +801,14 @@ both of which were ABI changes. <h3 class="heading"><a name="TOC29"></a><a name="mep_002dx_002delf"></a>mep-*-elf</h3> -<p>Toshiba Media embedded Processor. +<p>Toshiba Media embedded Processor. This configuration is intended for embedded systems. <p><hr /> <h3 class="heading"><a name="TOC30"></a><a name="microblaze_002dx_002delf"></a>microblaze-*-elf</h3> -<p>Xilinx MicroBlaze processor. +<p>Xilinx MicroBlaze processor. This configuration is intended for embedded systems. <p><hr /> @@ -963,7 +963,7 @@ the PSIM simulator. <h3 class="heading"><a name="TOC45"></a><a name="rl78_002dx_002delf"></a>rl78-*-elf</h3> -<p>The Renesas RL78 processor. +<p>The Renesas RL78 processor. This configuration is intended for embedded systems. <p><hr /> @@ -1051,7 +1051,7 @@ are known to work as well. 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> may fail to -build or cause memory corruption at runtime in some cases for C++ programs. +build or cause memory corruption at runtime in some cases for C++ programs. <!-- FIXME: still? --> GNU <samp><span class="command">ld</span></samp> usually works as well, although the version included in Solaris 10 cannot be used due to several bugs. Again, the current @@ -1148,13 +1148,13 @@ 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 -an x86-only problem by Sun, probably because they do not use DWARF-2). +an 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. + external symbolic relocation against non-allocatable section + .debug_info cannot be processed at runtime: relocation ignored. </pre> <p class="noindent">To work around this problem, compile with <samp><span class="option">-gstabs+</span></samp> instead of plain <samp><span class="option">-g</span></samp>. @@ -1175,7 +1175,7 @@ not that of GMP or MPFR or MPC). For example on a Solaris 9 system: thread-local storage (TLS). A typical error message is <pre class="smallexample"> ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o: - symbol <unknown>: bad symbol type SECT: symbol type must be TLS + symbol <unknown>: bad symbol type SECT: symbol type must be TLS </pre> <p class="noindent">This bug is fixed in Sun patch 118683-03 or later. @@ -1237,8 +1237,8 @@ binutils-2.22 or newer. <h3 class="heading"><a name="TOC60"></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. +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 “configlette” (see below). We are not interested in supporting older, a.out or COFF-based, versions of @@ -1246,7 +1246,7 @@ 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>. +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 @@ -1272,7 +1272,7 @@ VxWorks will incorporate this module.) <h3 class="heading"><a name="TOC61"></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. +(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). @@ -1340,19 +1340,19 @@ 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. +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. +provides native support for POSIX. <li>MinGW <a href="#x-x-mingw32">*-*-mingw32</a>: MinGW is a native GCC port for -the Win32 subsystem that provides a subset of POSIX. +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. +<a href="http://www.mkssoftware.com/">http://www.mkssoftware.com/</a> for more information. </ul> <h4 class="subheading"><a name="TOC68"></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>. +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. @@ -1405,7 +1405,7 @@ the Win32 subsystem. This target was last known to work in GCC 3.3. <h3 class="heading"><a name="TOC73"></a><a name="x_002dx_002dmingw32"></a>*-*-mingw32</h3> -<p>GCC will build with and support only MinGW runtime 3.12 and later. +<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. diff --git a/gcc-4.8/INSTALL/test.html b/gcc-4.8/INSTALL/test.html index 1a104438e..8bc6b29a2 100644 --- a/gcc-4.8/INSTALL/test.html +++ b/gcc-4.8/INSTALL/test.html @@ -3,7 +3,7 @@ <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"> +<meta name="generator" content="makeinfo 4.12"> <link title="Top" rel="top" href="#Top"> <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage"> <!-- @@ -44,10 +44,10 @@ license is included in the section entitled "GNU Free Documentation License". 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>. +<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. +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. @@ -136,13 +136,13 @@ The following will run each testsuite eight times using the ‘<samp><span c target, as if you had specified all possible combinations yourself: <pre class="smallexample"> --target_board='arm-sim/-mhard-float/-O1 \ - arm-sim/-mhard-float/-O2 \ - arm-sim/-mhard-float/-O3 \ - arm-sim/-mhard-float \ - arm-sim/-msoft-float/-O1 \ - arm-sim/-msoft-float/-O2 \ - arm-sim/-msoft-float/-O3 \ - arm-sim/-msoft-float' + arm-sim/-mhard-float/-O2 \ + arm-sim/-mhard-float/-O3 \ + arm-sim/-mhard-float \ + arm-sim/-msoft-float/-O1 \ + arm-sim/-msoft-float/-O2 \ + arm-sim/-msoft-float/-O3 \ + arm-sim/-msoft-float' </pre> <p>They can be combined as many times as you wish, in arbitrary ways. This list: |