diff -Nrcpad gcc-4.2.2/BUGS gcc-4.2.3/BUGS *** gcc-4.2.2/BUGS Sun Oct 7 21:23:19 2007 --- gcc-4.2.3/BUGS Fri Feb 1 17:06:58 2008 *************** *** 1,9 **** ! GCC Bugs ! ! The latest version of this document is always available at [1]http://gcc.gnu.org/bugs.html. ! _________________________________________________________________ Table of Contents --- 1,8 ---- + GCC Bugs ! The latest version of this document is always available at [1]http://gcc.gnu.org/bugs.html. ! __________________________________________________________________ Table of Contents *************** Table of Contents *** 13,51 **** + [5]Where to post it + [6]Detailed bug reporting instructions + [7]Detailed bug reporting instructions for GNAT ! + [8]Detailed bug reporting instructions when using a precompiled ! header * [9]Frequently Reported Bugs in GCC ! + [10]C++ ! o [11]Missing features ! o [12]Bugs fixed in the 3.4 series ! + [13]Fortran ! * [14]Non-bugs ! + [15]General ! + [16]C ! + [17]C++ ! o [18]Common problems when upgrading the compiler ! _________________________________________________________________ ! Reporting Bugs ! The main purpose of a bug report is to enable us to fix the bug. The most ! important prerequisite for this is that the report must be complete and ! self-contained. ! Before you report a bug, please check the [19]list of well-known bugs and, ! if possible, try a current development snapshot. If you want to report a bug ! with versions of GCC before 3.4 we strongly recommend upgrading to the ! current release first. ! Before reporting that GCC compiles your code incorrectly, please compile it ! with gcc -Wall and see whether this shows anything wrong with your code that ! could be the cause instead of a bug in GCC. Summarized bug reporting instructions ! After this summary, you'll find detailed bug reporting instructions, that ! explain how to obtain some of the information requested in this summary. What we need --- 12,48 ---- + [5]Where to post it + [6]Detailed bug reporting instructions + [7]Detailed bug reporting instructions for GNAT ! + [8]Detailed bug reporting instructions when using a ! precompiled header * [9]Frequently Reported Bugs in GCC ! + [10]Fortran ! * [11]Non-bugs ! + [12]General ! + [13]C ! + [14]C++ ! o [15]Common problems when upgrading the compiler ! __________________________________________________________________ ! Reporting Bugs ! The main purpose of a bug report is to enable us to fix the bug. The ! most important prerequisite for this is that the report must be ! complete and self-contained. ! Before you report a bug, please check the [16]list of well-known bugs ! and, if possible, try a current development snapshot. If you want to ! report a bug with versions of GCC before 3.4 we strongly recommend ! upgrading to the current release first. ! Before reporting that GCC compiles your code incorrectly, please ! compile it with gcc -Wall and see whether this shows anything wrong ! with your code that could be the cause instead of a bug in GCC. Summarized bug reporting instructions ! After this summary, you'll find detailed bug reporting instructions, ! that explain how to obtain some of the information requested in this ! summary. What we need *************** Summarized bug reporting instructions *** 56,311 **** * the options given when GCC was configured/built; * the complete command line that triggers the bug; * the compiler output (error messages, warnings, etc.); and ! * the preprocessed file (*.i*) that triggers the bug, generated by adding ! -save-temps to the complete compilation command, or, in the case of a ! bug report for the GNAT front end, a complete set of source files (see ! below). What we do not want ! * A source file that #includes header files that are left out of the bug ! report (see above) * That source file and a collection of header files. ! * An attached archive (tar, zip, shar, whatever) containing all (or some ! :-) of the above. ! * A code snippet that won't cause the compiler to produce the exact output ! mentioned in the bug report (e.g., a snippet with just a few lines ! around the one that apparently triggers the bug, with some pieces ! replaced with ellipses or comments for extra obfuscation :-) ! * The location (URL) of the package that failed to build (we won't download it, anyway, since you've already given us what we need to duplicate the bug, haven't you? :-) ! * An error that occurs only some of the times a certain file is compiled, ! such that retrying a sufficient number of times results in a successful ! compilation; this is a symptom of a hardware problem, not of a compiler ! bug (sorry) ! * Assembly files (*.s) produced by the compiler, or any binary files, such ! as object files, executables, core files, or precompiled header files ! * Duplicate bug reports, or reports of bugs already fixed in the ! development tree, especially those that have already been reported as ! fixed last week :-) ! * Bugs in the assembler, the linker or the C library. These are separate ! projects, with separate mailing lists and different bug reporting ! procedures * Bugs in releases or snapshots of GCC not issued by the GNU Project. Report them to whoever provided you with the release * Questions about the correctness or the expected behavior of certain ! constructs that are not GCC extensions. Ask them in forums dedicated to ! the discussion of the programming language Where to post it ! Please submit your bug report directly to the [20]GCC bug database. ! Alternatively, you can use the gccbug script that mails your bug report to ! the bug database. ! Only if all this is absolutely impossible, mail all information to ! [21]gcc-bugs@gcc.gnu.org. Detailed bug reporting instructions ! Please refer to the [22]next section when reporting bugs in GNAT, the Ada ! compiler, or to the [23]one after that when reporting bugs that appear when ! using a precompiled header. ! In general, all the information we need can be obtained by collecting the ! command line below, as well as its output and the preprocessed file it ! generates. gcc -v -save-temps all-your-options source-file ! The only excuses to not send us the preprocessed sources are (i) if you've ! found a bug in the preprocessor, (ii) if you've reduced the testcase to a ! small file that doesn't include any other file or (iii) if the bug appears ! only when using precompiled headers. If you can't post the preprocessed ! sources because they're proprietary code, then try to create a small file ! that triggers the same problem. ! Since we're supposed to be able to re-create the assembly output (extension ! .s), you usually should not include it in the bug report, although you may ! want to post parts of it to point out assembly code you consider to be ! wrong. ! Please avoid posting an archive (.tar, .shar or .zip); we generally need ! just a single file to reproduce the bug (the .i/.ii/.f preprocessed file), ! and, by storing it in an archive, you're just making our volunteers' jobs ! harder. Only when your bug report requires multiple source files to be ! reproduced should you use an archive. This is, for example, the case if you ! are using INCLUDE directives in Fortran code, which are not processed by the ! preprocessor, but the compiler. In that case, we need the main file and all ! INCLUDEd files. In any case, make sure the compiler version, error message, ! etc, are included in the body of your bug report as plain text, even if needlessly duplicated as part of an archive. Detailed bug reporting instructions for GNAT ! See the [24]previous section for bug reporting instructions for GCC language ! implementations other than Ada. ! Bug reports have to contain at least the following information in order to ! be useful: * the exact version of GCC, as shown by "gcc -v"; * the system type; * the options when GCC was configured/built; ! * the exact command line passed to the gcc program triggering the bug (not ! just the flags passed to gnatmake, but gnatmake prints the parameters it ! passed to gcc) * a collection of source files for reproducing the bug, preferably a minimal set (see below); * a description of the expected behavior; * a description of actual behavior. ! If your code depends on additional source files (usually package ! specifications), submit the source code for these compilation units in a ! single file that is acceptable input to gnatchop, i.e. contains no non-Ada ! text. If the compilation terminated normally, you can usually obtain a list ! of dependencies using the "gnatls -d main_unit" command, where main_unit is ! the file name of the main compilation unit (which is also passed to gcc). ! If you report a bug which causes the compiler to print a bug box, include ! that bug box in your report, and do not forget to send all the source files ! listed after the bug box along with your report. ! If you use gnatprep, be sure to send in preprocessed sources (unless you ! have to report a bug in gnatprep). ! When you have checked that your report meets these criteria, please submit ! it according to our [25]generic instructions. (If you use a mailing list for ! reporting, please include an "[Ada]" tag in the subject.) Detailed bug reporting instructions when using a precompiled header If you're encountering a bug when using a precompiled header, the first ! thing to do is to delete the precompiled header, and try running the same ! GCC command again. If the bug happens again, the bug doesn't really involve ! precompiled headers, please report it without using them by following the ! instructions [26]above. ! If you've found a bug while building a precompiled header (for instance, the ! compiler crashes), follow the usual instructions [27]above. ! If you've found a real precompiled header bug, what we'll need to reproduce ! it is the sources to build the precompiled header (as a single .i file), the ! source file that uses the precompiled header, any other headers that source ! file includes, and the command lines that you used to build the precompiled ! header and to use it. ! Please don't send us the actual precompiled header. It is likely to be very ! large and we can't use it to reproduce the problem. ! _________________________________________________________________ Frequently Reported Bugs in GCC This is a list of bugs in GCC that are reported very often, but not yet ! fixed. While it is certainly better to fix bugs instead of documenting them, ! this document might save people the effort of writing a bug report when the ! bug is already well-known. ! There are many reasons why a reported bug doesn't get fixed. It might be ! difficult to fix, or fixing it might break compatibility. Often, reports get ! a low priority when there is a simple work-around. In particular, bugs ! caused by invalid code have a simple work-around: fix the code. ! _________________________________________________________________ C++ ! ! Missing features ! ! The export keyword is not implemented. ! Most C++ compilers (G++ included) do not yet implement export, which ! is necessary for separate compilation of template declarations and ! definitions. Without export, a template definition must be in scope ! to be used. The obvious workaround is simply to place all definitions ! in the header itself. Alternatively, the compilation unit containing ! template definitions may be included from the header. ! ! Bugs fixed in the 3.4 series ! ! The following bugs are present up to (and including) GCC 3.3.x. They have ! been fixed in 3.4.0. ! ! Two-stage name-lookup. ! GCC did not implement two-stage name-lookup (also see [28]below). ! ! Covariant return types. ! GCC did not implement non-trivial covariant returns. ! ! Parse errors for "simple" code. ! GCC gave parse errors for seemingly simple code, such as ! ! struct A ! { ! A(); ! A(int); ! }; ! ! struct B ! { ! B(A); ! B(A,A); ! void foo(); ! }; ! ! A bar() ! { ! B b(A(),A(1)); // Variable b, initialized with two temporaries ! B(A(2)).foo(); // B temporary, initialized with A temporary ! return (A()); // return A temporary ! } ! ! Although being valid code, each of the three lines with a comment was ! rejected by GCC. The work-arounds for older compiler versions ! proposed below do not change the semantics of the programs at all. ! ! The problem in the first case was that GCC started to parse the ! declaration of b as a function called b returning B, taking a ! function returning A as an argument. When it encountered the 1, it ! was too late. To show the compiler that this should be really an ! expression, a comma operator with a dummy argument could be used: ! ! B b((0,A()),A(1)); ! ! The work-around for simpler cases like the second one was to add ! additional parentheses around the expressions that were mistaken as ! declarations: ! ! (B(A(2))).foo(); ! ! In the third case, however, additional parentheses were causing the ! problems: The compiler interpreted A() as a function (taking no ! arguments, returning A), and (A()) as a cast lacking an expression to ! be casted, hence the parse error. The work-around was to omit the ! parentheses: ! ! return A(); ! ! This problem occurred in a number of variants; in throw statements, ! people also frequently put the object in parentheses. ! _________________________________________________________________ Fortran G77 bugs are documented in the G77 manual rather than explicitly listed ! here. Please see [29]Known Causes of Trouble with GNU Fortran in the G77 ! manual. ! _________________________________________________________________ ! Non-bugs ! The following are not actually bugs, but are reported often enough to warrant a mention here. ! It is not always a bug in the compiler, if code which "worked" in a previous ! version, is now rejected. Earlier versions of GCC sometimes were less picky ! about standard conformance and accepted invalid source code. In addition, ! programming languages themselves change, rendering code invalid that used to ! be conforming (this holds especially for C++). In either case, you should ! update your code to match recent language standards. ! _________________________________________________________________ General ! Problems with floating point numbers - the [30]most often reported non-bug. ! In a number of cases, GCC appears to perform floating point computations incorrectly. For example, the C++ program #include --- 53,243 ---- * the options given when GCC was configured/built; * the complete command line that triggers the bug; * the compiler output (error messages, warnings, etc.); and ! * the preprocessed file (*.i*) that triggers the bug, generated by ! adding -save-temps to the complete compilation command, or, in the ! case of a bug report for the GNAT front end, a complete set of ! source files (see below). What we do not want ! * A source file that #includes header files that are left out of the ! bug report (see above) * That source file and a collection of header files. ! * An attached archive (tar, zip, shar, whatever) containing all (or ! some :-) of the above. ! * A code snippet that won't cause the compiler to produce the exact ! output mentioned in the bug report (e.g., a snippet with just a few ! lines around the one that apparently triggers the bug, with some ! pieces replaced with ellipses or comments for extra obfuscation :-) ! * The location (URL) of the package that failed to build (we won't download it, anyway, since you've already given us what we need to duplicate the bug, haven't you? :-) ! * An error that occurs only some of the times a certain file is ! compiled, such that retrying a sufficient number of times results ! in a successful compilation; this is a symptom of a hardware ! problem, not of a compiler bug (sorry) ! * Assembly files (*.s) produced by the compiler, or any binary files, ! such as object files, executables, core files, or precompiled ! header files ! * Duplicate bug reports, or reports of bugs already fixed in the ! development tree, especially those that have already been reported ! as fixed last week :-) ! * Bugs in the assembler, the linker or the C library. These are ! separate projects, with separate mailing lists and different bug ! reporting procedures * Bugs in releases or snapshots of GCC not issued by the GNU Project. Report them to whoever provided you with the release * Questions about the correctness or the expected behavior of certain ! constructs that are not GCC extensions. Ask them in forums ! dedicated to the discussion of the programming language Where to post it ! Please submit your bug report directly to the [17]GCC bug database. ! Alternatively, you can use the gccbug script that mails your bug report ! to the bug database. ! Only if all this is absolutely impossible, mail all information to ! [18]gcc-bugs@gcc.gnu.org. Detailed bug reporting instructions ! Please refer to the [19]next section when reporting bugs in GNAT, the ! Ada compiler, or to the [20]one after that when reporting bugs that ! appear when using a precompiled header. ! In general, all the information we need can be obtained by collecting ! the command line below, as well as its output and the preprocessed file ! it generates. gcc -v -save-temps all-your-options source-file ! The only excuses to not send us the preprocessed sources are (i) if ! you've found a bug in the preprocessor, (ii) if you've reduced the ! testcase to a small file that doesn't include any other file or (iii) ! if the bug appears only when using precompiled headers. If you can't ! post the preprocessed sources because they're proprietary code, then ! try to create a small file that triggers the same problem. ! Since we're supposed to be able to re-create the assembly output ! (extension .s), you usually should not include it in the bug report, ! although you may want to post parts of it to point out assembly code ! you consider to be wrong. ! Please avoid posting an archive (.tar, .shar or .zip); we generally ! need just a single file to reproduce the bug (the .i/.ii/.f ! preprocessed file), and, by storing it in an archive, you're just ! making our volunteers' jobs harder. Only when your bug report requires ! multiple source files to be reproduced should you use an archive. This ! is, for example, the case if you are using INCLUDE directives in ! Fortran code, which are not processed by the preprocessor, but the ! compiler. In that case, we need the main file and all INCLUDEd files. ! In any case, make sure the compiler version, error message, etc, are ! included in the body of your bug report as plain text, even if needlessly duplicated as part of an archive. Detailed bug reporting instructions for GNAT ! See the [21]previous section for bug reporting instructions for GCC ! language implementations other than Ada. ! Bug reports have to contain at least the following information in order ! to be useful: * the exact version of GCC, as shown by "gcc -v"; * the system type; * the options when GCC was configured/built; ! * the exact command line passed to the gcc program triggering the bug ! (not just the flags passed to gnatmake, but gnatmake prints the ! parameters it passed to gcc) * a collection of source files for reproducing the bug, preferably a minimal set (see below); * a description of the expected behavior; * a description of actual behavior. ! If your code depends on additional source files (usually package ! specifications), submit the source code for these compilation units in ! a single file that is acceptable input to gnatchop, i.e. contains no ! non-Ada text. If the compilation terminated normally, you can usually ! obtain a list of dependencies using the "gnatls -d main_unit" command, ! where main_unit is the file name of the main compilation unit (which is ! also passed to gcc). ! If you report a bug which causes the compiler to print a bug box, ! include that bug box in your report, and do not forget to send all the ! source files listed after the bug box along with your report. ! If you use gnatprep, be sure to send in preprocessed sources (unless ! you have to report a bug in gnatprep). ! When you have checked that your report meets these criteria, please ! submit it according to our [22]generic instructions. (If you use a ! mailing list for reporting, please include an "[Ada]" tag in the ! subject.) Detailed bug reporting instructions when using a precompiled header If you're encountering a bug when using a precompiled header, the first ! thing to do is to delete the precompiled header, and try running the ! same GCC command again. If the bug happens again, the bug doesn't ! really involve precompiled headers, please report it without using them ! by following the instructions [23]above. ! If you've found a bug while building a precompiled header (for ! instance, the compiler crashes), follow the usual instructions ! [24]above. ! If you've found a real precompiled header bug, what we'll need to ! reproduce it is the sources to build the precompiled header (as a ! single .i file), the source file that uses the precompiled header, any ! other headers that source file includes, and the command lines that you ! used to build the precompiled header and to use it. ! Please don't send us the actual precompiled header. It is likely to be ! very large and we can't use it to reproduce the problem. ! __________________________________________________________________ Frequently Reported Bugs in GCC This is a list of bugs in GCC that are reported very often, but not yet ! fixed. While it is certainly better to fix bugs instead of documenting ! them, this document might save people the effort of writing a bug ! report when the bug is already well-known. ! There are many reasons why a reported bug doesn't get fixed. It might ! be difficult to fix, or fixing it might break compatibility. Often, ! reports get a low priority when there is a simple work-around. In ! particular, bugs caused by invalid code have a simple work-around: fix ! the code. ! __________________________________________________________________ C++ ! __________________________________________________________________ Fortran G77 bugs are documented in the G77 manual rather than explicitly listed ! here. Please see [25]Known Causes of Trouble with GNU Fortran in the ! G77 manual. ! __________________________________________________________________ ! Non-bugs ! The following are not actually bugs, but are reported often enough to warrant a mention here. ! It is not always a bug in the compiler, if code which "worked" in a ! previous version, is now rejected. Earlier versions of GCC sometimes ! were less picky about standard conformance and accepted invalid source ! code. In addition, programming languages themselves change, rendering ! code invalid that used to be conforming (this holds especially for ! C++). In either case, you should update your code to match recent ! language standards. ! __________________________________________________________________ General ! Problems with floating point numbers - the [26]most often reported ! non-bug. ! In a number of cases, GCC appears to perform floating point computations incorrectly. For example, the C++ program #include *************** int main() *** 318,340 **** return 0; } ! might print 50 on some systems and optimization levels, and 49 on ! others. ! This is the result of rounding: The computer cannot represent all ! real numbers exactly, so it has to use approximations. When computing ! with approximation, the computer needs to round to the nearest ! representable number. ! This is not a bug in the compiler, but an inherent limitation of the ! floating point types. Please study [31]this paper for more information. ! _________________________________________________________________ C ! Increment/decrement operator (++/--) not working as expected - a [32]problem ! with many variations. The following expressions have unpredictable results: x[i]=++i --- 250,272 ---- return 0; } ! might print 50 on some systems and optimization levels, and 49 ! on others. ! This is the result of rounding: The computer cannot represent ! all real numbers exactly, so it has to use approximations. When ! computing with approximation, the computer needs to round to the ! nearest representable number. ! This is not a bug in the compiler, but an inherent limitation of ! the floating point types. Please study [27]this paper for more information. ! __________________________________________________________________ C ! Increment/decrement operator (++/--) not working as expected - a ! [28]problem with many variations. The following expressions have unpredictable results: x[i]=++i *************** foo(i,++i) *** 342,373 **** i*(++i) /* special case with foo=="operator*" */ std::cout << i << ++i /* foo(foo(std::cout,i),++i) */ ! since the i without increment can be evaluated before or after ++i. ! The C and C++ standards have the notion of "sequence points". ! Everything that happens between two sequence points happens in an ! unspecified order, but it has to happen after the first and before ! the second sequence point. The end of a statement and a function call ! are examples for sequence points, whereas assignments and the comma ! between function arguments are not. ! Modifying a value twice between two sequence points as shown in the ! following examples is even worse: i=++i foo(++i,++i) (++i)*(++i) /* special case with foo=="operator*" */ std::cout << ++i << ++i /* foo(foo(std::cout,++i),++i) */ ! This leads to undefined behavior (i.e. the compiler can do anything). Casting does not work as expected when optimization is turned on. ! This is often caused by a violation of aliasing rules, which are part ! of the ISO C standard. These rules say that a program is invalid if ! you try to access a variable through a pointer of an incompatible ! type. This is happening in the following example where a short is ! accessed through a pointer to integer (the code assumes 16-bit shorts ! and 32-bit ints): #include --- 274,307 ---- i*(++i) /* special case with foo=="operator*" */ std::cout << i << ++i /* foo(foo(std::cout,i),++i) */ ! since the i without increment can be evaluated before or after ! ++i. ! The C and C++ standards have the notion of "sequence points". ! Everything that happens between two sequence points happens in ! an unspecified order, but it has to happen after the first and ! before the second sequence point. The end of a statement and a ! function call are examples for sequence points, whereas ! assignments and the comma between function arguments are not. ! Modifying a value twice between two sequence points as shown in ! the following examples is even worse: i=++i foo(++i,++i) (++i)*(++i) /* special case with foo=="operator*" */ std::cout << ++i << ++i /* foo(foo(std::cout,++i),++i) */ ! This leads to undefined behavior (i.e. the compiler can do ! anything). Casting does not work as expected when optimization is turned on. ! This is often caused by a violation of aliasing rules, which are ! part of the ISO C standard. These rules say that a program is ! invalid if you try to access a variable through a pointer of an ! incompatible type. This is happening in the following example ! where a short is accessed through a pointer to integer (the code ! assumes 16-bit shorts and 32-bit ints): #include *************** int main() *** 384,417 **** return 0; } ! The aliasing rules were designed to allow compilers more aggressive ! optimization. Basically, a compiler can assume that all changes to ! variables happen through pointers or references to variables of a ! type compatible to the accessed variable. Dereferencing a pointer ! that violates the aliasing rules results in undefined behavior. ! In the case above, the compiler may assume that no access through an ! integer pointer can change the array a, consisting of shorts. Thus, ! printf may be called with the original values of a[0] and a[1]. What ! really happens is up to the compiler and may change with architecture ! and optimization level. ! Recent versions of GCC turn on the option -fstrict-aliasing (which ! allows alias-based optimizations) by default with -O2. And some ! architectures then really print "1111 1111" as result. Without ! optimization the executable will generate the "expected" output "2222 ! 2222". ! To disable optimizations based on alias-analysis for faulty legacy ! code, the option -fno-strict-aliasing can be used as a work-around. ! The option -Wstrict-aliasing (which is included in -Wall) warns about ! some - but not all - cases of violation of aliasing rules when ! -fstrict-aliasing is active. ! To fix the code above, you can use a union instead of a cast (note ! that this is a GCC extension which might not work with other ! compilers): #include --- 318,353 ---- return 0; } ! The aliasing rules were designed to allow compilers more ! aggressive optimization. Basically, a compiler can assume that ! all changes to variables happen through pointers or references ! to variables of a type compatible to the accessed variable. ! Dereferencing a pointer that violates the aliasing rules results ! in undefined behavior. ! In the case above, the compiler may assume that no access ! through an integer pointer can change the array a, consisting of ! shorts. Thus, printf may be called with the original values of ! a[0] and a[1]. What really happens is up to the compiler and may ! change with architecture and optimization level. ! Recent versions of GCC turn on the option -fstrict-aliasing ! (which allows alias-based optimizations) by default with -O2. ! And some architectures then really print "1111 1111" as result. ! Without optimization the executable will generate the "expected" ! output "2222 2222". ! To disable optimizations based on alias-analysis for faulty ! legacy code, the option -fno-strict-aliasing can be used as a ! work-around. ! The option -Wstrict-aliasing (which is included in -Wall) warns ! about some - but not all - cases of violation of aliasing rules ! when -fstrict-aliasing is active. ! To fix the code above, you can use a union instead of a cast ! (note that this is a GCC extension which might not work with ! other compilers): #include *************** int main() *** 434,445 **** Now the result will always be "2222 2222". ! For some more insight into the subject, please have a look at ! [33]this article. Cannot use preprocessor directive in macro arguments. ! Let me guess... you used an older version of GCC to compile code that ! looks something like this: memcpy(dest, src, #ifdef PLATFORM1 --- 370,381 ---- Now the result will always be "2222 2222". ! For some more insight into the subject, please have a look at ! [29]this article. Cannot use preprocessor directive in macro arguments. ! Let me guess... you used an older version of GCC to compile code ! that looks something like this: memcpy(dest, src, #ifdef PLATFORM1 *************** test.c:8: undefined or invalid # directi *** 460,483 **** test.c:9: parse error before `24' test.c:10: undefined or invalid # directive ! This is because your C library's happens to define memcpy ! as a macro - which is perfectly legitimate. In recent versions of ! glibc, for example, printf is among those functions which are ! implemented as macros. ! Versions of GCC prior to 3.3 did not allow you to put #ifdef (or any ! other preprocessor directive) inside the arguments of a macro. The ! code therefore would not compile. As of GCC 3.3 this kind of construct is always accepted and the ! preprocessor will probably do what you expect, but see the manual for ! detailed semantics. ! However, this kind of code is not portable. It is "undefined ! behavior" according to the C standard; that means different compilers ! may do different things with it. It is always possible to rewrite ! code which uses conditionals inside macros so that it doesn't. You ! could write the above example #ifdef PLATFORM1 memcpy(dest, src, 12); --- 396,419 ---- test.c:9: parse error before `24' test.c:10: undefined or invalid # directive ! This is because your C library's happens to define ! memcpy as a macro - which is perfectly legitimate. In recent ! versions of glibc, for example, printf is among those functions ! which are implemented as macros. ! Versions of GCC prior to 3.3 did not allow you to put #ifdef (or ! any other preprocessor directive) inside the arguments of a ! macro. The code therefore would not compile. As of GCC 3.3 this kind of construct is always accepted and the ! preprocessor will probably do what you expect, but see the ! manual for detailed semantics. ! However, this kind of code is not portable. It is "undefined ! behavior" according to the C standard; that means different ! compilers may do different things with it. It is always possible ! to rewrite code which uses conditionals inside macros so that it ! doesn't. You could write the above example #ifdef PLATFORM1 memcpy(dest, src, 12); *************** test.c:10: undefined or invalid # direct *** 485,569 **** memcpy(dest, src, 24); #endif ! This is a bit more typing, but I personally think it's better style ! in addition to being more portable. Cannot initialize a static variable with stdin. ! This has nothing to do with GCC, but people ask us about it a lot. ! Code like this: #include FILE *yyin = stdin; ! will not compile with GNU libc, because stdin is not a constant. This ! was done deliberately, to make it easier to maintain binary ! compatibility when the type FILE needs to be changed. It is ! surprising for people used to traditional Unix C libraries, but it is ! permitted by the C standard. ! This construct commonly occurs in code generated by old versions of ! lex or yacc. We suggest you try regenerating the parser with a ! current version of flex or bison, respectively. In your own code, the ! appropriate fix is to move the initialization to the beginning of ! main. ! There is a common misconception that the GCC developers are ! responsible for GNU libc. These are in fact two entirely separate ! projects; please check the [34]GNU libc web pages for details. ! _________________________________________________________________ C++ ! Nested classes can access private members and types of the containing class. ! Defect report 45 clarifies that nested classes are members of the ! class they are nested in, and so are granted access to private ! members of that class. G++ emits two copies of constructors and destructors. ! In general there are three types of constructors (and destructors). 1. The complete object constructor/destructor. 2. The base object constructor/destructor. 3. The allocating constructor/deallocating destructor. ! The first two are different, when virtual base classes are involved. Global destructors are not run in the correct order. ! Global destructors should be run in the reverse order of their ! constructors completing. In most cases this is the same as the ! reverse order of constructors starting, but sometimes it is ! different, and that is important. You need to compile and link your ! programs with --use-cxa-atexit. We have not turned this switch on by ! default, as it requires a cxa aware runtime library (libc, glibc, or ! equivalent). Classes in exception specifiers must be complete types. ! [15.4]/1 tells you that you cannot have an incomplete type, or ! pointer to incomplete (other than cv void *) in an exception specification. Exceptions don't work in multithreaded applications. ! You need to rebuild g++ and libstdc++ with --enable-threads. ! Remember, C++ exceptions are not like hardware interrupts. You cannot ! throw an exception in one thread and catch it in another. You cannot ! throw an exception from a signal handler and catch it in the main ! thread. Templates, scoping, and digraphs. ! If you have a class in the global namespace, say named X, and want to ! give it as a template argument to some other class, say std::vector, ! then std::vector<::X> fails with a parser error. The reason is that the standard mandates that the sequence <: is ! treated as if it were the token [. (There are several such ! combinations of characters - they are called digraphs.) Depending on ! the version, the compiler then reports a parse error before the ! character : (the colon before X) or a missing closing bracket ]. ! The simplest way to avoid this is to write std::vector< ::X>, i.e. ! place a space between the opening angle bracket and the scope ! operator. Copy constructor access check while initializing a reference. Consider this code: --- 421,518 ---- memcpy(dest, src, 24); #endif ! This is a bit more typing, but I personally think it's better ! style in addition to being more portable. Cannot initialize a static variable with stdin. ! This has nothing to do with GCC, but people ask us about it a ! lot. Code like this: #include FILE *yyin = stdin; ! will not compile with GNU libc, because stdin is not a constant. ! This was done deliberately, to make it easier to maintain binary ! compatibility when the type FILE needs to be changed. It is ! surprising for people used to traditional Unix C libraries, but ! it is permitted by the C standard. ! This construct commonly occurs in code generated by old versions ! of lex or yacc. We suggest you try regenerating the parser with ! a current version of flex or bison, respectively. In your own ! code, the appropriate fix is to move the initialization to the ! beginning of main. ! There is a common misconception that the GCC developers are ! responsible for GNU libc. These are in fact two entirely ! separate projects; please check the [30]GNU libc web pages for ! details. ! __________________________________________________________________ C++ ! Most C++ compilers (G++ included) do not yet implement export, ! which is necessary for separate compilation of template ! declarations and definitions. Without export, a template ! definition must be in scope to be used. The obvious workaround ! is simply to place all definitions in the header itself. ! Alternatively, the compilation unit containing template ! definitions may be included from the header. ! ! Nested classes can access private members and types of the containing ! class. ! Defect report 45 clarifies that nested classes are members of ! the class they are nested in, and so are granted access to ! private members of that class. G++ emits two copies of constructors and destructors. ! In general there are three types of constructors (and ! destructors). 1. The complete object constructor/destructor. 2. The base object constructor/destructor. 3. The allocating constructor/deallocating destructor. ! The first two are different, when virtual base classes are ! involved. Global destructors are not run in the correct order. ! Global destructors should be run in the reverse order of their ! constructors completing. In most cases this is the same as the ! reverse order of constructors starting, but sometimes it is ! different, and that is important. You need to compile and link ! your programs with --use-cxa-atexit. We have not turned this ! switch on by default, as it requires a cxa aware runtime library ! (libc, glibc, or equivalent). Classes in exception specifiers must be complete types. ! [15.4]/1 tells you that you cannot have an incomplete type, or ! pointer to incomplete (other than cv void *) in an exception specification. Exceptions don't work in multithreaded applications. ! You need to rebuild g++ and libstdc++ with --enable-threads. ! Remember, C++ exceptions are not like hardware interrupts. You ! cannot throw an exception in one thread and catch it in another. ! You cannot throw an exception from a signal handler and catch it ! in the main thread. Templates, scoping, and digraphs. ! If you have a class in the global namespace, say named X, and ! want to give it as a template argument to some other class, say ! std::vector, then std::vector<::X> fails with a parser error. The reason is that the standard mandates that the sequence <: is ! treated as if it were the token [. (There are several such ! combinations of characters - they are called digraphs.) ! Depending on the version, the compiler then reports a parse ! error before the character : (the colon before X) or a missing ! closing bracket ]. ! The simplest way to avoid this is to write std::vector< ::X>, ! i.e. place a space between the opening angle bracket and the ! scope operator. Copy constructor access check while initializing a reference. Consider this code: *************** void bar(void) *** 590,684 **** } Starting with GCC 3.4.0, binding an rvalue to a const reference ! requires an accessible copy constructor. This might be surprising at ! first sight, especially since most popular compilers do not correctly ! implement this rule. ! The C++ Standard says that a temporary object should be created in ! this context and its contents filled with a copy of the object we are ! trying to bind to the reference; it also says that the temporary copy ! can be elided, but the semantic constraints (eg. accessibility) of ! the copy constructor still have to be checked. ! For further information, you can consult the following paragraphs of ! the C++ standard: [dcl.init.ref]/5, bullet 2, sub-bullet 1, and ! [class.temporary]/2. Common problems when upgrading the compiler ABI changes ! The C++ application binary interface (ABI) consists of two components: the ! first defines how the elements of classes are laid out, how functions are ! called, how function names are mangled, etc; the second part deals with the ! internals of the objects in libstdc++. Although we strive for a non-changing ! ABI, so far we have had to modify it with each major release. If you change ! your compiler to a different major release you must recompile all libraries ! that contain C++ code. If you fail to do so you risk getting linker errors ! or malfunctioning programs. Some of our Java support libraries also contain ! C++ code, so you might want to recompile all libraries to be safe. It should ! not be necessary to recompile if you have changed to a bug-fix release of ! the same version of the compiler; bug-fix releases are careful to avoid ABI ! changes. See also the [35]compatibility section of the GCC manual. ! Remark: A major release is designated by a change to the first or second ! component of the two- or three-part version number. A minor (bug-fix) ! release is designated by a change to the third component only. Thus GCC 3.2 ! and 3.3 are major releases, while 3.3.1 and 3.3.2 are bug-fix releases for ! GCC 3.3. With the 3.4 series we are introducing a new naming scheme; the ! first release of this series is 3.4.0 instead of just 3.4. Standard conformance ! With each release, we try to make G++ conform closer to the ISO C++ standard ! (available at [36]http://www.ncits.org/cplusplus.htm). We have also ! implemented some of the core and library defect reports (available at ! [37]http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html & ! [38]http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html respectively). ! Non-conforming legacy code that worked with older versions of GCC may be ! rejected by more recent compilers. There is no command-line switch to ensure ! compatibility in general, because trying to parse standard-conforming and ! old-style code at the same time would render the C++ frontend ! unmaintainable. However, some non-conforming constructs are allowed when the ! command-line option -fpermissive is used. ! Two milestones in standard conformance are GCC 3.0 (including a major ! overhaul of the standard library) and the 3.4.0 version (with its new C++ ! parser). New in GCC 3.0 ! * The standard library is much more conformant, and uses the std:: namespace (which is now a real namespace, not an alias for ::). ! * The standard header files for the c library don't end with .h, but begin ! with c (i.e. rather than ). The .h names are still ! available, but are deprecated. * is deprecated, use instead. ! * streambuf::seekoff & streambuf::seekpos are private, instead use streambuf::pubseekoff & streambuf::pubseekpos respectively. ! * If std::operator << (std::ostream &, long long) doesn't exist, you need ! to recompile libstdc++ with --enable-long-long. ! If you get lots of errors about things like cout not being found, you've ! most likely forgotten to tell the compiler to look in the std:: namespace. ! There are several ways to do this: ! * Say std::cout at the call. This is the most explicit way of saying what ! you mean. ! * Say using std::cout; somewhere before the call. You will need to do this ! for each function or type you wish to use from the standard library. ! * Say using namespace std; somewhere before the call. This is the ! quick-but-dirty fix. This brings the whole of the std:: namespace into ! scope. Never do this in a header file, as every user of your header file ! will be affected by this decision. New in GCC 3.4.0 ! The new parser brings a lot of improvements, especially concerning name-lookup. ! * The "implicit typename" extension got removed (it was already deprecated ! since GCC 3.1), so that the following code is now rejected, see [14.6]: template struct A { --- 539,639 ---- } Starting with GCC 3.4.0, binding an rvalue to a const reference ! requires an accessible copy constructor. This might be ! surprising at first sight, especially since most popular ! compilers do not correctly implement this rule. ! The C++ Standard says that a temporary object should be created ! in this context and its contents filled with a copy of the ! object we are trying to bind to the reference; it also says that ! the temporary copy can be elided, but the semantic constraints ! (eg. accessibility) of the copy constructor still have to be ! checked. ! For further information, you can consult the following ! paragraphs of the C++ standard: [dcl.init.ref]/5, bullet 2, ! sub-bullet 1, and [class.temporary]/2. Common problems when upgrading the compiler ABI changes ! The C++ application binary interface (ABI) consists of two components: ! the first defines how the elements of classes are laid out, how ! functions are called, how function names are mangled, etc; the second ! part deals with the internals of the objects in libstdc++. Although we ! strive for a non-changing ABI, so far we have had to modify it with ! each major release. If you change your compiler to a different major ! release you must recompile all libraries that contain C++ code. If you ! fail to do so you risk getting linker errors or malfunctioning ! programs. Some of our Java support libraries also contain C++ code, so ! you might want to recompile all libraries to be safe. It should not be ! necessary to recompile if you have changed to a bug-fix release of the ! same version of the compiler; bug-fix releases are careful to avoid ABI ! changes. See also the [31]compatibility section of the GCC manual. ! Remark: A major release is designated by a change to the first or ! second component of the two- or three-part version number. A minor ! (bug-fix) release is designated by a change to the third component ! only. Thus GCC 3.2 and 3.3 are major releases, while 3.3.1 and 3.3.2 ! are bug-fix releases for GCC 3.3. With the 3.4 series we are ! introducing a new naming scheme; the first release of this series is ! 3.4.0 instead of just 3.4. Standard conformance ! With each release, we try to make G++ conform closer to the ISO C++ ! standard (available at [32]http://www.ncits.org/cplusplus.htm). We have ! also implemented some of the core and library defect reports (available ! at [33]http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html & ! [34]http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html respectively). ! Non-conforming legacy code that worked with older versions of GCC may ! be rejected by more recent compilers. There is no command-line switch ! to ensure compatibility in general, because trying to parse ! standard-conforming and old-style code at the same time would render ! the C++ frontend unmaintainable. However, some non-conforming ! constructs are allowed when the command-line option -fpermissive is ! used. ! Two milestones in standard conformance are GCC 3.0 (including a major ! overhaul of the standard library) and the 3.4.0 version (with its new ! C++ parser). New in GCC 3.0 ! * The standard library is much more conformant, and uses the std:: namespace (which is now a real namespace, not an alias for ::). ! * The standard header files for the c library don't end with .h, but ! begin with c (i.e. rather than ). The .h names ! are still available, but are deprecated. * is deprecated, use instead. ! * streambuf::seekoff & streambuf::seekpos are private, instead use streambuf::pubseekoff & streambuf::pubseekpos respectively. ! * If std::operator << (std::ostream &, long long) doesn't exist, you ! need to recompile libstdc++ with --enable-long-long. ! If you get lots of errors about things like cout not being found, ! you've most likely forgotten to tell the compiler to look in the std:: ! namespace. There are several ways to do this: ! * Say std::cout at the call. This is the most explicit way of saying ! what you mean. ! * Say using std::cout; somewhere before the call. You will need to do ! this for each function or type you wish to use from the standard ! library. ! * Say using namespace std; somewhere before the call. This is the ! quick-but-dirty fix. This brings the whole of the std:: namespace ! into scope. Never do this in a header file, as every user of your ! header file will be affected by this decision. New in GCC 3.4.0 ! The new parser brings a lot of improvements, especially concerning name-lookup. ! * The "implicit typename" extension got removed (it was already ! deprecated since GCC 3.1), so that the following code is now ! rejected, see [14.6]: template struct A { *************** template struct B *** 693,699 **** B b; ! * For similar reasons, the following code now requires the template keyword, see [14.2]: template struct A --- 648,654 ---- B b; ! * For similar reasons, the following code now requires the template keyword, see [14.2]: template struct A *************** template struct B *** 709,715 **** B b; ! * We now have two-stage name-lookup, so that the following code is rejected, see [14.6]/9: template int foo() --- 664,670 ---- B b; ! * We now have two-stage name-lookup, so that the following code is rejected, see [14.6]/9: template int foo() *************** template struct B : A *** 735,742 **** int foo5() { return j; } // OK }; ! In addition to the problems listed above, the manual contains a section on ! [39]Common Misunderstandings with GNU C++. References --- 690,697 ---- int foo5() { return j; } // OK }; ! In addition to the problems listed above, the manual contains a section ! on [35]Common Misunderstandings with GNU C++. References *************** References *** 749,781 **** 7. http://gcc.gnu.org/bugs.html#gnat 8. http://gcc.gnu.org/bugs.html#pch 9. http://gcc.gnu.org/bugs.html#known ! 10. http://gcc.gnu.org/bugs.html#cxx ! 11. http://gcc.gnu.org/bugs.html#missing ! 12. http://gcc.gnu.org/bugs.html#fixed34 ! 13. http://gcc.gnu.org/bugs.html#fortran ! 14. http://gcc.gnu.org/bugs.html#nonbugs ! 15. http://gcc.gnu.org/bugs.html#nonbugs_general ! 16. http://gcc.gnu.org/bugs.html#nonbugs_c ! 17. http://gcc.gnu.org/bugs.html#nonbugs_cxx ! 18. http://gcc.gnu.org/bugs.html#upgrading ! 19. http://gcc.gnu.org/bugs.html#known ! 20. http://gcc.gnu.org/bugzilla/ ! 21. mailto:gcc-bugs@gcc.gnu.org ! 22. http://gcc.gnu.org/bugs.html#gnat ! 23. http://gcc.gnu.org/bugs.html#pch 24. http://gcc.gnu.org/bugs.html#detailed ! 25. http://gcc.gnu.org/bugs.html#where ! 26. http://gcc.gnu.org/bugs.html#detailed ! 27. http://gcc.gnu.org/bugs.html#detailed ! 28. http://gcc.gnu.org/bugs.html#new34 ! 29. http://gcc.gnu.org/onlinedocs/gcc-3.4.6/g77/Trouble.html ! 30. http://gcc.gnu.org/PR323 ! 31. http://www.validlab.com/goldberg/paper.ps ! 32. http://gcc.gnu.org/PR11751 ! 33. http://mail-index.NetBSD.org/tech-kern/2003/08/11/0001.html ! 34. http://www.gnu.org/software/libc/ ! 35. http://gcc.gnu.org/onlinedocs/gcc/Compatibility.html ! 36. http://www.ncits.org/cplusplus.htm ! 37. http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html ! 38. http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html ! 39. http://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Misunderstandings.html --- 704,732 ---- 7. http://gcc.gnu.org/bugs.html#gnat 8. http://gcc.gnu.org/bugs.html#pch 9. http://gcc.gnu.org/bugs.html#known ! 10. http://gcc.gnu.org/bugs.html#fortran ! 11. http://gcc.gnu.org/bugs.html#nonbugs ! 12. http://gcc.gnu.org/bugs.html#nonbugs_general ! 13. http://gcc.gnu.org/bugs.html#nonbugs_c ! 14. http://gcc.gnu.org/bugs.html#nonbugs_cxx ! 15. http://gcc.gnu.org/bugs.html#upgrading ! 16. http://gcc.gnu.org/bugs.html#known ! 17. http://gcc.gnu.org/bugzilla/ ! 18. mailto:gcc-bugs@gcc.gnu.org ! 19. http://gcc.gnu.org/bugs.html#gnat ! 20. http://gcc.gnu.org/bugs.html#pch ! 21. http://gcc.gnu.org/bugs.html#detailed ! 22. http://gcc.gnu.org/bugs.html#where ! 23. http://gcc.gnu.org/bugs.html#detailed 24. http://gcc.gnu.org/bugs.html#detailed ! 25. http://gcc.gnu.org/onlinedocs/gcc-3.4.6/g77/Trouble.html ! 26. http://gcc.gnu.org/PR323 ! 27. http://www.validlab.com/goldberg/paper.ps ! 28. http://gcc.gnu.org/PR11751 ! 29. http://mail-index.NetBSD.org/tech-kern/2003/08/11/0001.html ! 30. http://www.gnu.org/software/libc/ ! 31. http://gcc.gnu.org/onlinedocs/gcc/Compatibility.html ! 32. http://www.ncits.org/cplusplus.htm ! 33. http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html ! 34. http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html ! 35. http://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Misunderstandings.html diff -Nrcpad gcc-4.2.2/ChangeLog gcc-4.2.3/ChangeLog *** gcc-4.2.2/ChangeLog Sun Oct 7 21:20:53 2007 --- gcc-4.2.3/ChangeLog Fri Feb 1 16:51:15 2008 *************** *** 1,3 **** --- 1,7 ---- + 2008-02-01 Release Manager + + * GCC 4.2.3 released. + 2007-10-07 Release Manager * GCC 4.2.2 released. diff -Nrcpad gcc-4.2.2/FAQ gcc-4.2.3/FAQ *** gcc-4.2.2/FAQ Sun Oct 7 21:23:19 2007 --- gcc-4.2.3/FAQ Fri Feb 1 17:06:58 2008 *************** *** 1,15 **** ! GCC Frequently Asked Questions ! ! The latest version of this document is always available at [1]http://gcc.gnu.org/faq.html. This FAQ tries to answer specific questions concerning GCC. For general ! information regarding C, C++, resp. Fortran please check the [2]comp.lang.c ! FAQ, [3]comp.std.c++ FAQ, and the [4]Fortran Information page. Other GCC-related FAQs: [5]libstdc++-v3, and [6]GCJ. ! _________________________________________________________________ Questions --- 1,15 ---- + GCC Frequently Asked Questions ! The latest version of this document is always available at [1]http://gcc.gnu.org/faq.html. This FAQ tries to answer specific questions concerning GCC. For general ! information regarding C, C++, resp. Fortran please check the ! [2]comp.lang.c FAQ, [3]comp.std.c++ FAQ, and the [4]Fortran Information ! page. Other GCC-related FAQs: [5]libstdc++-v3, and [6]GCJ. ! __________________________________________________________________ Questions *************** *** 29,288 **** 2. [20]How can I run the test suite with multiple options? 4. [21]Miscellaneous 1. [22]Friend Templates ! 2. [23]dynamic_cast, throw, typeid don't work with shared libraries 3. [24]Why do I need autoconf, bison, xgettext, automake, etc? 4. [25]Why can't I build a shared library? ! 5. [26]When building C++, the linker says my constructors, destructors ! or virtual tables are undefined, but I defined them ! _________________________________________________________________ General information How do I get a bug fixed or a feature added? ! There are lots of ways to get something fixed. The list below may be ! incomplete, but it covers many of the common cases. These are listed roughly ! in order of decreasing difficulty for the average GCC user, meaning someone ! who is not skilled in the internals of GCC, and where difficulty is measured ! in terms of the time required to fix the bug. No alternative is better than ! any other; each has its benefits and disadvantages. ! * Fix it yourself. This alternative will probably bring results, if you ! work hard enough, but will probably take a lot of time, and, depending ! on the quality of your work and the perceived benefits of your changes, ! your code may or may not ever make it into an official release of GCC. * [27]Report the problem to the GCC bug tracking system and hope that ! someone will be kind enough to fix it for you. While this is certainly ! possible, and often happens, there is no guarantee that it will. You ! should not expect the same response from this method that you would see ! from a commercial support organization since the people who read GCC bug ! reports, if they choose to help you, will be volunteering their time. ! * Hire someone to fix it for you. There are various companies and ! individuals providing support for GCC. This alternative costs money, but ! is relatively likely to get results. ! _________________________________________________________________ Does GCC work on my platform? The host/target specific installation notes for GCC include information ! about known problems with installing or using GCC on particular platforms. ! These are included in the sources for a release in INSTALL/specific.html, ! and the [28]latest version is always available at the GCC web site. Reports ! of [29]successful builds for several versions of GCC are also available at ! the web site. ! _________________________________________________________________ ! Installation How to install multiple versions of GCC ! It may be desirable to install multiple versions of the compiler on the same ! system. This can be done by using different prefix paths at configure time ! and a few symlinks. ! Basically, configure the two compilers with different --prefix options, then ! build and install each compiler. Assume you want "gcc" to be the latest ! compiler and available in /usr/local/bin; also assume that you want "gcc2" ! to be the older gcc2 compiler and also available in /usr/local/bin. ! The easiest way to do this is to configure the new GCC with ! --prefix=/usr/local/gcc and the older gcc2 with --prefix=/usr/local/gcc2. ! Build and install both compilers. Then make a symlink from ! /usr/local/bin/gcc to /usr/local/gcc/bin/gcc and from /usr/local/bin/gcc2 to ! /usr/local/gcc2/bin/gcc. Create similar links for the "g++", "c++" and "g77" ! compiler drivers. ! An alternative to using symlinks is to configure with a --program-transform-name option. This option specifies a sed command to ! process installed program names with. Using it you can, for instance, have ! all the new GCC programs installed as "new-gcc" and the like. You will still ! have to specify different --prefix options for new GCC and old GCC, because ! it is only the executable program names that are transformed. The difference ! is that you (as administrator) do not have to set up symlinks, but must ! specify additional directories in your (as a user) PATH. A complication with ! --program-transform-name is that the sed command invariably contains ! characters significant to the shell, and these have to be escaped correctly, ! also it is not possible to use "^" or "$" in the command. Here is the option ! to prefix "new-" to the new GCC installed programs: --program-transform-name='s,\\\\(.*\\\\),new-\\\\1,' ! With the above --prefix option, that will install the new GCC programs into ! /usr/local/gcc/bin with names prefixed by "new-". You can use ! --program-transform-name if you have multiple versions of GCC, and wish to ! be sure about which version you are invoking. ! If you use --prefix, GCC may have difficulty locating a GNU assembler or ! linker on your system, [30]GCC can not find GNU as/GNU ld explains how to ! deal with this. ! Another option that may be easier is to use the --program-prefix= or ! --program-suffix= options to configure. So if you're installing GCC 2.95.2 ! and don't want to disturb the current version of GCC in /usr/local/bin/, you ! could do configure --program-suffix=-2.95.2 This should result in GCC being installed as /usr/local/bin/gcc-2.95.2 instead of /usr/local/bin/gcc. ! _________________________________________________________________ Dynamic linker is unable to find GCC libraries ! This problem manifests itself by programs not finding shared libraries they ! depend on when the programs are started. Note this problem often manifests ! itself with failures in the libio/libstdc++ tests after configuring with ! --enable-shared and building GCC. ! GCC does not specify a runpath so that the dynamic linker can find dynamic ! libraries at runtime. ! The short explanation is that if you always pass a -R option to the linker, ! then your programs become dependent on directories which may be NFS mounted, ! and programs may hang unnecessarily when an NFS server goes down. ! The problem is not programs that do require the directories; those programs ! are going to hang no matter what you do. The problem is programs that do not ! require the directories. ! SunOS effectively always passed a -R option for every -L option; this was a ! bad idea, and so it was removed for Solaris. We should not recreate it. ! However, if you feel you really need such an option to be passed ! automatically to the linker, you may add it to the GCC specs file. This file ! can be found in the same directory that contains cc1 (run gcc ! -print-prog-name=cc1 to find it). You may add linker flags such as -R or ! -rpath, depending on platform and linker, to the *link or *lib specs. ! Another alternative is to install a wrapper script around gcc, g++ or ld ! that adds the appropriate directory to the environment variable LD_RUN_PATH ! or equivalent (again, it's platform-dependent). ! Yet another option, that works on a few platforms, is to hard-code the full ! pathname of the library into its soname. This can only be accomplished by ! modifying the appropriate .ml file within libstdc++/config (and also ! libg++/config, if you are building libg++), so that $(libdir)/ appears just ! before the library name in -soname or -h options. ! _________________________________________________________________ GCC can not find GNU as/GNU ld ! GCC searches the PATH for an assembler and a loader, but it only does so ! after searching a directory list hard-coded in the GCC executables. Since, ! on most platforms, the hard-coded list includes directories in which the ! system assembler and loader can be found, you may have to take one of the ! following actions to arrange that GCC uses the GNU versions of those ! programs. To ensure that GCC finds the GNU assembler (the GNU loader), which are ! required by [31]some configurations, you should configure these with the ! same --prefix option as you used for GCC. Then build & install GNU as (GNU ! ld) and proceed with building GCC. ! Another alternative is to create links to GNU as and ld in any of the ! directories printed by the command `gcc -print-search-dirs | grep ! '^programs:''. The link to `ld' should be named `real-ld' if `ld' already ! exists. If such links do not exist while you're compiling GCC, you may have ! to create them in the build directories too, within the gcc directory and in ! all the gcc/stage* subdirectories. ! GCC 2.95 allows you to specify the full pathname of the assembler and the ! linker to use. The configure flags are `--with-as=/path/to/as' and ! `--with-ld=/path/to/ld'. GCC will try to use these pathnames before looking ! for `as' or `(real-)ld' in the standard search dirs. If, at configure-time, ! the specified programs are found to be GNU utilities, `--with-gnu-as' and ! `--with-gnu-ld' need not be used; these flags will be auto-detected. One ! drawback of this option is that it won't allow you to override the search ! path for assembler and linker with command-line options -B/path/ if the ! specified filenames exist. ! _________________________________________________________________ cpp: Usage:... Error ! If you get an error like this when building GCC (particularly when building ! __mulsi3), then you likely have a problem with your environment variables. cpp: Usage: /usr/lib/gcc-lib/i586-unknown-linux-gnulibc1/2.7.2.3/cpp [switches] input output ! First look for an explicit '.' in either LIBRARY_PATH or GCC_EXEC_PREFIX ! from your environment. If you do not find an explicit '.', look for an empty ! pathname in those variables. Note that ':' at either the start or end of ! these variables is an implicit '.' and will cause problems. Also note '::' in these paths will also cause similar problems. ! _________________________________________________________________ Optimizing the compiler itself ! If you want to test a particular optimization option, it's useful to try ! bootstrapping the compiler with that option turned on. For example, to test ! the -fssa option, you could bootstrap like this: make BOOT_CFLAGS="-O2 -fssa" bootstrap ! _________________________________________________________________ Why does libiconv get linked into jc1 on Solaris? ! The Java front end requires iconv. If the compiler used to bootstrap GCC ! finds libiconv (because the GNU version of libiconv has been installed in ! the same prefix as the bootstrap compiler), but the newly built GCC does not ! find the library (because it will be installed with a different prefix), ! then a link-time error will occur when building jc1. This problem does not ! show up so often on platforms that have libiconv in a default location (like ! /usr/lib) because then both compilers can find a library named libiconv, ! even though it is a different library. ! Using --disable-nls at configure-time does not prevent this problem because ! jc1 uses iconv even in that case. Solutions include temporarily removing the ! GNU libiconv, copying it to a default location such as /usr/lib/, and using ! --enable-languages at configure-time to disable Java. ! _________________________________________________________________ ! Testsuite problems How do I pass flags like -fnew-abi to the testsuite? ! If you invoke runtest directly, you can use the --tool_opts option, e.g: runtest --tool_opts "-fnew-abi -fno-honor-std" ! Or, if you use make check you can use the make variable RUNTESTFLAGS, e.g: make RUNTESTFLAGS="--tool_opts '-fnew-abi -fno-honor-std'" check-g++ ! _________________________________________________________________ How can I run the test suite with multiple options? ! If you invoke runtest directly, you can use the --target_board option, e.g: runtest --target_board "unix{-fPIC,-fpic,}" ! Or, if you use make check you can use the make variable RUNTESTFLAGS, e.g: make RUNTESTFLAGS="--target_board 'unix{-fPIC,-fpic,}'" check-gcc ! Either of these examples will run the tests three times. Once with -fPIC, ! once with -fpic, and once with no additional flags. This technique is particularly useful on multilibbed targets. ! _________________________________________________________________ Miscellaneous Friend Templates In order to make a specialization of a template function a friend of a ! (possibly template) class, you must explicitly state that the friend ! function is a template, by appending angle brackets to its name, and this ! template function must have been declared already. Here's an example: template class foo { friend void bar(foo); } ! The above declaration declares a non-template function named bar, so it must ! be explicitly defined for each specialization of foo. A template definition ! of bar won't do, because it is unrelated with the non-template declaration ! above. So you'd have to end up writing: void bar(foo) { /* ... */ } void bar(foo) { /* ... */ } ! If you meant bar to be a template function, you should have forward-declared ! it as follows. Note that, since the template function declaration refers to ! the template class, the template class must be forward-declared too: template class foo; --- 29,309 ---- 2. [20]How can I run the test suite with multiple options? 4. [21]Miscellaneous 1. [22]Friend Templates ! 2. [23]dynamic_cast, throw, typeid don't work with shared ! libraries 3. [24]Why do I need autoconf, bison, xgettext, automake, etc? 4. [25]Why can't I build a shared library? ! 5. [26]When building C++, the linker says my constructors, ! destructors or virtual tables are undefined, but I defined ! them ! __________________________________________________________________ General information How do I get a bug fixed or a feature added? ! There are lots of ways to get something fixed. The list below may be ! incomplete, but it covers many of the common cases. These are listed ! roughly in order of decreasing difficulty for the average GCC user, ! meaning someone who is not skilled in the internals of GCC, and where ! difficulty is measured in terms of the time required to fix the bug. No ! alternative is better than any other; each has its benefits and ! disadvantages. ! * Fix it yourself. This alternative will probably bring results, if ! you work hard enough, but will probably take a lot of time, and, ! depending on the quality of your work and the perceived benefits of ! your changes, your code may or may not ever make it into an ! official release of GCC. * [27]Report the problem to the GCC bug tracking system and hope that ! someone will be kind enough to fix it for you. While this is ! certainly possible, and often happens, there is no guarantee that ! it will. You should not expect the same response from this method ! that you would see from a commercial support organization since the ! people who read GCC bug reports, if they choose to help you, will ! be volunteering their time. ! * Hire someone to fix it for you. There are various companies and ! individuals providing support for GCC. This alternative costs ! money, but is relatively likely to get results. ! __________________________________________________________________ Does GCC work on my platform? The host/target specific installation notes for GCC include information ! about known problems with installing or using GCC on particular ! platforms. These are included in the sources for a release in ! INSTALL/specific.html, and the [28]latest version is always available ! at the GCC web site. Reports of [29]successful builds for several ! versions of GCC are also available at the web site. ! __________________________________________________________________ ! Installation How to install multiple versions of GCC ! It may be desirable to install multiple versions of the compiler on the ! same system. This can be done by using different prefix paths at ! configure time and a few symlinks. ! Basically, configure the two compilers with different --prefix options, ! then build and install each compiler. Assume you want "gcc" to be the ! latest compiler and available in /usr/local/bin; also assume that you ! want "gcc2" to be the older gcc2 compiler and also available in ! /usr/local/bin. ! The easiest way to do this is to configure the new GCC with ! --prefix=/usr/local/gcc and the older gcc2 with ! --prefix=/usr/local/gcc2. Build and install both compilers. Then make a ! symlink from /usr/local/bin/gcc to /usr/local/gcc/bin/gcc and from ! /usr/local/bin/gcc2 to /usr/local/gcc2/bin/gcc. Create similar links ! for the "g++", "c++" and "g77" compiler drivers. ! An alternative to using symlinks is to configure with a --program-transform-name option. This option specifies a sed command to ! process installed program names with. Using it you can, for instance, ! have all the new GCC programs installed as "new-gcc" and the like. You ! will still have to specify different --prefix options for new GCC and ! old GCC, because it is only the executable program names that are ! transformed. The difference is that you (as administrator) do not have ! to set up symlinks, but must specify additional directories in your (as ! a user) PATH. A complication with --program-transform-name is that the ! sed command invariably contains characters significant to the shell, ! and these have to be escaped correctly, also it is not possible to use ! "^" or "$" in the command. Here is the option to prefix "new-" to the ! new GCC installed programs: --program-transform-name='s,\\\\(.*\\\\),new-\\\\1,' ! With the above --prefix option, that will install the new GCC programs ! into /usr/local/gcc/bin with names prefixed by "new-". You can use ! --program-transform-name if you have multiple versions of GCC, and wish ! to be sure about which version you are invoking. ! If you use --prefix, GCC may have difficulty locating a GNU assembler ! or linker on your system, [30]GCC can not find GNU as/GNU ld explains ! how to deal with this. ! Another option that may be easier is to use the --program-prefix= or ! --program-suffix= options to configure. So if you're installing GCC ! 2.95.2 and don't want to disturb the current version of GCC in ! /usr/local/bin/, you could do configure --program-suffix=-2.95.2 This should result in GCC being installed as /usr/local/bin/gcc-2.95.2 instead of /usr/local/bin/gcc. ! __________________________________________________________________ Dynamic linker is unable to find GCC libraries ! This problem manifests itself by programs not finding shared libraries ! they depend on when the programs are started. Note this problem often ! manifests itself with failures in the libio/libstdc++ tests after ! configuring with --enable-shared and building GCC. ! GCC does not specify a runpath so that the dynamic linker can find ! dynamic libraries at runtime. ! The short explanation is that if you always pass a -R option to the ! linker, then your programs become dependent on directories which may be ! NFS mounted, and programs may hang unnecessarily when an NFS server ! goes down. ! The problem is not programs that do require the directories; those ! programs are going to hang no matter what you do. The problem is ! programs that do not require the directories. ! SunOS effectively always passed a -R option for every -L option; this ! was a bad idea, and so it was removed for Solaris. We should not ! recreate it. ! However, if you feel you really need such an option to be passed ! automatically to the linker, you may add it to the GCC specs file. This ! file can be found in the same directory that contains cc1 (run gcc ! -print-prog-name=cc1 to find it). You may add linker flags such as -R ! or -rpath, depending on platform and linker, to the *link or *lib ! specs. ! Another alternative is to install a wrapper script around gcc, g++ or ! ld that adds the appropriate directory to the environment variable ! LD_RUN_PATH or equivalent (again, it's platform-dependent). ! Yet another option, that works on a few platforms, is to hard-code the ! full pathname of the library into its soname. This can only be ! accomplished by modifying the appropriate .ml file within ! libstdc++/config (and also libg++/config, if you are building libg++), ! so that $(libdir)/ appears just before the library name in -soname or ! -h options. ! __________________________________________________________________ GCC can not find GNU as/GNU ld ! GCC searches the PATH for an assembler and a loader, but it only does ! so after searching a directory list hard-coded in the GCC executables. ! Since, on most platforms, the hard-coded list includes directories in ! which the system assembler and loader can be found, you may have to ! take one of the following actions to arrange that GCC uses the GNU ! versions of those programs. To ensure that GCC finds the GNU assembler (the GNU loader), which are ! required by [31]some configurations, you should configure these with ! the same --prefix option as you used for GCC. Then build & install GNU ! as (GNU ld) and proceed with building GCC. ! Another alternative is to create links to GNU as and ld in any of the ! directories printed by the command `gcc -print-search-dirs | grep ! '^programs:''. The link to `ld' should be named `real-ld' if `ld' ! already exists. If such links do not exist while you're compiling GCC, ! you may have to create them in the build directories too, within the ! gcc directory and in all the gcc/stage* subdirectories. ! GCC 2.95 allows you to specify the full pathname of the assembler and ! the linker to use. The configure flags are `--with-as=/path/to/as' and ! `--with-ld=/path/to/ld'. GCC will try to use these pathnames before ! looking for `as' or `(real-)ld' in the standard search dirs. If, at ! configure-time, the specified programs are found to be GNU utilities, ! `--with-gnu-as' and `--with-gnu-ld' need not be used; these flags will ! be auto-detected. One drawback of this option is that it won't allow ! you to override the search path for assembler and linker with ! command-line options -B/path/ if the specified filenames exist. ! __________________________________________________________________ cpp: Usage:... Error ! If you get an error like this when building GCC (particularly when ! building __mulsi3), then you likely have a problem with your ! environment variables. cpp: Usage: /usr/lib/gcc-lib/i586-unknown-linux-gnulibc1/2.7.2.3/cpp [switches] input output ! First look for an explicit '.' in either LIBRARY_PATH or ! GCC_EXEC_PREFIX from your environment. If you do not find an explicit ! '.', look for an empty pathname in those variables. Note that ':' at ! either the start or end of these variables is an implicit '.' and will ! cause problems. Also note '::' in these paths will also cause similar problems. ! __________________________________________________________________ Optimizing the compiler itself ! If you want to test a particular optimization option, it's useful to ! try bootstrapping the compiler with that option turned on. For example, ! to test the -fssa option, you could bootstrap like this: make BOOT_CFLAGS="-O2 -fssa" bootstrap ! __________________________________________________________________ Why does libiconv get linked into jc1 on Solaris? ! The Java front end requires iconv. If the compiler used to bootstrap ! GCC finds libiconv (because the GNU version of libiconv has been ! installed in the same prefix as the bootstrap compiler), but the newly ! built GCC does not find the library (because it will be installed with ! a different prefix), then a link-time error will occur when building ! jc1. This problem does not show up so often on platforms that have ! libiconv in a default location (like /usr/lib) because then both ! compilers can find a library named libiconv, even though it is a ! different library. ! Using --disable-nls at configure-time does not prevent this problem ! because jc1 uses iconv even in that case. Solutions include temporarily ! removing the GNU libiconv, copying it to a default location such as ! /usr/lib/, and using --enable-languages at configure-time to disable ! Java. ! __________________________________________________________________ ! Testsuite problems How do I pass flags like -fnew-abi to the testsuite? ! If you invoke runtest directly, you can use the --tool_opts option, ! e.g: runtest --tool_opts "-fnew-abi -fno-honor-std" ! Or, if you use make check you can use the make variable RUNTESTFLAGS, ! e.g: make RUNTESTFLAGS="--tool_opts '-fnew-abi -fno-honor-std'" check-g++ ! __________________________________________________________________ How can I run the test suite with multiple options? ! If you invoke runtest directly, you can use the --target_board option, ! e.g: runtest --target_board "unix{-fPIC,-fpic,}" ! Or, if you use make check you can use the make variable RUNTESTFLAGS, ! e.g: make RUNTESTFLAGS="--target_board 'unix{-fPIC,-fpic,}'" check-gcc ! Either of these examples will run the tests three times. Once with ! -fPIC, once with -fpic, and once with no additional flags. This technique is particularly useful on multilibbed targets. ! __________________________________________________________________ Miscellaneous Friend Templates In order to make a specialization of a template function a friend of a ! (possibly template) class, you must explicitly state that the friend ! function is a template, by appending angle brackets to its name, and ! this template function must have been declared already. Here's an ! example: template class foo { friend void bar(foo); } ! The above declaration declares a non-template function named bar, so it ! must be explicitly defined for each specialization of foo. A template ! definition of bar won't do, because it is unrelated with the ! non-template declaration above. So you'd have to end up writing: void bar(foo) { /* ... */ } void bar(foo) { /* ... */ } ! If you meant bar to be a template function, you should have ! forward-declared it as follows. Note that, since the template function ! declaration refers to the template class, the template class must be ! forward-declared too: template class foo; *************** class foo { *** 297,428 **** template void bar(foo) { /* ... */ } ! In this case, the template argument list could be left empty, because it can ! be implicitly deduced from the function arguments, but the angle brackets ! must be present, otherwise the declaration will be taken as a non-template ! function. Furthermore, in some cases, you may have to explicitly specify the ! template arguments, to remove ambiguity. ! An error in the last public comment draft of the ANSI/ISO C++ Standard and ! the fact that previous releases of GCC would accept such friend declarations ! as template declarations has led people to believe that the forward ! declaration was not necessary, but, according to the final version of the ! Standard, it is. ! _________________________________________________________________ dynamic_cast, throw, typeid don't work with shared libraries ! The new C++ ABI in the GCC 3.0 series uses address comparisons, rather than ! string compares, to determine type equality. This leads to better ! performance. Like other objects that have to be present in the final ! executable, these std::type_info objects have what is called vague linkage ! because they are not tightly bound to any one particular translation unit ! (object file). The compiler has to emit them in any translation unit that ! requires their presence, and then rely on the linking and loading process to ! make sure that only one of them is active in the final executable. With ! static linking all of these symbols are resolved at link time, but with ! dynamic linking, further resolution occurs at load time. You have to ensure ! that objects within a shared library are resolved against objects in the ! executable and other shared libraries. ! * For a program which is linked against a shared library, no additional ! precautions are needed. ! * You cannot create a shared library with the "-Bsymbolic" option, as that ! prevents the resolution described above. ! * If you use dlopen to explicitly load code from a shared library, you ! must do several things. First, export global symbols from the executable ! by linking it with the "-E" flag (you will have to specify this as ! "-Wl,-E" if you are invoking the linker in the usual manner from the ! compiler driver, g++). You must also make the external symbols in the ! loaded library available for subsequent libraries by providing the ! RTLD_GLOBAL flag to dlopen. The symbol resolution can be immediate or ! lazy. Template instantiations are another, user visible, case of objects with ! vague linkage, which needs similar resolution. If you do not take the above ! precautions, you may discover that a template instantiation with the same ! argument list, but instantiated in multiple translation units, has several ! addresses, depending in which translation unit the address is taken. (This ! is not an exhaustive list of the kind of objects which have vague linkage ! and are expected to be resolved during linking & loading.) If you are worried about different objects with the same name colliding ! during the linking or loading process, then you should use namespaces to ! disambiguate them. Giving distinct objects with global linkage the same name ! is a violation of the One Definition Rule (ODR) [basic.def.odr]. For more details about the way that GCC implements these and other C++ ! features, please read the [32]ABI specification. Note the std::type_info ! objects which must be resolved all begin with "_ZTS". Refer to ld's ! documentation for a description of the "-E" & "-Bsymbolic" flags. ! _________________________________________________________________ Why do I need autoconf, bison, xgettext, automake, etc? ! If you're using diffs up dated from one snapshot to the next, or if you're ! using the SVN repository, you may need several additional programs to build ! GCC. ! These include, but are not necessarily limited to autoconf, automake, bison, ! and xgettext. ! This is necessary because neither diff nor cvs keep timestamps correct. This ! causes problems for generated files as "make" may think those generated ! files are out of date and try to regenerate them. ! An easy way to work around this problem is to use the gcc_update script in ! the contrib subdirectory of GCC, which handles this transparently without ! requiring installation of any additional tools. ! When building from diffs or SVN or if you modified some sources, you may ! also need to obtain development versions of some GNU tools, as the ! production versions do not necessarily handle all features needed to rebuild ! GCC. ! In general, the current versions of these tools from [33]ftp://ftp.gnu.org/gnu/ will work. At present, Autoconf 2.50 is not ! supported, and you will need to use Autoconf 2.13; work is in progress to ! fix this problem. Also look at [34]ftp://gcc.gnu.org/pub/gcc/infrastructure/ ! for any special versions of packages. ! _________________________________________________________________ Why can't I build a shared library? ! When building a shared library you may get an error message from the linker ! like `assert pure-text failed:' or `DP relative code in file'. ! This kind of error occurs when you've failed to provide proper flags to gcc ! when linking the shared library. ! You can get this error even if all the .o files for the shared library were ! compiled with the proper PIC option. When building a shared library, gcc ! will compile additional code to be included in the library. That additional ! code must also be compiled with the proper PIC option. ! Adding the proper PIC option (-fpic or -fPIC) to the link line which creates ! the shared library will fix this problem on targets that support PIC in this ! manner. For example: gcc -c -fPIC myfile.c gcc -shared -o libmyfile.so -fPIC myfile.o ! _________________________________________________________________ When building C++, the linker says my constructors, destructors or virtual tables are undefined, but I defined them ! The ISO C++ Standard specifies that all virtual methods of a class that are ! not pure-virtual must be defined, but does not require any diagnostic for ! violations of this rule [class.virtual]/8. Based on this assumption, GCC ! will only emit the implicitly defined constructors, the assignment operator, ! the destructor and the virtual table of a class in the translation unit that ! defines its first such non-inline method. Therefore, if you fail to define this particular method, the linker may ! complain about the lack of definitions for apparently unrelated symbols. ! Unfortunately, in order to improve this error message, it might be necessary ! to change the linker, and this can't always be done. ! The solution is to ensure that all virtual methods that are not pure are ! defined. Note that a destructor must be defined even if it is declared ! pure-virtual [class.dtor]/7. References --- 318,455 ---- template void bar(foo) { /* ... */ } ! In this case, the template argument list could be left empty, because ! it can be implicitly deduced from the function arguments, but the angle ! brackets must be present, otherwise the declaration will be taken as a ! non-template function. Furthermore, in some cases, you may have to ! explicitly specify the template arguments, to remove ambiguity. ! An error in the last public comment draft of the ANSI/ISO C++ Standard ! and the fact that previous releases of GCC would accept such friend ! declarations as template declarations has led people to believe that ! the forward declaration was not necessary, but, according to the final ! version of the Standard, it is. ! __________________________________________________________________ dynamic_cast, throw, typeid don't work with shared libraries ! The new C++ ABI in the GCC 3.0 series uses address comparisons, rather ! than string compares, to determine type equality. This leads to better ! performance. Like other objects that have to be present in the final ! executable, these std::type_info objects have what is called vague ! linkage because they are not tightly bound to any one particular ! translation unit (object file). The compiler has to emit them in any ! translation unit that requires their presence, and then rely on the ! linking and loading process to make sure that only one of them is ! active in the final executable. With static linking all of these ! symbols are resolved at link time, but with dynamic linking, further ! resolution occurs at load time. You have to ensure that objects within ! a shared library are resolved against objects in the executable and ! other shared libraries. ! * For a program which is linked against a shared library, no ! additional precautions are needed. ! * You cannot create a shared library with the "-Bsymbolic" option, as ! that prevents the resolution described above. ! * If you use dlopen to explicitly load code from a shared library, ! you must do several things. First, export global symbols from the ! executable by linking it with the "-E" flag (you will have to ! specify this as "-Wl,-E" if you are invoking the linker in the ! usual manner from the compiler driver, g++). You must also make the ! external symbols in the loaded library available for subsequent ! libraries by providing the RTLD_GLOBAL flag to dlopen. The symbol ! resolution can be immediate or lazy. Template instantiations are another, user visible, case of objects with ! vague linkage, which needs similar resolution. If you do not take the ! above precautions, you may discover that a template instantiation with ! the same argument list, but instantiated in multiple translation units, ! has several addresses, depending in which translation unit the address ! is taken. (This is not an exhaustive list of the kind of objects which ! have vague linkage and are expected to be resolved during linking & ! loading.) If you are worried about different objects with the same name colliding ! during the linking or loading process, then you should use namespaces ! to disambiguate them. Giving distinct objects with global linkage the ! same name is a violation of the One Definition Rule (ODR) ! [basic.def.odr]. For more details about the way that GCC implements these and other C++ ! features, please read the [32]ABI specification. Note the ! std::type_info objects which must be resolved all begin with "_ZTS". ! Refer to ld's documentation for a description of the "-E" & ! "-Bsymbolic" flags. ! __________________________________________________________________ Why do I need autoconf, bison, xgettext, automake, etc? ! If you're using diffs up dated from one snapshot to the next, or if ! you're using the SVN repository, you may need several additional ! programs to build GCC. ! These include, but are not necessarily limited to autoconf, automake, ! bison, and xgettext. ! This is necessary because neither diff nor cvs keep timestamps correct. ! This causes problems for generated files as "make" may think those ! generated files are out of date and try to regenerate them. ! An easy way to work around this problem is to use the gcc_update script ! in the contrib subdirectory of GCC, which handles this transparently ! without requiring installation of any additional tools. ! When building from diffs or SVN or if you modified some sources, you ! may also need to obtain development versions of some GNU tools, as the ! production versions do not necessarily handle all features needed to ! rebuild GCC. ! In general, the current versions of these tools from [33]ftp://ftp.gnu.org/gnu/ will work. At present, Autoconf 2.50 is not ! supported, and you will need to use Autoconf 2.13; work is in progress ! to fix this problem. Also look at ! [34]ftp://gcc.gnu.org/pub/gcc/infrastructure/ for any special versions ! of packages. ! __________________________________________________________________ Why can't I build a shared library? ! When building a shared library you may get an error message from the ! linker like `assert pure-text failed:' or `DP relative code in file'. ! This kind of error occurs when you've failed to provide proper flags to ! gcc when linking the shared library. ! You can get this error even if all the .o files for the shared library ! were compiled with the proper PIC option. When building a shared ! library, gcc will compile additional code to be included in the ! library. That additional code must also be compiled with the proper PIC ! option. ! Adding the proper PIC option (-fpic or -fPIC) to the link line which ! creates the shared library will fix this problem on targets that ! support PIC in this manner. For example: gcc -c -fPIC myfile.c gcc -shared -o libmyfile.so -fPIC myfile.o ! __________________________________________________________________ When building C++, the linker says my constructors, destructors or virtual tables are undefined, but I defined them ! The ISO C++ Standard specifies that all virtual methods of a class that ! are not pure-virtual must be defined, but does not require any ! diagnostic for violations of this rule [class.virtual]/8. Based on this ! assumption, GCC will only emit the implicitly defined constructors, the ! assignment operator, the destructor and the virtual table of a class in ! the translation unit that defines its first such non-inline method. Therefore, if you fail to define this particular method, the linker may ! complain about the lack of definitions for apparently unrelated ! symbols. Unfortunately, in order to improve this error message, it ! might be necessary to change the linker, and this can't always be done. ! The solution is to ensure that all virtual methods that are not pure ! are defined. Note that a destructor must be defined even if it is ! declared pure-virtual [class.dtor]/7. References diff -Nrcpad gcc-4.2.2/INSTALL/binaries.html gcc-4.2.3/INSTALL/binaries.html *** gcc-4.2.2/INSTALL/binaries.html Thu Jan 1 00:00:00 1970 --- gcc-4.2.3/INSTALL/binaries.html Fri Feb 1 17:06:59 2008 *************** *** 0 **** --- 1,120 ---- + + + Installing GCC: Binaries + + + + + + + + + + +

Installing GCC: Binaries

+ + 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. + +

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. + +

+ +

In addition to those specific offerings, you can get a binary + distribution CD-ROM from the + Free Software Foundation. + 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. + +

+

Return to the GCC Installation page + + + + + + + + diff -Nrcpad gcc-4.2.2/INSTALL/build.html gcc-4.2.3/INSTALL/build.html *** gcc-4.2.2/INSTALL/build.html Thu Jan 1 00:00:00 1970 --- gcc-4.2.3/INSTALL/build.html Fri Feb 1 17:06:58 2008 *************** *** 0 **** --- 1,293 ---- + + + Installing GCC: Building + + + + + + + + + + +

Installing GCC: Building

+ + Now that GCC is configured, you are ready to build the compiler and + runtime libraries. + +

Some commands executed when making the compiler may fail (return a + nonzero status) and be ignored by make. These failures, which + are often due to files that were not found, are expected, and can safely + be ignored. + +

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 + --disable-werror. + +

On certain old systems, defining certain environment variables such as + CC can interfere with the functioning of make. + +

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. + +

If you build GCC on a BSD system using a directory stored in an old System + V file system, problems may occur in running fixincludes if the + System V file system doesn't support symbolic links. These problems + result in a failure to fix the declaration of size_t in + sys/types.h. If you find that size_t is a signed type and + that type mismatches occur, this could be the cause. + +

The solution is not to use such a directory for building GCC. + +

When building from SVN or snapshots, or if you modify parser sources, + you need the Bison parser generator installed. If you do not modify + parser sources, releases contain the Bison-generated files and you do + not need Bison installed to build them. + +

When building from SVN or snapshots, or if you modify Texinfo + documentation, you need version 4.4 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. + +

0.1 Building a native compiler

+ +

For a native build, the default configuration is to perform + a 3-stage bootstrap of the compiler when `make' is invoked. + This will build the entire GCC system and ensure that it compiles + itself correctly. It can be disabled with the --disable-bootstrap + parameter to `configure', but bootstrapping is suggested because + the compiler will be tested more completely and could also have + better performance. + +

The bootstrapping process will complete the following steps: + +

    +
  • Build tools necessary to build the compiler. + +
  • 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. + +
  • Perform a comparison test of the stage2 and stage3 compilers. + +
  • Build runtime libraries using the stage3 compiler from the previous step. + +
+ +

If you are short on disk space you might consider `make + bootstrap-lean' 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. + +

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.) + + 

          make CFLAGS='-O' LIBCFLAGS='-g -O2' \
+             LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
+
+

If you wish to use non-default GCC flags when compiling the stage2 and + stage3 compilers, set BOOT_CFLAGS on the command line when doing + `make'. Non-default optimization flags are less well + tested here than the default of `-g -O2', but should still work. + In a few cases, you may find that you need to specify special flags such + as -msoft-float here to complete the bootstrap; or, if the + native compiler miscompiles the stage1 compiler, you may need to work + around this, by choosing BOOT_CFLAGS to avoid the parts of the + stage1 compiler that were miscompiled, or by using `make + bootstrap4' to increase the number of stages of bootstrap. + +

Note that using non-standard CFLAGS can cause bootstrap to fail + if these trigger a warning with the new compiler. For example using + `-O2 -g -mcpu=i686' on i686-pc-linux-gnu will cause bootstrap + failure as -mcpu= is deprecated in 3.4.0 and above. + +

If you used the flag --enable-languages=... 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 LANGUAGES when calling `make' + does not work anymore! + +

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 “different”. If you encounter this problem, you will + need to disable comparison in the Makefile.) + +

If you do not want to bootstrap your compiler, you can configure with + --disable-bootstrap. 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 + powerpc-unknown-linux-gnu toolchain on a + powerpc64-unknown-linux-gnu host. In this case, pass + --enable-bootstrap to the configure script. + +

0.2 Building a cross compiler

+ +

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. + +

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. + +

Assuming you have already installed a native copy of GCC and configured + your cross compiler, issue the command make, which performs the + following steps: + +

    +
  • Build host tools necessary to build the compiler. + +
  • 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. + +
  • Build the compiler (single stage only). + +
  • Build runtime libraries using the compiler from the previous step. +
+ +

Note that if an error occurs in any step the make process will exit. + +

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 + prefix/target/bin. Here is a table of the tools + you should put in this directory: + +

+
as
This should be the cross-assembler. + +
ld
This should be the cross-linker. + +
ar
This should be the cross-archiver: a program which can manipulate + archive files (linker libraries) in the target machine's format. + +
ranlib
This should be a program to construct a symbol table in an archive file. +
+ +

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. + +

The easiest way to provide these files is to build the Binutils package. + Configure it with the same --host and --target + 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. + +

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 + --with-sysroot or --with-headers and + --with-libs. Many targets also require “start files” such + as crt0.o and + crtn.o which are linked into each executable. There may be several + alternatives for crt0.o, for use with profiling or other + compilation options. Check your target's definition of + STARTFILE_SPEC to find out what start files it uses. + +

0.3 Building in parallel

+ +

GNU Make 3.79 and above, which is necessary to build GCC, support + building in parallel. To activate this, you can use `make -j 2' + instead of `make'. 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. + +

0.4 Building the Ada compiler

+ +

In order to build GNAT, the Ada compiler, you need a working GNAT + compiler (GNAT version 3.14 or later, or GCC version 3.1 or later). + This includes GNAT tools such as gnatmake and + gnatlink, since the Ada front end is written in Ada and + uses some GNAT-specific extensions. + +

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. + +

configure 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 --enable-languages is + used to disable building the Ada front end. + +

0.5 Building with profile feedback

+ +

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 make profiledbootstrap. + +

When `make profiledbootstrap' is run, it will first build a stage1 + compiler. This compiler is used to build a stageprofile compiler + instrumented to collect execution counts of instruction and branch + probabilities. Then runtime libraries are compiled with profile collected. + Finally a stagefeedback compiler is built using the information collected. + +

Unlike standard bootstrap, several additional restrictions apply. The + compiler used to build stage1 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. + +

+

Return to the GCC Installation page + + + + + + + + + + + diff -Nrcpad gcc-4.2.2/INSTALL/configure.html gcc-4.2.3/INSTALL/configure.html *** gcc-4.2.2/INSTALL/configure.html Thu Jan 1 00:00:00 1970 --- gcc-4.2.3/INSTALL/configure.html Fri Feb 1 17:06:58 2008 *************** *** 0 **** --- 1,919 ---- + + + Installing GCC: Configuration + + + + + + + + + + +

Installing GCC: Configuration

+ + 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. + +

We use srcdir to refer to the toplevel source directory for + GCC; we use objdir to refer to the toplevel build/object directory. + +

If you obtained the sources via SVN, srcdir must refer to the top + gcc directory, the one where the MAINTAINERS can be found, + and not its gcc subdirectory, otherwise the build will fail. + +

If either srcdir or objdir is located on an automounted NFS + file system, the shell's built-in pwd command will return + temporary pathnames. Using these can lead to various sorts of build + problems. To avoid this issue, set the PWDCMD environment + variable to an automounter-aware pwd command, e.g., + pawd or `amq -w', during the configuration and build + phases. + +

First, we highly recommend that GCC be built into a + separate directory than the sources which does not reside + within the source tree. This is how we generally build GCC; building + where srcdir == objdir should still work, but doesn't + get extensive testing; building where objdir is a subdirectory + of srcdir is unsupported. + +

If you have previously built GCC in the same directory for a + different target machine, do `make distclean' to delete all files + that might be invalid. One of the files this deletes is Makefile; + if `make distclean' complains that Makefile does not exist + or issues a message like “don't know how to make distclean” it probably + means that the directory is already suitably clean. However, with the + recommended method of building in a separate objdir, you should + simply use a different objdir for each target. + +

Second, when configuring a native system, either cc or + gcc must be in your path or you must set CC in + your environment before running configure. Otherwise the configuration + scripts may fail. + +

To configure GCC: + + 

        % mkdir objdir
+         % cd objdir
+         % srcdir/configure [options] [target]
+
+

Target specification

+ +
    +
  • GCC has code to correctly determine the correct value for target + for nearly all native systems. Therefore, we highly recommend you not + provide a configure target when configuring a native compiler. + +
  • target must be specified as --target=target + when configuring a cross compiler; examples of valid targets would be + m68k-coff, sh-elf, etc. + +
  • Specifying just target instead of --target=target + implies that the host defaults to target. +
+ +

Options specification

+ +

Use options to override several configure time options for + GCC. A list of supported options follows; `configure + --help' may list other options, but those not listed below may not + work and should not normally be used. + +

Note that each --enable option has a corresponding + --disable option and that each --with option has a + corresponding --without option. + +

+
--prefix=dirname
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 + /usr/local. + +

We highly recommend against dirname being the same or a + subdirectory of objdir or vice versa. If specifying a directory + beneath a user's home directory tree, some shells will not expand + dirname correctly if it contains the `~' metacharacter; use + $HOME instead. + +

The following standard autoconf options are supported. Normally you + should not need to use these options. +

+
--exec-prefix=dirname
Specify the toplevel installation directory for architecture-dependent + files. The default is prefix. + +
--bindir=dirname
Specify the installation directory for the executables called by users + (such as gcc and g++). The default is + exec-prefix/bin. + +
--libdir=dirname
Specify the installation directory for object code libraries and + internal data files of GCC. The default is exec-prefix/lib. + +
--libexecdir=dirname
Specify the installation directory for internal executables of GCC. + The default is exec-prefix/libexec. + +
--with-slibdir=dirname
Specify the installation directory for the shared libgcc library. The + default is libdir. + +
--infodir=dirname
Specify the installation directory for documentation in info format. + The default is prefix/info. + +
--datadir=dirname
Specify the installation directory for some architecture-independent + data files referenced by GCC. The default is prefix/share. + +
--mandir=dirname
Specify the installation directory for manual pages. The default is + prefix/man. (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.) + +
--with-gxx-include-dir=dirname
Specify + the installation directory for G++ header files. The default is + prefix/include/c++/version. + +
+ +
--program-prefix=prefix
GCC supports some transformations of the names of its programs when + installing them. This option prepends prefix to the names of + programs to install in bindir (see above). For example, specifying + --program-prefix=foo- would result in `gcc' + being installed as /usr/local/bin/foo-gcc. + +
--program-suffix=suffix
Appends suffix to the names of programs to install in bindir + (see above). For example, specifying --program-suffix=-3.1 + would result in `gcc' being installed as + /usr/local/bin/gcc-3.1. + +
--program-transform-name=pattern
Applies the `sed' script pattern to be applied to the names + of programs to install in bindir (see above). pattern has to + consist of one or more basic `sed' editing commands, separated by + semicolons. For example, if you want the `gcc' program name to be + transformed to the installed program /usr/local/bin/myowngcc and + the `g++' program name to be transformed to + /usr/local/bin/gspecial++ without changing other program names, + you could use the pattern + --program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/' + to achieve this effect. + +

All three options can be combined and used together, resulting in more + complex conversion patterns. As a basic rule, prefix (and + suffix) are prepended (appended) before further transformations + can happen with a special transformation script pattern. + +

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. + +

For native builds, some of the installed programs are also installed + with the target alias in front of their name, as in + `i686-pc-linux-gnu-gcc'. All of the above transformations happen + before the target alias is prepended to the name—so, specifying + --program-prefix=foo- and program-suffix=-3.1, the + resulting binary would be installed as + /usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1. + +

As a last shortcoming, none of the installed Ada programs are + transformed yet, which will be fixed in some time. + +

--with-local-prefix=dirname
Specify the + installation directory for local include files. The default is + /usr/local. Specify this option if you want the compiler to + search directory dirname/include for locally installed + header files instead of /usr/local/include. + +

You should specify --with-local-prefix only if your + site has a different convention (not /usr/local) for where to put + site-specific files. + +

The default value for --with-local-prefix is /usr/local + regardless of the value of --prefix. Specifying + --prefix has no effect on which directory GCC searches for + local header files. This may seem counterintuitive, but actually it is + logical. + +

The purpose of --prefix is to specify where to install + GCC. The local header files in /usr/local/include—if you put + any in that directory—are not part of GCC. They are part of other + programs—perhaps many others. (GCC installs its own header files in + another directory which is based on the --prefix value.) + +

Both the local-prefix include directory and the GCC-prefix include + directory are part of GCC's “system include” 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. + +

Some autoconf macros add -I directory options to the + compiler command line, to ensure that directories containing installed + packages' headers are searched. When directory 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. + +

GCC automatically searches for ordinary libraries using + GCC_EXEC_PREFIX. 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 /usr. + +

Sites that need to install multiple versions of GCC may not want to + use the above simple configuration. It is possible to use the + --program-prefix, --program-suffix and + --program-transform-name options to install multiple versions + into a single directory, but it may be simpler to use different prefixes + and the --with-local-prefix 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 LIBRARY_PATH). + +

The same value can be used for both --with-local-prefix and + --prefix provided it is not /usr. This can be used + to avoid the default search of /usr/local/include. + +

Do not specify /usr as the --with-local-prefix! + The directory you use for --with-local-prefix must not + 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 fixincludes script. + +

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. + +

--enable-shared[=package[,...]]
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. + +

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 + `libgcc' (also known as `gcc'), `libstdc++' (not + `libstdc++-v3'), `libffi', `zlib', `boehm-gc', + `ada', `libada', `libjava' and `libobjc'. + Note `libiberty' does not support shared libraries at all. + +

Use --disable-shared to build only static libraries. Note that + --disable-shared does not accept a list of package names as + argument, only --enable-shared does. + +

--with-gnu-as
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 --with-gnu-as.) If you have more than one + assembler installed on your system, you may want to use this option in + connection with --with-as=pathname or + --with-build-time-tools=pathname. + +

The following systems are the only ones where it makes a difference + whether you use the GNU assembler. On any other system, + --with-gnu-as has no effect. + +

    +
  • `hppa1.0-any-any' +
  • `hppa1.1-any-any' +
  • `i386-any-sysv' +
  • `m68k-bull-sysv' +
  • `m68k-hp-hpux' +
  • `m68000-hp-hpux' +
  • `m68000-att-sysv' +
  • `sparc-sun-solaris2.any' +
  • `sparc64-any-solaris2.any' +
+ +

On the systems listed above (except for the HP-PA, the SPARC, for ISC on + the 386, if you use the GNU assembler, you should also use the GNU linker + (and specify --with-gnu-ld). + +

--with-as=pathname
Specify that the compiler should use the assembler pointed to by + pathname, rather than the one found by the standard rules to find + an assembler, which are: +
    +
  • Unless GCC is being built with a cross compiler, check the + libexec/gcc/target/version directory. + libexec defaults to exec-prefix/libexec; + exec-prefix defaults to prefix, which + defaults to /usr/local unless overridden by the + --prefix=pathname switch described above. target + is the target system triple, such as `sparc-sun-solaris2.7', and + version denotes the GCC version, such as 3.0. + +
  • If the target system is the same that you are building on, check + operating system specific directories (e.g. /usr/ccs/bin on + Sun Solaris 2). + +
  • Check in the PATH for a tool whose name is prefixed by the + target system triple. + +
  • Check in the PATH 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). +
+ +

You may want to use --with-as 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. + +

--with-gnu-ld
Same as --with-gnu-as + but for the linker. + +
--with-ld=pathname
Same as --with-as + but for the linker. + +
--with-stabs
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. + +

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. + +

Normally, GCC uses the ECOFF debugging format by default; if you + prefer BSD stabs, specify --with-stabs when you configure GCC. + +

No matter which default you choose when you configure GCC, the user + can use the -gcoff and -gstabs+ options to specify explicitly + the debug format for a particular compilation. + +

--with-stabs is meaningful on the ISC system on the 386, also, if + --with-gas 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. + +

--with-stabs 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. + +

--disable-multilib
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. + +

Some targets provide finer-grained control over which multilibs are built + (e.g., --disable-softfloat): +

+
arc-*-elf*
biendian. + +
arm-*-*
fpu, 26bit, underscore, interwork, biendian, nofmult. + +
m68*-*-*
softfloat, m68881, m68000, m68020. + +
mips*-*-*
single-float, biendian, softfloat. + +
powerpc*-*-*, rs6000*-*-*
aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian, + sysv, aix. + +
+ +
--enable-threads
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. + +

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, --enable-threads is an + alias for --enable-threads=single. + +

--disable-threads
Specify that threading support should be disabled for the system. + This is an alias for --enable-threads=single. + +
--enable-threads=lib
Specify that + lib 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 lib are: + +
+
aix
AIX thread support. +
dce
DCE thread support. +
gnat
Ada tasking support. For non-Ada programs, this setting is equivalent + to `single'. 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. +
mach
Generic MACH thread support, known to work on NeXTSTEP. (Please note + that the file needed to support this configuration, gthr-mach.h, is + missing and thus this setting will cause a known bootstrap failure.) +
no
This is an alias for `single'. +
posix
Generic POSIX/Unix98 thread support. +
posix95
Generic POSIX/Unix95 thread support. +
rtems
RTEMS thread support. +
single
Disable thread support, should work for all platforms. +
solaris
Sun Solaris 2 thread support. +
vxworks
VxWorks thread support. +
win32
Microsoft Win32 API thread support. +
nks
Novell Kernel Services thread support. +
+ +
--enable-tls
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 + --enable-tls or --disable-tls. 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. + +
--disable-tls
Specify that the target does not support TLS. + This is an alias for --enable-tls=no. + +
--with-cpu=cpu
Specify which cpu variant the compiler should generate code for by default. + cpu will be used as the default value of the -mcpu= switch. + This option is only supported on some targets, including ARM, i386, PowerPC, + and SPARC. + +
--with-schedule=cpu
--with-arch=cpu
--with-tune=cpu
--with-abi=abi
--with-fpu=type
--with-float=type
These configure options provide default values for the -mschedule=, + -march=, -mtune=, -mabi=, and -mfpu= + options and for -mhard-float or -msoft-float. As with + --with-cpu, which switches will be accepted and acceptable values + of the arguments depend on the target. + +
--with-mode=mode
Specify if the compiler should default to -marm or -mthumb. + This option is only supported on ARM targets. + +
--with-divide=type
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 type are: +
+
traps
Division by zero checks use conditional traps (this is the default on + systems that support conditional traps). +
breaks
Division by zero checks use the break instruction. +
+ +
--enable-__cxa_atexit
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 + -fuse-cxa-exit to be passed by default. + +
--enable-target-optspace
Specify that target + libraries should be optimized for code space instead of code speed. + This is the default for the m32r platform. + +
--disable-cpp
Specify that a user visible cpp program should not be installed. + +
--with-cpp-install-dir=dirname
Specify that the user visible cpp program should be installed + in prefix/dirname/cpp, in addition to bindir. + +
--enable-initfini-array
Force the use of sections .init_array and .fini_array + (instead of .init and .fini) for constructors and + destructors. Option --disable-initfini-array has the + opposite effect. If neither option is specified, the configure script + will try to guess whether the .init_array and + .fini_array sections are supported and, if they are, use them. + +
--enable-maintainer-mode
The build rules that + regenerate the GCC master message catalog gcc.pot 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 --enable-maintainer-mode will enable + this. Note that you need a recent version of the gettext tools + to do so. + +
--disable-bootstrap
For a native build, the default configuration is to perform + a 3-stage bootstrap of the compiler when `make' is invoked, + testing that GCC can compile itself correctly. If you want to disable + this process, you can configure with --disable-bootstrap. + +
--enable-bootstrap
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 --enable-bootstrap. + +
--enable-generated-files-in-srcdir
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. + +

If you configure with --enable-generated-files-in-srcdir 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. + +

--enable-version-specific-runtime-libs
Specify + that runtime libraries should be installed in the compiler specific + subdirectory (libdir/gcc) rather than the usual places. In + addition, `libstdc++''s include files will be installed into + libdir unless you overruled it by using + --with-gxx-include-dir=dirname. Using this option is + particularly useful if you intend to use several versions of GCC in + parallel. This is currently supported by `libgfortran', + `libjava', `libmudflap', `libstdc++', and `libobjc'. + +
--with-java-home=dirname
This `libjava' option overrides the default value of the + `java.home' system property. It is also used to set + `sun.boot.class.path' to dirname/lib/rt.jar. By + default `java.home' is set to prefix and + `sun.boot.class.path' to + datadir/java/libgcj-version.jar. + +
--enable-languages=lang1,lang2,...
Specify that only a particular subset of compilers and + their runtime libraries should be built. For a list of valid values for + langN you can issue the following command in the + gcc directory of your GCC source tree:
+ 
          grep language= */config-lang.in
+
+

Currently, you can use any of the following: + all, ada, c, c++, fortran, java, + objc, obj-c++, treelang. + Building the Ada compiler has special requirements, see below. + If you do not pass this flag, or specify the option all, then all + default languages available in the gcc sub-tree will be configured. + Ada, Objective-C++, and treelang are not default languages; the rest are. + Re-defining LANGUAGES when calling `make' does not + work anymore, as those language sub-directories might not have been + configured! + +

--disable-libada
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 `make -C gcc gnatlib_and_tools'. + +
--disable-libssp
Specify that the run-time libraries for stack smashing protection + should not be built. + +
--disable-libgomp
Specify that the run-time libraries used by GOMP should not be built. + +
--with-dwarf2
Specify that the compiler should + use DWARF 2 debugging information as the default. + +
--enable-targets=all
--enable-targets=target_list
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 powerpc-linux. + +
--enable-secureplt
This option enables -msecure-plt by default for powerpc-linux. + See “RS/6000 and PowerPC Options” in the main manual + +
--enable-win32-registry
--enable-win32-registry=key
--disable-win32-registry
The --enable-win32-registry option enables Microsoft Windows-hosted GCC + to look up installations paths in the registry using the following key: + + 
          HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\key
+
+

key defaults to GCC version number, and can be overridden by the + --enable-win32-registry=key 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 --disable-win32-registry + option. This option has no effect on the other hosts. + +

--nfp
Specify that the machine does not have a floating point unit. This + option only applies to `m68k-sun-sunosn'. On any other + system, --nfp has no effect. + +
--enable-werror
--disable-werror
--enable-werror=yes
--enable-werror=no
When you specify this option, it controls whether certain files in the + compiler are built with -Werror in bootstrap stage2 and later. + If you don't specify it, -Werror is turned on for the main + development trunk. However it defaults to off for release branches and + final releases. The specific files which get -Werror are + controlled by the Makefiles. + +
--enable-checking
--enable-checking=list
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 `yes' by default when building + from SVN or snapshots, but `release' for releases. More control + over the checks may be had by specifying list. The categories of + checks available are `yes' (most common checks + `assert,misc,tree,gc,rtlflag,runtime'), `no' (no checks at + all), `all' (all but `valgrind'), `release' (cheapest + checks `assert,runtime') or `none' (same as `no'). + Individual checks can be enabled with these flags `assert', + `fold', `gc', `gcac' `misc', `rtl', + `rtlflag', `runtime', `tree', and `valgrind'. + +

The `valgrind' check requires the external valgrind + simulator, available from http://valgrind.org/. The + `rtl', `gcac' and `valgrind' checks are very expensive. + To disable all checking, `--disable-checking' or + `--enable-checking=none' 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. + +

--enable-coverage
--enable-coverage=level
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 + level argument controls whether the compiler is built optimized or + not, values are `opt' and `noopt'. 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. + +
--enable-gather-detailed-mem-stats
When this option is specified more detailed information on memory + allocation is gathered. This information is printed when using + -fmem-report. + +
--with-gc
--with-gc=choice
With this option you can specify the garbage collector implementation + used during the compilation process. choice can be one of + `page' and `zone', where `page' is the default. + +
--enable-nls
--disable-nls
The --enable-nls 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 --disable-nls option disables NLS. + +
--with-included-gettext
If NLS is enabled, the --with-included-gettext option causes the build + procedure to prefer its copy of GNU gettext. + +
--with-catgets
If NLS is enabled, and if the host lacks gettext but has the + inferior catgets interface, the GCC build procedure normally + ignores catgets and instead uses GCC's copy of the GNU + gettext library. The --with-catgets option causes the + build procedure to use the host's catgets in this situation. + +
--with-libiconv-prefix=dir
Search for libiconv header files in dir/include and + libiconv library files in dir/lib. + +
--enable-obsolete
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. + +

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. + +

--enable-decimal-float
--disable-decimal-float
Enable (or disable) support for the C decimal floating point + extension. This is enabled by default only on PowerPC GNU/Linux + systems. Other systems may also support it, but require the user to + specifically enable it. + +
--with-long-double-128
Specify if long double type should be 128-bit by default on selected + GNU/Linux architectures. If using --without-long-double-128, + long double will be by default 64-bit, the same as double type. + When neither of these configure options are used, the default will be + 128-bit long double when built against GNU C Library 2.4 and later, + 64-bit long double otherwise. + +
+ +

Cross-Compiler-Specific Options

+ +

The following options only apply to building cross compilers. +

+
--with-sysroot
--with-sysroot=dir
Tells GCC to consider dir 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 --with-headers and + --with-libs that this option obsoletes. The default value, + in case --with-sysroot is not given an argument, is + ${gcc_tooldir}/sys-root. If the specified directory is a + subdirectory of ${exec_prefix}, then it will be found relative to + the GCC binaries if the installation tree is moved. + +
--with-build-sysroot
--with-build-sysroot=dir
Tells GCC to consider dir as the system root (see + --with-sysroot) while building target libraries, instead of + the directory specified with --with-sysroot. This option is + only useful when you are already using --with-sysroot. You + can use --with-build-sysroot when you are configuring with + --prefix set to a directory that is different from the one in + which you are installing GCC and your target libraries. + +

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. + +

--with-headers
--with-headers=dir
Deprecated in favor of --with-sysroot. + Specifies that target headers are available when building a cross compiler. + The dir argument specifies a directory which has the target include + files. These include files will be copied into the gcc install + directory. This option with the dir argument is required when + building a cross compiler, if prefix/target/sys-include + doesn't pre-exist. If prefix/target/sys-include does + pre-exist, the dir argument may be omitted. fixincludes + will be run on these files to make them compatible with GCC. + +
--without-headers
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. + +
--with-libs
--with-libs=``dir1 dir2 ... dirN''
Deprecated in favor of --with-sysroot. + Specifies a list of directories which contain the target runtime + libraries. These libraries will be copied into the gcc install + directory. If the directory list is omitted, this option has no + effect. + +
--with-newlib
Specifies that `newlib' is + being used as the target C library. This causes __eprintf to be + omitted from libgcc.a on the assumption that it will be provided by + `newlib'. + +
--with-build-time-tools=dir
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. + +

For example, on a ia64-hp-hpux system, you may have the GNU + assembler and linker in /usr/bin, and the native tools in a + different path, and build a toolchain that expects to find the + native tools in /usr/bin. + +

When you use this option, you should ensure that dir includes + ar, as, ld, nm, + ranlib and strip if necessary, and possibly + objdump. Otherwise, GCC may use an inconsistent set of + tools. +

+ +

Fortran-Specific Options

+ +

The following options apply to the build of the Fortran front end. + +

+
--with-gmp=pathname
--with-gmp-include=pathname
--with-gmp-lib=pathname
--with-mpfr=pathname
--with-mpfr-include=pathname
--with-mpfr-lib=pathname
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 + the Fortran front-end, you can explicitly specify the directory where + they are installed (`--with-gmp=gmpinstalldir', + `--with-mpfr=mpfrinstalldir'). The + --with-gmp=gmpinstalldir option is shorthand for + --with-gmp-lib=gmpinstalldir/lib and + --with-gmp-include=gmpinstalldir/include. Likewise the + --with-mpfr=mpfrinstalldir option is shorthand for + --with-mpfr-lib=mpfrinstalldir/lib and + --with-mpfr-include=mpfrinstalldir/include. If these + shorthand assumptions are not correct, you can use the explicit + include and lib options directly. + +
+ +

Java-Specific Options

+ +

The following option applies to the build of the Java front end. + +

+
--disable-libgcj
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 `libgcj' isn't built, you + may need to port it; in this case, before modifying the top-level + configure.in so that `libgcj' is enabled by default on this platform, + you may use --enable-libgcj to override the default. + +
+ +

The following options apply to building `libgcj'. + +

General Options
+ +
+
--disable-getenv-properties
Don't set system properties from GCJ_PROPERTIES. + +
--enable-hash-synchronization
Use a global hash table for monitor locks. Ordinarily, + `libgcj''s `configure' 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. + +
--enable-interpreter
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 --disable-interpreter). + +
--disable-java-net
Disable java.net. This disables the native part of java.net only, + using non-functional stubs for native method implementations. + +
--disable-jvmpi
Disable JVMPI support. + +
--with-ecos
Enable runtime eCos target support. + +
--without-libffi
Don't use `libffi'. This will disable the interpreter and JNI + support as well, as these require `libffi' to work. + +
--enable-libgcj-debug
Enable runtime debugging code. + +
--enable-libgcj-multifile
If specified, causes all .java source files to be + compiled into .class files in one invocation of + `gcj'. This can speed up build time, but is more + resource-intensive. If this option is unspecified or + disabled, `gcj' is invoked once for each .java + file to compile into a .class file. + +
--with-libiconv-prefix=DIR
Search for libiconv in DIR/include and DIR/lib. + +
--enable-sjlj-exceptions
Force use of the setjmp/longjmp-based scheme for exceptions. + `configure' ordinarily picks the correct value based on the platform. + Only use this option if you are sure you need a different setting. + +
--with-system-zlib
Use installed `zlib' rather than that included with GCC. + +
--with-win32-nlsapi=ansi, unicows or unicode
Indicates how MinGW `libgcj' translates between UNICODE + characters and the Win32 API. +
+
ansi
Use the single-byte char and the Win32 A functions natively, + translating to and from UNICODE when using these functions. If + unspecified, this is the default. + +
unicows
Use the WCHAR and Win32 W functions natively. Adds + -lunicows to libgcj.spec to link with `libunicows'. + unicows.dll needs to be deployed on Microsoft Windows 9X machines + running built executables. libunicows.a, an open-source + import library around Microsoft's unicows.dll, is obtained from + http://libunicows.sourceforge.net/, which also gives details + on getting unicows.dll from Microsoft. + +
unicode
Use the WCHAR and Win32 W functions natively. Does not + add -lunicows to libgcj.spec. The built executables will + only run on Microsoft Windows NT and above. +
+
+ +
AWT-Specific Options
+ +
+
--with-x
Use the X Window System. + +
--enable-java-awt=PEER(S)
Specifies the AWT peer library or libraries to build alongside + `libgcj'. If this option is unspecified or disabled, AWT + will be non-functional. Current valid values are gtk and + xlib. Multiple libraries should be separated by a + comma (i.e. --enable-java-awt=gtk,xlib). + +
--enable-gtk-cairo
Build the cairo Graphics2D implementation on GTK. + +
--enable-java-gc=TYPE
Choose garbage collector. Defaults to boehm if unspecified. + +
--disable-gtktest
Do not try to compile and run a test GTK+ program. + +
--disable-glibtest
Do not try to compile and run a test GLIB program. + +
--with-libart-prefix=PFX
Prefix where libart is installed (optional). + +
--with-libart-exec-prefix=PFX
Exec prefix where libart is installed (optional). + +
--disable-libarttest
Do not try to compile and run a test libart program. + +
+ +

+

Return to the GCC Installation page + + + + + + + + + + + + diff -Nrcpad gcc-4.2.2/INSTALL/download.html gcc-4.2.3/INSTALL/download.html *** gcc-4.2.2/INSTALL/download.html Thu Jan 1 00:00:00 1970 --- gcc-4.2.3/INSTALL/download.html Fri Feb 1 17:06:58 2008 *************** *** 0 **** --- 1,90 ---- + + + Downloading GCC + + + + + + + + + + +

Downloading GCC

+ + GCC is distributed via SVN and FTP + tarballs compressed with gzip or + bzip2. It is possible to download a full distribution or specific + components. + +

Please refer to the releases web page + for information on how to obtain GCC. + +

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. + +

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). + +

Unpack the core distribution as well as any language specific + distributions in the same directory. + +

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 + (bfd, binutils, gas, gprof, ld, + opcodes, ...) to the directory containing the GCC sources. + +

+

Return to the GCC Installation page + + + + + + + + + + + + + diff -Nrcpad gcc-4.2.2/INSTALL/finalinstall.html gcc-4.2.3/INSTALL/finalinstall.html *** gcc-4.2.2/INSTALL/finalinstall.html Thu Jan 1 00:00:00 1970 --- gcc-4.2.3/INSTALL/finalinstall.html Fri Feb 1 17:06:59 2008 *************** *** 0 **** --- 1,166 ---- + + + Installing GCC: Final installation + + + + + + + + + + +

Installing GCC: Final installation

+ Now that GCC has been built (and optionally tested), you can install it with + 
     cd objdir; make install
+
+

We strongly recommend to install into a target directory where there is + no previous version of GCC present. + +

That step completes the installation of GCC; user level binaries can + be found in prefix/bin where prefix is the value + you specified with the --prefix to configure (or + /usr/local by default). (If you specified --bindir, + that directory will be used instead; otherwise, if you specified + --exec-prefix, exec-prefix/bin will be used.) + Headers for the C++ and Java libraries are installed in + prefix/include; libraries in libdir + (normally prefix/lib); internal parts of the compiler in + libdir/gcc and libexecdir/gcc; documentation + in info format in infodir (normally + prefix/info). + +

When installing cross-compilers, GCC's executables + are not only installed into bindir, that + is, exec-prefix/bin, but additionally into + exec-prefix/target-alias/bin, if that directory + exists. Typically, such tooldirs hold target-specific + binutils, including assembler and linker. + +

Installation into a temporary staging area or into a chroot + jail can be achieved with the command + + 

     make DESTDIR=path-to-rootdir install
+
+

where path-to-rootdir is the absolute path of + a directory relative to which all installation paths will be + interpreted. Note that the directory specified by DESTDIR + need not exist yet; it will be created if necessary. + +

There is a subtle point with tooldirs and DESTDIR: + If you relocate a cross-compiler installation with + e.g. `DESTDIR=rootdir', then the directory + rootdir/exec-prefix/target-alias/bin 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 DESTDIR feature. + +

If you are bootstrapping a released version of GCC then please + quickly review the build status page for your release, available from + http://gcc.gnu.org/buildstat.html. + If your system is not listed for the version of GCC that you built, + send a note to + gcc@gcc.gnu.org indicating + that you successfully built and installed GCC. + Include the following information: + +

    +
  • Output from running srcdir/config.guess. Do not send + that file itself, just the one-line output from running it. + +
  • The output of `gcc -v' for your newly installed gcc. + This tells us which version of GCC you built and the options you passed to + configure. + +
  • 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 `gcc -v', but if you downloaded the + “core” compiler plus additional front ends then it isn't apparent + which ones you built unless you tell us about it. + +
  • If the build was for GNU/Linux, also include: +
      +
    • The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3); + this information should be available from /etc/issue. + +
    • The version of the Linux kernel, available from `uname --version' + or `uname -a'. + +
    • The version of glibc you used; for RPM-based systems like Red Hat, + Mandrake, and SuSE type `rpm -q glibc' to get the glibc version, + and on systems like Debian and Progeny use `dpkg -l libc6'. +
    + For other systems, you can include similar information if you think it is + relevant. + +
  • 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. +
+ +

We'd also like to know if the + host/target specific installation notes + didn't include your host/target information or if that information is + incomplete or out of date. Send a note to + gcc@gcc.gnu.org detailing how the information should be changed. + +

If you find a bug, please report it following the + bug reporting guidelines. + +

If you want to print the GCC manuals, do `cd objdir; make + dvi'. You will need to have texi2dvi (version at least 4.4) + and TeX installed. This creates a number of .dvi files in + subdirectories of objdir; these may be converted for + printing with programs such as dvips. Alternately, by using + `make pdf' in place of `make dvi', you can create documentation + in the form of .pdf files; this requires texi2pdf, which + is included with Texinfo version 4.8 and later. You can also + buy printed manuals from the Free Software Foundation, though such manuals may not be for the most + recent version of GCC. + +

If you would like to generate online HTML documentation, do `cd + objdir; make html' and HTML will be generated for the gcc manuals in + objdir/gcc/HTML. + +

+

Return to the GCC Installation page + + + + + + + + + diff -Nrcpad gcc-4.2.2/INSTALL/gfdl.html gcc-4.2.3/INSTALL/gfdl.html *** gcc-4.2.2/INSTALL/gfdl.html Thu Jan 1 00:00:00 1970 --- gcc-4.2.3/INSTALL/gfdl.html Fri Feb 1 17:06:59 2008 *************** *** 0 **** --- 1,462 ---- + + + Installing GCC: GNU Free Documentation License + + + + + + + + + + +

Installing GCC: GNU Free Documentation License

+

Installing GCC: GNU Free Documentation License

+ +

Version 1.2, November 2002
+ + 
     Copyright © 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.
+
+
    +
  1. PREAMBLE + +

    The purpose of this License is to make a manual, textbook, or other + functional and useful document free 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. + +

    This License is a kind of “copyleft”, 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. + +

    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. + +

  2. APPLICABILITY AND DEFINITIONS + +

    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 “Document”, below, + refers to any such manual or work. Any member of the public is a + licensee, and is addressed as “you”. You accept the license if you + copy, modify or distribute the work in a way requiring permission + under copyright law. + +

    A “Modified Version” 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. + +

    A “Secondary Section” 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. + +

    The “Invariant Sections” 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. + +

    The “Cover Texts” 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. + +

    A “Transparent” 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 “Transparent” is called “Opaque”. + +

    Examples of suitable formats for Transparent copies include plain + ascii without markup, Texinfo input format, LaTeX input + format, SGML or XML using a publicly available + DTD, and standard-conforming simple HTML, + PostScript or PDF designed for human modification. Examples + of transparent image formats include PNG, XCF and + JPG. Opaque formats include proprietary formats that can be + read and edited only by proprietary word processors, SGML or + XML for which the DTD and/or processing tools are + not generally available, and the machine-generated HTML, + PostScript or PDF produced by some word processors for + output purposes only. + +

    The “Title Page” 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, “Title Page” means + the text near the most prominent appearance of the work's title, + preceding the beginning of the body of the text. + +

    A section “Entitled XYZ” 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 “Acknowledgements”, + “Dedications”, “Endorsements”, or “History”.) To “Preserve the Title” + of such a section when you modify the Document means that it remains a + section “Entitled XYZ” according to this definition. + +

    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. + +

  3. VERBATIM COPYING + +

    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. + +

    You may also lend copies, under the same conditions stated above, and + you may publicly display copies. + +

  4. COPYING IN QUANTITY + +

    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. + +

    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. + +

    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. + +

    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. + +

  5. MODIFICATIONS + +

    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: + +

      +
    1. 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. + +
    2. 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. + +
    3. State on the Title page the name of the publisher of the + Modified Version, as the publisher. + +
    4. Preserve all the copyright notices of the Document. + +
    5. Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices. + +
    6. 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. + +
    7. Preserve in that license notice the full lists of Invariant Sections + and required Cover Texts given in the Document's license notice. + +
    8. Include an unaltered copy of this License. + +
    9. Preserve the section Entitled “History”, 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 “History” 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. + +
    10. 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. + 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. + +
    11. For any section Entitled “Acknowledgements” or “Dedications”, 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. + +
    12. 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. + +
    13. Delete any section Entitled “Endorsements”. Such a section + may not be included in the Modified Version. + +
    14. Do not retitle any existing section to be Entitled “Endorsements” or + to conflict in title with any Invariant Section. + +
    15. Preserve any Warranty Disclaimers. +
    + +

    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. + +

    You may add a section Entitled “Endorsements”, provided it contains + nothing but endorsements of your Modified Version by various + parties—for example, statements of peer review or that the text has + been approved by an organization as the authoritative definition of a + standard. + +

    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. + +

    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. + +

  6. COMBINING DOCUMENTS + +

    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. + +

    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. + +

    In the combination, you must combine any sections Entitled “History” + in the various original documents, forming one section Entitled + “History”; likewise combine any sections Entitled “Acknowledgements”, + and any sections Entitled “Dedications”. You must delete all + sections Entitled “Endorsements.” + +

  7. COLLECTIONS OF DOCUMENTS + +

    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. + +

    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. + +

  8. AGGREGATION WITH INDEPENDENT WORKS + +

    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 “aggregate” 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. + +

    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. + +

  9. TRANSLATION + +

    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. + +

    If a section in the Document is Entitled “Acknowledgements”, + “Dedications”, or “History”, the requirement (section 4) to Preserve + its Title (section 1) will typically require changing the actual + title. + +

  10. TERMINATION + +

    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. + +

  11. FUTURE REVISIONS OF THIS LICENSE + +

    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 + http://www.gnu.org/copyleft/. + +

    Each version of the License is given a distinguishing version number. + If the Document specifies that a particular numbered version of this + License “or any later version” 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. +

+ +

ADDENDUM: How to use this License for your documents

+ +

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: + + 

       Copyright (C)  year  your name.
+        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''.
+
+

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, + replace the “with...Texts.” line with this: + + 

         with the Invariant Sections being list their titles, with
+          the Front-Cover Texts being list, and with the Back-Cover Texts
+          being list.
+
+

If you have Invariant Sections without Cover Texts, or some other + combination of the three, merge those two alternatives to suit the + situation. + +

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. + + + + + +

+

Return to the GCC Installation page + + + + + diff -Nrcpad gcc-4.2.2/INSTALL/index.html gcc-4.2.3/INSTALL/index.html *** gcc-4.2.2/INSTALL/index.html Thu Jan 1 00:00:00 1970 --- gcc-4.2.3/INSTALL/index.html Fri Feb 1 17:06:58 2008 *************** *** 0 **** --- 1,123 ---- + + + Installing GCC + + + + + + + + + + +

Installing GCC

+ The latest version of this document is always available at + http://gcc.gnu.org/install/. + +

This document describes the generic installation procedure for GCC as well + as detailing some target specific installation instructions. + +

GCC includes several components that previously were separate distributions + with their own installation instructions. This document supersedes all + package specific installation instructions. + +

Before starting the build/install procedure please check the + host/target specific installation notes. + We recommend you browse the entire generic installation instructions before + you proceed. + +

Lists of successful builds for released versions of GCC are + available at http://gcc.gnu.org/buildstat.html. + These lists are updated as new information becomes available. + +

The installation procedure itself is broken into five steps. + +

    +
  1. Prerequisites +
  2. Downloading the source +
  3. Configuration +
  4. Building +
  5. Testing (optional) +
  6. Final install +
+ +

Please note that GCC does not support `make uninstall' 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. + +

There are also some old installation instructions, + which are mostly obsolete but still contain some information which has + not yet been merged into the main part of this manual. + +

+

Return to the GCC Installation page + +

Copyright © 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006 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. + + + + + + + + + + + + + + + diff -Nrcpad gcc-4.2.2/INSTALL/old.html gcc-4.2.3/INSTALL/old.html *** gcc-4.2.2/INSTALL/old.html Thu Jan 1 00:00:00 1970 --- gcc-4.2.3/INSTALL/old.html Fri Feb 1 17:06:59 2008 *************** *** 0 **** --- 1,212 ---- + + + Installing GCC: Old documentation + + + + + + + + + + +

Installing GCC: Old documentation

+

Old installation documentation

+ +

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. + +

Here is the procedure for installing GCC on a GNU or Unix system. + +

    +
  1. 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 + as, ld or whatever is appropriate. + +

    Alternatively, you can do subsequent compilation using a value of the + PATH environment variable such that the necessary GNU tools come + before the standard system tools. + +

  2. Specify the host, build and target machine configurations. You do this + when you run the configure script. + +

    The build machine is the system which you are using, the + host machine is the system where you want to run the resulting + compiler (normally the build machine), and the target machine is + the system for which you want the compiler to generate code. + +

    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 configure; 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 + configure cannot figure out what your configuration is or guesses + wrong. + +

    In those cases, specify the build machine's configuration name + with the --host option; the host and target will default to be + the same as the host machine. + +

    Here is an example: + + 

              ./configure --host=sparc-sun-sunos4.1
+
    +

    A configuration name may be canonical or it may be more or less + abbreviated. + +

    A canonical configuration name has three parts, separated by dashes. + It looks like this: `cpu-company-system'. + (The three parts may themselves contain dashes; configure + can figure out which dashes serve which purpose.) For example, + `m68k-sun-sunos4.1' specifies a Sun 3. + +

    You can also replace parts of the configuration by nicknames or aliases. + For example, `sun3' stands for `m68k-sun', so + `sun3-sunos4.1' is another way to specify a Sun 3. + +

    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. + +

    See Configurations, 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. + +

+ +

Configurations Supported by GCC

+ Here are the possible CPU types: + +
+ + 1750a, a29k, alpha, arm, avr, cn, 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. +
+ +

Here are the recognized company names. As you can see, customary + abbreviations are used rather than the longer official names. + + +

+ 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. +
+ +

The company name is meaningful only to disambiguate when the rest of + the information supplied is insufficient. You can omit it, writing + just `cpu-system', if it is not needed. For example, + `vax-ultrix4.2' is equivalent to `vax-dec-ultrix4.2'. + +

Here is a list of system types: + +

+ 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. +
+ +

You can omit the system type; then configure guesses the + operating system from the CPU and company. + +

You can add a version number to the system type; this may or may not + make a difference. For example, you can write `bsd4.3' or + `bsd4.4' to distinguish versions of BSD. In practice, the version + number is most needed for `sysv3' and `sysv4', which are often + treated differently. + +

`linux-gnu' is the canonical name for the GNU/Linux target; however + GCC will also accept `linux'. The version of the kernel in use is + not relevant on these systems. A suffix such as `libc1' or `aout' + distinguishes major versions of the C library; all of the suffixed versions + are obsolete. + +

If you specify an impossible combination such as `i860-dg-vms', + then you may get an error message from configure, or it may + ignore part of the information and do the best it can with the rest. + configure always prints the canonical name for the alternative + that it used. GCC does not support all possible alternatives. + +

Often a particular model of machine has a name. Many machine names are + recognized as aliases for CPU/company combinations. Thus, the machine + name `sun3', mentioned above, is an alias for `m68k-sun'. + 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: + +

+ 3300, 3b1, 3bn, 7300, altos3068, altos, + apollo68, att-7300, balance, + convex-cn, crds, decstation-3100, + decstation, delta, encore, + fx2800, gmicro, hp7nn, hp8nn, + hp9k2nn, hp9k3nn, hp9k7nn, + hp9k8nn, 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. +
+ +

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 `local' as the company name to access them. If you use + configuration `cpu-local', the configuration name + without the cpu prefix + is used to form the configuration file names. + +

Thus, if you specify `m68k-local', configuration uses + files m68k.md, local.h, m68k.c, + xm-local.h, t-local, and x-local, all in the + directory config/m68k. +

+

Return to the GCC Installation page + + + + + + diff -Nrcpad gcc-4.2.2/INSTALL/prerequisites.html gcc-4.2.3/INSTALL/prerequisites.html *** gcc-4.2.2/INSTALL/prerequisites.html Thu Jan 1 00:00:00 1970 --- gcc-4.2.3/INSTALL/prerequisites.html Fri Feb 1 17:06:58 2008 *************** *** 0 **** --- 1,236 ---- + + + Prerequisites for GCC + + + + + + + + + + +

Prerequisites for GCC

+ + GCC requires that various tools and packages be available for use in the + build procedure. Modifying GCC sources requires additional tools + described below. + +

Tools/packages necessary for building GCC

+ +
+
ISO C90 compiler
Necessary to bootstrap GCC, although versions of GCC prior + to 3.4 also allow bootstrapping with a traditional (K&R) C compiler. + +

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. + +

GNAT
+ 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. + +
A “working” POSIX compatible shell, or GNU bash
+ Necessary when running configure because some + /bin/sh shells have bugs and may crash when configuring the + target libraries. In other cases, /bin/sh or ksh + have disastrous corner-case performance problems. This + can cause target configure runs to literally take days to + complete in some cases. + +

So on some platforms /bin/ksh is sufficient, on others it + isn't. See the host/target specific instructions for your platform, or + use bash to be sure. Then set CONFIG_SHELL in your + environment to your “good” shell prior to running + configure/make. + +

zsh is not a fully compliant POSIX shell and will not + work when configuring GCC. + +

GNU binutils
+ Necessary in some circumstances, optional in others. See the + host/target specific instructions for your platform for the exact + requirements. + +
gzip version 1.2.4 (or later) or
bzip2 version 1.0.2 (or later)
+ Necessary to uncompress GCC tar files when source code is + obtained via FTP mirror sites. + +
GNU make version 3.79.1 (or later)
+ You must have GNU make installed to build GCC. + +
GNU tar version 1.14 (or later)
+ Necessary (only on some platforms) to untar the source code. Many + systems' tar programs will also work, only try GNU + tar if you have problems. + +
GNU Multiple Precision Library (GMP) version 4.1 (or later)
+ Necessary to build the Fortran frontend. If you do not have it + installed in your library search path, you will have to configure with + the --with-gmp configure option. See also + --with-gmp-lib and --with-gmp-include. + +
MPFR Library version 2.2.1 (or later)
+ Necessary to build the Fortran frontend. It can be downloaded from + http://www.mpfr.org/. The version of MPFR that is bundled with + GMP 4.1.x contains numerous bugs. Although GNU Fortran will appear + to function with the buggy versions of MPFR, there are a few GNU Fortran + bugs that will not be fixed when using this version. It is strongly + recommended to upgrade to the recommended version of MPFR. + +

The --with-mpfr configure option should be used if your MPFR + Library is not installed in your default library search path. See + also --with-mpfr-lib and --with-mpfr-include. + +

jar, or InfoZIP (zip and unzip)
+ Necessary to build libgcj, the GCJ runtime. + +
+ +

Tools/packages necessary for modifying GCC

+ +
+
autoconf versions 2.13 and 2.59
GNU m4 version 1.4 (or later)
+ Necessary when modifying configure.ac, aclocal.m4, etc. + to regenerate configure and config.in files. Most + directories require autoconf 2.59 (exactly), but the toplevel + still requires autoconf 2.13 (exactly). + +
automake version 1.9.6
+ Necessary when modifying a Makefile.am file to regenerate its + associated Makefile.in. + +

Much of GCC does not use automake, so directly edit the Makefile.in + file. Specifically this applies to the gcc, intl, + libcpp, libiberty, libobjc directories as well + as any of their subdirectories. + +

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. + +

gettext version 0.14.5 (or later)
+ Needed to regenerate gcc.pot. + +
gperf version 2.7.2 (or later)
+ Necessary when modifying gperf input files, e.g. + gcc/cp/cfns.gperf to regenerate its associated header file, e.g. + gcc/cp/cfns.h. + +
DejaGnu 1.4.4
Expect
Tcl
+ Necessary to run the GCC testsuite; see the section on testing for details. + +
autogen version 5.5.4 (or later) and
guile version 1.4.1 (or later)
+ Necessary to regenerate fixinc/fixincl.x from + fixinc/inclhack.def and fixinc/*.tpl. + +

Necessary to run `make check' for fixinc. + +

Necessary to regenerate the top level Makefile.in file from + Makefile.tpl and Makefile.def. + +

GNU Bison version 1.28 (or later)
Berkeley yacc (byacc) is also reported to work other + than for GCJ. + +

Necessary when modifying *.y files. + +

Necessary to build GCC during development because the generated output + files are not included in the SVN repository. They are included in + releases. + +

Flex version 2.5.4 (or later)
+ Necessary when modifying *.l files. + +

Necessary to build GCC during development because the generated output + files are not included in the SVN repository. They are included in + releases. + +

Texinfo version 4.4 (or later)
+ Necessary for running makeinfo when modifying *.texi + files to test your changes. + +

Necessary for running make dvi or make pdf to + create printable documentation in DVI or PDF format. Texinfo version + 4.8 or later is required for make pdf. + +

Necessary to build GCC documentation during development because the + generated output files are not included in the SVN repository. They are + included in releases. + +

TeX (any working version)
+ Necessary for running texi2dvi and texi2pdf, which + are used when running make dvi or make pdf to create + DVI or PDF files, respectively. + +
SVN (any version)
SSH (any version)
+ Necessary to access the SVN repository. Public releases and weekly + snapshots of the development sources are also available via FTP. + +
Perl version 5.6.1 (or later)
+ Necessary when regenerating Makefile dependencies in libiberty. + Necessary when regenerating libiberty/functions.texi. + Necessary when generating manpages from Texinfo manuals. + Necessary when targetting Darwin, building libstdc++, + and not using --disable-symvers. + Used by various scripts to generate some files included in SVN (mainly + Unicode-related and rarely changing) from source tables. + +
GNU diffutils version 2.7 (or later)
+ Useful when submitting patches for the GCC source code. + +
patch version 2.5.4 (or later)
+ Necessary when applying patches, created with diff, to one's + own sources. + +
+ +

+

Return to the GCC Installation page + + + + + + + + + + + + + + diff -Nrcpad gcc-4.2.2/INSTALL/specific.html gcc-4.2.3/INSTALL/specific.html *** gcc-4.2.2/INSTALL/specific.html Thu Jan 1 00:00:00 1970 --- gcc-4.2.3/INSTALL/specific.html Fri Feb 1 17:06:58 2008 *************** *** 0 **** --- 1,1687 ---- + + + Host/Target specific installation notes for GCC + + + + + + + + + + +

Host/Target specific installation notes for GCC

+ + Please read this document carefully before installing the + GNU Compiler Collection on your machine. + +

Note that this list of install notes is not 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. + +

+ + + +

+

+ +

alpha*-*-*

+ +

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. + +

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. + +

+ +

alpha*-dec-osf*

+ +

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. + +

As of GCC 3.2, versions before alpha*-dec-osf4 are no longer + supported. (These are the versions which identify themselves as DEC + OSF/1.) + +

In Digital Unix V4.0, virtual memory exhausted bootstrap failures + may be fixed by configuring with --with-gc=simple, + reconfiguring Kernel Virtual Memory and Swap parameters + per the /usr/sbin/sys_check Tuning Suggestions, + or applying the patch in + http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html. + +

In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not + currently (2001-06-13) work with mips-tfile. As a workaround, + we need to use the old assembler, invoked via the barely documented + -oldas option. To bootstrap GCC, you either need to use the + Compaq C Compiler: + + 

        % CC=cc srcdir/configure [options] [target]
+
+

or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0: + + 

        % CC=gcc -Wa,-oldas srcdir/configure [options] [target]
+
+

As of GNU binutils 2.11.2, neither GNU as nor GNU ld + are supported on Tru64 UNIX, so you must not configure GCC with + --with-gnu-as or --with-gnu-ld. + +

GCC writes a `.verstamp' 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 /usr/include/stamp.h. If you install a + new version of DEC Unix, you should rebuild GCC to pick up the new version + stamp. + +

Note that since the Alpha is a 64-bit architecture, cross-compilers from + 32-bit machines will not generate code as efficient as that generated + when the compiler is running on a 64-bit machine because many + optimizations that depend on being able to represent a word on the + target in an integral value on the host cannot be performed. Building + cross-compilers on the Alpha for 32-bit machines has only been tested in + a few cases and may not work properly. + +

`make compare' may fail on old versions of DEC Unix unless you add + -save-temps to CFLAGS. 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 stage1 and + stage2 compilations. The option -save-temps forces a + fixed name to be used for the assembler input file, instead of a + randomly chosen name in /tmp. Do not add -save-temps + unless the comparisons fail without that option. If you add + -save-temps, you will have to manually delete the `.i' and + `.s' files after each series of compilations. + +

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 --with-stabs option of configure above + for more information on these formats and how to select them. + +

There is a bug in DEC's assembler that produces incorrect line numbers + for ECOFF format when the `.align' 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 -O is specified are + different depending on whether or not -g is also specified. + +

To avoid this behavior, specify -gstabs+ and use GDB instead of + DBX. DEC is now aware of this problem with the assembler and hopes to + provide a fix shortly. + +

+ +

alphaev5-cray-unicosmk*

+ +

Cray T3E systems running Unicos/Mk. + +

This port is incomplete and has many known bugs. We hope to improve the + support for this target soon. Currently, only the C front end is supported, + and it is not possible to build parallel applications. Cray modules are not + supported; in particular, Craylibs are assumed to be in + /opt/ctl/craylibs/craylibs. + +

On this platform, you need to tell GCC where to find the assembler and + the linker. The simplest way to do so is by providing --with-as + and --with-ld to configure, e.g. + + 

         configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
+            --enable-languages=c
+
+

The comparison test at the end of the bootstrapping process fails on Unicos/Mk + because the assembler inserts timestamps into object files. You should + be able to work around this by doing `make all' after getting this + failure. + +

+ +

arc-*-elf

+ +

Argonaut ARC processor. + This configuration is intended for embedded systems. + +

+ +

arm-*-elf

+ +

xscale-*-*

+ +

ARM-family processors. Subtargets that use the ELF object format + require GNU binutils 2.13 or newer. Such subtargets include: + arm-*-freebsd, arm-*-netbsdelf, arm-*-*linux, + arm-*-rtems and arm-*-kaos. + +

+ +

arm-*-coff

+ +

ARM-family processors. Note that there are two different varieties + of PE format subtarget supported: arm-wince-pe and + arm-pe as well as a standard COFF target arm-*-coff. + +

+ +

arm-*-aout

+ +

ARM-family processors. These targets support the AOUT file format: + arm-*-aout, arm-*-netbsd. + +

+ +

avr

+ +

ATMEL AVR-family micro controllers. These are used in embedded + applications. There are no standard Unix configurations. + See “AVR Options” in the main manual + for the list of supported MCU types. + +

Use `configure --target=avr --enable-languages="c"' to configure GCC. + +

Further installation notes and other useful information about AVR tools + can also be obtained from: + +

+ +

We strongly recommend using binutils 2.13 or newer. + +

The following error: + 

       Error: register required
+
+

indicates that you should upgrade to a newer version of the binutils. + +

+ +

Blackfin

+ +

The Blackfin processor, an Analog Devices DSP. + See “Blackfin Options” in the main manual + +

More information, and a version of binutils with support for this processor, + is available at http://blackfin.uclinux.org + +

+ +

c4x

+ +

Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal + Processors. These are used in embedded applications. There are no + standard Unix configurations. + See “TMS320C3x/C4x Options” in the main manual + for the list of supported MCU types. + +

GCC can be configured as a cross compiler for both the C3x and C4x + architectures on the same system. Use `configure --target=c4x + --enable-languages="c,c++"' to configure. + +

Further installation notes and other useful information about C4x tools + can also be obtained from: + +

+ +

+ +

CRIS

+ +

CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip + series. These are used in embedded applications. + +

See “CRIS Options” in the main manual + for a list of CRIS-specific options. + +

There are a few different CRIS targets: +

+
cris-axis-aout
Old target. Includes a multilib for the `elinux' a.out-based + target. No multilibs for newer architecture variants. +
cris-axis-elf
Mainly for monolithic embedded systems. Includes a multilib for the + `v10' core used in `ETRAX 100 LX'. +
cris-axis-linux-gnu
A GNU/Linux port for the CRIS architecture, currently targeting + `ETRAX 100 LX' by default. +
+ +

For cris-axis-aout and cris-axis-elf you need binutils 2.11 + or newer. For cris-axis-linux-gnu you need binutils 2.12 or newer. + +

Pre-packaged tools can be obtained from + ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/. More + information about this platform is available at + http://developer.axis.com/. + +

+ +

CRX

+ +

The CRX CompactRISC architecture is a low-power 32-bit architecture with + fast context switching and architectural extensibility features. + +

See “CRX Options” in the main manual for a list of CRX-specific options. + +

Use `configure --target=crx-elf --enable-languages=c,c++' to configure + GCC for building a CRX cross-compiler. The option `--target=crx-elf' + is also used to build the `newlib' C library for CRX. + +

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: + `gcc/libstdc++-v3/configure --host=crx-elf --with-newlib + --enable-sjlj-exceptions --enable-cxx-flags='-fexceptions -frtti'' + +

+ +

DOS

+ +

Please have a look at the binaries page. + +

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. + +

+ +

*-*-freebsd*

+ +

The version of binutils installed in /usr/bin 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. + +

Support for FreeBSD 1 was discontinued in GCC 3.2. + +

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 /usr/bin) and C++ EH failures were noted. + +

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 -gstabs instead + of -g, 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, --enable-threads 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. + +

In principle, --enable-threads is now compatible with + --enable-libgcj on FreeBSD. However, it has only been built + and tested on `i386-*-freebsd[45]' and `alpha-*-freebsd[45]'. + 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. + +

Shared libgcc_s.so is now built and installed by default. + +

+ +

h8300-hms

+ +

Renesas H8/300 series of processors. + +

Please have a look at the binaries page. + +

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. + +

+ +

hppa*-hp-hpux*

+ +

Support for HP-UX version 9 and older was discontinued in GCC 3.4. + +

We require using gas/binutils on all hppa platforms; + you may encounter a variety of problems if you try to use the HP assembler. + +

Specifically, -g does not work on HP-UX (since that system + uses a peculiar debugging format which GCC does not know about), unless + you use GAS and GDB. It may be helpful to configure GCC with the + --with-gnu-as and + --with-as=... options to ensure that GCC can find GAS. + +

If you wish to use the pa-risc 2.0 architecture support with a 32-bit + runtime, you must use gas/binutils 2.11 or newer. + +

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 `hppa1*' machine. + +

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. + +

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, UNIX_STD can be set to `95' + or `98'. Another way is to add an appropriate set of predefines + to CC. The description for the munix= option contains + a list of the predefines used with each standard. + +

As of GCC 4.1, DWARF2 exception handling is available on HP-UX. + It is now the default. This exposed a bug in the handling of data + relocations in the GAS assembler. The handling of 64-bit data relocations + was seriously broken, affecting debugging and exception support on all + `hppa64-*-*' targets. Under some circumstances, 32-bit data relocations + could also be handled incorrectly. This problem is fixed in GAS version + 2.16.91 20051125. + +

GCC versions prior to 4.1 incorrectly passed and returned complex + values. They are now passed in the same manner as aggregates. + +

More specific information to `hppa*-hp-hpux*' targets follows. + +

+ +

hppa*-hp-hpux10

+ +

For hpux10.20, we highly recommend you pick up the latest sed patch + PHCO_19798 from HP. HP has two sites which provide patches free of + charge: + +

+ +

The HP assembler on these systems has some problems. Most notably the + assembler 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 `make all-host all-target' + after getting the failure from `make'. + +

GCC 4.0 requires CVS binutils as of April 28, 2004 or later. Earlier + versions require binutils 2.8 or later. + +

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. + +

+ +

hppa*-hp-hpux11

+ +

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. + +

Refer to binaries 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. The libffi and libjava + haven't been ported to HP-UX and don't build. + +

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. + +

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 + --enable-languages="c,c++,f77,objc" option in your configure + command. + +

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. + +

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 `hppa[1-2]*-hp-hpux11*' target generates code + for the 32-bit PA-RISC runtime architecture and uses the HP linker. + The `hppa64-hp-hpux11*' target generates 64-bit code for the + PA-RISC 2.0 architecture. The HP and GNU linkers are both supported + for this target. + +

The script config.guess now selects the target type based on the compiler + detected during configuration. You must define PATH or CC so + that configure finds an appropriate compiler for the initial bootstrap. + When CC is used, the definition should contain the options that are + needed whenever CC is used. + +

Specifically, options that determine the runtime architecture must be + in CC to correctly select the target for the build. It is also + convenient to place many other compiler options in CC. For example, + CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE" + can be used to bootstrap the GCC 3.3 branch with the HP compiler in + 64-bit K&R/bundled mode. The +DA2.0W option will result in + the automatic selection of the `hppa64-hp-hpux11*' 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 + -Ac option. These defines aren't necessary with -Ae. + +

It is best to explicitly configure the `hppa64-hp-hpux11*' target + with the --with-ld=... 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 been reported to sometimes occur in unified builds of + binutils and GCC. + +

GCC 3.0 through 3.2 require binutils 2.11 or above. GCC 3.3 through + GCC 4.0 require binutils 2.14 or later. + +

Although the HP assembler can be used for an initial build, it shouldn't + be used with any languages other than C and perhaps Fortran due to its + many limitations. 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. You can't generate debugging information when using + the HP assembler. Finally, bootstrapping fails in the final + comparison of object modules due to the time stamps that it inserts into + the modules. The bootstrap can be continued from this point with + `make all-host all-target'. + +

A recent linker patch must be installed for the correct operation of + GCC 3.3 and later. PHSS_26559 and PHSS_24304 are the + oldest linker patches that are known to work. They are for HP-UX + 11.00 and 11.11, respectively. PHSS_24303, the companion to + PHSS_24304, 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. + +

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. + +

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 +init and +fini 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. + +

There are a number of issues to consider in selecting which linker to + use with the 64-bit port. The GNU 64-bit linker can only create dynamic + binaries. The -static option causes linking with archive + libraries but doesn't produce a truly static binary. Dynamic binaries + still require final binding by the dynamic loader to resolve a set of + dynamic-loader-defined symbols. The default behavior of the HP linker + is the same as the GNU linker. However, it can generate true 64-bit + static binaries using the +compat option. + +

The HP 64-bit linker doesn't support linkonce semantics. As a + result, C++ programs have many more sections than they should. + +

The GNU 64-bit linker has some issues with shared library support + and exceptions. As a result, we only support libgcc in archive + format. For similar reasons, dwarf2 unwind and exception support + are disabled. The GNU linker also has problems creating binaries + with -static. It doesn't provide stubs for internal + calls to global functions in shared libraries, so these calls + can't be overloaded. + +

Thread support is not implemented in GCC 3.0 through 3.2, so the + --enable-threads configure option does not work. In 3.3 + and later, POSIX threads are supported. The optional DCE thread + library is not supported. + +

This port still is undergoing significant development. + +

+ +

*-*-linux-gnu

+ +

Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present + in glibc 2.2.5 and later. More information is available in the + libstdc++-v3 documentation. + +

+ +

i?86-*-linux*aout

+ +

Use this configuration to generate a.out binaries on Linux-based + GNU systems. This configuration is being superseded. + +

+ +

i?86-*-linux*

+ +

As of GCC 3.3, binutils 2.13.1 or later is required for this platform. + See bug 10877 for more information. + +

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 www.bitwizard.nl. + +

+ +

i?86-*-sco3.2v5*

+ +

Use this for the SCO OpenServer Release 5 family of operating systems. + +

Unlike earlier versions of GCC, the ability to generate COFF with this + target is no longer provided. + +

Earlier versions of GCC emitted DWARF 1 when generating ELF to allow + the system debugger to be used. That support was too burdensome to + maintain. GCC now emits only DWARF 2 for this target. This means you + may use either the UDK debugger or GDB to debug programs built by this + version of GCC. + +

GCC is now only supported on releases 5.0.4 and later, and requires that + you install Support Level Supplement OSS646B or later, and Support Level + Supplement OSS631C or later. If you are using release 5.0.7 of + OpenServer, you must have at least the first maintenance pack installed + (this includes the relevant portions of OSS646). OSS646, also known as + the “Execution Environment Update”, provides updated link editors and + assemblers, as well as updated standard C and math libraries. The C + startup modules are also updated to support the System V gABI draft, and + GCC relies on that behavior. OSS631 provides a collection of commonly + used open source libraries, some of which GCC depends on (such as GNU + gettext and zlib). SCO OpenServer Release 5.0.7 has all of this built + in by default, but OSS631C and later also apply to that release. Please + visit + ftp://ftp.sco.com/pub/openserver5 + for the latest versions of these (and other potentially useful) + supplements. + +

Although there is support for using the native assembler, it is + recommended that you configure GCC to use the GNU assembler. You do + this by using the flags + --with-gnu-as. You should + use a modern version of GNU binutils. Version 2.13.2.1 was used for all + testing. In general, only the --with-gnu-as option is tested. + A modern bintuils (as well as a plethora of other development related + GNU utilities) can be found in Support Level Supplement OSS658A, the + “GNU Development Tools” package. See the SCO web and ftp sites for details. + That package also contains the currently “officially supported” version of + GCC, version 2.95.3. It is useful for bootstrapping this version. + +

+ +

i?86-*-solaris2.10

+ +

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. + +

It is recommended that you configure GCC to use the GNU assembler in + /usr/sfw/bin/gas but the Sun linker, using the options + --with-gnu-as --with-as=/usr/sfw/bin/gas --without-gnu-ld + --with-ld=/usr/ccs/bin/ld. + +

+ +

i?86-*-udk

+ +

This target emulates the SCO Universal Development Kit and requires that + package be installed. (If it is installed, you will have a + /udk/usr/ccs/bin/cc file present.) It's very much like the + `i?86-*-unixware7*' target + but is meant to be used when hosting on a system where UDK isn't the + default compiler such as OpenServer 5 or Unixware 2. This target will + generate binaries that will run on OpenServer, Unixware 2, or Unixware 7, + with the same warnings and caveats as the SCO UDK. + +

This target is a little tricky to build because we have to distinguish + it from the native tools (so it gets headers, startups, and libraries + from the right place) while making the tools not think we're actually + building a cross compiler. The easiest way to do this is with a configure + command like this: + + 

         CC=/udk/usr/ccs/bin/cc /your/path/to/gcc/configure \
+            --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
+
+

You should substitute `i686' in the above command with the appropriate + processor for your host. + +

After the usual `make' and + `make install', you can then access the UDK-targeted GCC + tools by adding udk- before the commonly known name. For + example, to invoke the C compiler, you would use udk-gcc. + They will coexist peacefully with any native-target GCC tools you may + have installed. + +

+ +

ia64-*-linux

+ +

IA-64 processor (also known as IPF, or Itanium Processor Family) + running GNU/Linux. + +

If you are using the installed system libunwind library with + --with-system-libunwind, then you must use libunwind 0.98 or + later. + +

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. + +

+ +

ia64-*-hpux*

+ +

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 --with-gnu-as may be necessary. + +

The GCC libunwind library has not been ported to HPUX. This means that for + GCC versions 3.2.3 and earlier, --enable-libunwind-exceptions + is required to build GCC. For GCC 3.3 and later, this is the default. + For gcc 3.4.3 and later, --enable-libunwind-exceptions is + removed and the system libunwind library will always be used. + +

+ + +

*-ibm-aix*

+ +

Support for AIX version 3 and older was discontinued in GCC 3.4. + +

“out of memory” bootstrap failures may indicate a problem with + process resource limits (ulimit). Hard limits are configured in the + /etc/security/limits system configuration file. + +

To speed up the configuration phases of bootstrapping and installing GCC, + one may use GNU Bash instead of AIX /bin/sh, e.g., + + 

        % CONFIG_SHELL=/opt/freeware/bin/bash
+         % export CONFIG_SHELL
+
+

and then proceed as described in the build instructions, where we strongly recommend specifying an absolute path + to invoke srcdir/configure. + +

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. + +

Errors involving alloca when building GCC generally are due + to an incorrect definition of CC 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 must be invoked as cc + (not xlc). Once configure has been informed of + xlc, one needs to use `make distclean' to remove the + configure cache files and ensure that CC environment variable + does not provide a definition that will confuse configure. + If this error occurs during stage2 or later, then the problem most likely + is the version of Make (see above). + +

The native as and ld 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. + +

Building libstdc++.a 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) + +

`libstdc++' in GCC 3.4 increments the major version number of the + shared object and GCC installation places the libstdc++.a + 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 `libstdc++' shared object needs to be available + to the AIX runtime loader. The GCC 3.1 `libstdc++.so.4', if + present, and GCC 3.3 `libstdc++.so.5' shared objects can be + installed for runtime dynamic loading using the following steps to set + the `F_LOADONLY' flag in the shared object for each + multilib libstdc++.a installed: + +

Extract the shared objects from the currently installed + libstdc++.a archive: + 

        % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
+
+

Enable the `F_LOADONLY' flag so that the shared object will be + available for runtime dynamic loading, but not linking: + 

        % strip -e libstdc++.so.4 libstdc++.so.5
+
+

Archive the runtime-only shared object in the GCC 3.4 + libstdc++.a archive: + 

        % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
+
+

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. + +

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. + 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 -g + option of the archive command may be used to create archives of 32-bit + objects using the original “small format”. A correct version of the + routines is shipped with AIX 4.3.2 and above. + +

Some versions of the AIX binder (linker) can fail with a relocation + overflow severe error when the -bbigtoc 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 + techsupport.services.ibm.com + website as PTF U455193. + +

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 + techsupport.services.ibm.com + website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above. + +

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 + techsupport.services.ibm.com + website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above. + +

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., `.' vs `,' 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 LANG + environment variable to `C' or `En_US'. + +

By default, GCC for AIX 4.1 and above produces code that can be used on + both Power or PowerPC processors. + +

A default can be specified with the -mcpu=cpu_type + switch and using the configure option --with-cpu-cpu_type. + +

+ +

iq2000-*-elf

+ +

Vitesse IQ2000 processors. These are used in embedded + applications. There are no standard Unix configurations. + +

+ +

m32c-*-elf

+ +

Renesas M32C processor. + This configuration is intended for embedded systems. + +

+ +

m32r-*-elf

+ +

Renesas M32R processor. + This configuration is intended for embedded systems. + +

+ +

m6811-elf

+ +

Motorola 68HC11 family micro controllers. These are used in embedded + applications. There are no standard Unix configurations. + +

+ +

m6812-elf

+ +

Motorola 68HC12 family micro controllers. These are used in embedded + applications. There are no standard Unix configurations. + +

+ +

m68k-hp-hpux

+ +

HP 9000 series 300 or 400 running HP-UX. HP-UX version 8.0 has a bug in + the assembler that prevents compilation of GCC. This + bug manifests itself during the first stage of compilation, while + building libgcc2.a: + + 

     _floatdisf
+      cc1: warning: `-g' option not supported on this version of GCC
+      cc1: warning: `-g1' option not supported on this version of GCC
+      ./xgcc: Internal compiler error: program as got fatal signal 11
+
+

A patched version of the assembler is available as the file + ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler. If you + have HP software support, the patch can also be obtained directly from + HP, as described in the following note: + +

+ This is the patched assembler, to patch SR#1653-010439, where the + assembler aborts on floating point constants. + +

The bug is not really in the assembler, but in the shared library + version of the function “cvtnum(3c)”. The bug on “cvtnum(3c)” is + SR#4701-078451. Anyway, the attached assembler uses the archive + library version of “cvtnum(3c)” and thus does not exhibit the bug. +

+ +

This patch is also known as PHCO_4484. + +

In addition gdb does not understand that native HP-UX format, so + you must use gas if you wish to use gdb. + +

On HP-UX version 8.05, but not on 8.07 or more recent versions, the + fixproto shell script triggers a bug in the system shell. If you + encounter this problem, upgrade your operating system or use BASH (the + GNU shell) to run fixproto. This bug will cause the fixproto + program to report an error of the form: + + 

     ./fixproto: sh internal 1K buffer overflow
+
+

To fix this, you can also change the first line of the fixproto script + to look like: + + 

     #!/bin/ksh
+
+

+ +

mips-*-*

+ +

If on a MIPS system you get an error message saying “does not have gp + sections for all it's [sic] sectons [sic]”, 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. + +

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. + +

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 `mips*-*-*' use the generic implementation instead. You can also + configure for `mipsel-elf' as a workaround. The + `mips*-*-linux*' target continues to use the MIPS II routines. More + work on this is expected in future releases. + +

MIPS systems check for division by zero (unless + -mno-check-zero-division 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 (SIGFPE). To enable + the use of break, use the --with-divide=breaks + configure option when configuring GCC. The default is to + use traps on systems that support them. + +

Cross-compilers for the MIPS as target using the MIPS assembler + currently do not work, because the auxiliary programs + mips-tdump.c and mips-tfile.c 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. + +

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 libgcj.so, to + be incorrectly generated. Binutils CVS snapshots and releases made + after Nov. 9, 2006 are thought to be free from both of these problems. + +

+ +

mips-sgi-irix5

+ +

In order to compile GCC on an SGI running IRIX 5, the `compiler_dev.hdr' + subsystem must be installed from the IDO CD-ROM supplied by SGI. + It is also available for download from + ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist. + +

If you use the MIPS C compiler to bootstrap, it may be necessary + to increase its table size for switch statements with the + -Wf,-XNg1500 option. If you use the -O2 + optimization option, you also need to use -Olimit 3000. + +

To enable debugging under IRIX 5, you must use GNU binutils 2.15 or + later, and use the --with-gnu-ld configure option + when configuring GCC. You need to use GNU ar and nm, + also distributed with GNU binutils. + +

Some users have reported that /bin/sh will hang during bootstrap. + This problem can be avoided by running the commands: + + 

        % CONFIG_SHELL=/bin/ksh
+         % export CONFIG_SHELL
+
+

before starting the build. + +

+ +

mips-sgi-irix6

+ +

If you are using SGI's MIPSpro cc as your bootstrap compiler, you must + ensure that the N32 ABI is in use. To test this, compile a simple C + file with cc and then run file on the + resulting object file. The output should look like: + + 

     test.o: ELF N32 MSB ...
+
+

If you see: + + 

     test.o: ELF 32-bit MSB ...
+
+

or + + 

     test.o: ELF 64-bit MSB ...
+
+

then your version of cc uses the O32 or N64 ABI by default. You + should set the environment variable CC to `cc -n32' + before configuring GCC. + +

If you want the resulting gcc to run on old 32-bit systems + with the MIPS R4400 CPU, you need to ensure that only code for the `mips3' + instruction set architecture (ISA) is generated. While GCC 3.x does + this correctly, both GCC 2.95 and SGI's MIPSpro cc may change + the ISA depending on the machine where GCC is built. Using one of them + as the bootstrap compiler may result in `mips4' code, which won't run at + all on `mips3'-only systems. For the test program above, you should see: + + 

     test.o: ELF N32 MSB mips-3 ...
+
+

If you get: + + 

     test.o: ELF N32 MSB mips-4 ...
+
+

instead, you should set the environment variable CC to `cc + -n32 -mips3' or `gcc -mips3' respectively before configuring GCC. + +

MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining + memcmp. Either add -U__INLINE_INTRINSICS to the CC + environment variable as a workaround or upgrade to MIPSpro C 7.4.1m. + +

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 --disable-multilib so GCC doesn't + try to use them. This will disable building the O32 libraries, too. + Look for /usr/lib64/libc.so.1 to see if you + have the 64-bit libraries installed. + +

To enable debugging for the O32 ABI, you must use GNU as from + GNU binutils 2.15 or later. You may also use GNU ld, but + this is not required and currently causes some problems with Ada. + +

The --enable-threads option doesn't currently work, a patch is + in preparation for a future release. The --enable-libgcj + option is disabled by default: IRIX 6 uses a very low default limit + (20480) for the command line length. Although libtool contains a + workaround for this problem, at least the N64 `libgcj' is known not + to build despite this, running into an internal error of the native + ld. A sure fix is to increase this limit (`ncargs') to + its maximum of 262144 bytes. If you have root access, you can use the + systune command to do this. + +

wchar_t support in `libstdc++' is not available for old + IRIX 6.5.x releases, x < 19. The problem cannot be autodetected + and in order to build GCC for such targets you need to configure with + --disable-wchar_t. + +

See http://freeware.sgi.com/ for more + information about using GCC on IRIX platforms. + +

+ +

powerpc-*-*

+ +

You can specify a default version for the -mcpu=cpu_type + switch by using the configure option --with-cpu-cpu_type. + +

+ +

powerpc-*-darwin*

+ +

PowerPC running Darwin (Mac OS X kernel). + +

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 + http://developer.apple.com/darwin/projects/compiler/ (free + registration required). + +

This version of GCC requires at least cctools-590.7. + +

The version of GCC shipped by Apple typically includes a number of + extensions not available in a standard GCC release. These extensions + are generally for backwards compatibility and best avoided. + +

+ +

powerpc-*-elf, powerpc-*-sysv4

+ +

PowerPC system in big endian mode, running System V.4. + +

+ +

powerpc*-*-linux-gnu*

+ +

You will need + binutils 2.15 + or newer for a working GCC. + +

+ +

powerpc-*-netbsd*

+ +

PowerPC system in big endian mode running NetBSD. To build the + documentation you will need Texinfo version 4.4 (NetBSD 1.5.1 included + Texinfo version 3.12). + +

+ +

powerpc-*-eabisim

+ +

Embedded PowerPC system in big endian mode for use in running under the + PSIM simulator. + +

+ +

powerpc-*-eabi

+ +

Embedded PowerPC system in big endian mode. + +

+ +

powerpcle-*-elf, powerpcle-*-sysv4

+ +

PowerPC system in little endian mode, running System V.4. + +

+ +

powerpcle-*-eabisim

+ +

Embedded PowerPC system in little endian mode for use in running under + the PSIM simulator. + +

+ +

powerpcle-*-eabi

+ +

Embedded PowerPC system in little endian mode. + +

+ +

s390-*-linux*

+ +

S/390 system running GNU/Linux for S/390. + +

+ +

s390x-*-linux*

+ +

zSeries system (64-bit) running GNU/Linux for zSeries. + +

+ +

s390x-ibm-tpf*

+ +

zSeries system (64-bit) running TPF. This platform is + supported as cross-compilation target only. + +

+ + + + +

*-*-solaris2*

+ +

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 + binaries page for details. + +

The Solaris 2 /bin/sh will often fail to configure + libstdc++-v3, boehm-gc or libjava. We therefore + recommend using the following initial sequence of commands + + 

        % CONFIG_SHELL=/bin/ksh
+         % export CONFIG_SHELL
+
+

and proceed as described in the configure instructions. + In addition we strongly recommend specifying an absolute path to invoke + srcdir/configure. + +

Solaris 2 comes with a number of optional OS packages. Some of these + are needed to use GCC fully, namely SUNWarc, + SUNWbtool, SUNWesu, SUNWhea, SUNWlibm, + SUNWsprot, and SUNWtoo. 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. + +

To check whether an optional package is installed, use + the pkginfo command. To add an optional package, use the + pkgadd command. For further details, see the Solaris 2 + documentation. + +

Trying to use the linker and other tools in + /usr/ucb to install GCC has been observed to cause trouble. + For example, the linker may hang indefinitely. The fix is to remove + /usr/ucb from your PATH. + +

The build process works more smoothly with the legacy Sun tools so, if you + have /usr/xpg4/bin in your PATH, we recommend that you place + /usr/bin before /usr/xpg4/bin for the duration of the build. + +

All releases of GNU binutils prior to 2.11.2 have known bugs on this + platform. We recommend the use of GNU binutils 2.11.2 or later, or the + vendor tools (Sun as, Sun ld). Note that your mileage + may vary if you use a combination of the GNU tools and the Sun tools: while + the combination GNU as + Sun ld should reasonably work, + the reverse combination Sun as + GNU ld is known to + cause memory corruption at runtime in some cases for C++ programs. + +

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 + http://sourceware.org/ml/binutils-cvs/2004-09/msg00036.html to the + release. + +

We recommend using GNU binutils 2.16 or later in conjunction with GCC 4.x, + or the vendor tools (Sun as, Sun ld). 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 + http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html to the + release. + +

Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or + newer: g++ will complain that types are missing. These headers assume + that omitting the type means int; this assumption worked for C89 but + is wrong for C++, and is now wrong for C99 also. + +

g++ accepts such (invalid) constructs with the option + -fpermissive; it + will assume that any missing type is int (as defined by C89). + +

There are patches for Solaris 2.6 (105633-56 or newer for SPARC, + 106248-42 or newer for Intel), 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. + +

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 expect + program which is used only by the GCC testsuite driver. When the bug + causes the expect program to miss anticipated output, extra + testsuite failures appear. + +

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. + +

+ +

sparc-sun-solaris2*

+ +

When GCC is configured to use binutils 2.11.2 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. + +

Sun as 4.x is broken in that it cannot cope with long symbol names. + A typical error message might look similar to the following: + + 

     /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
+        can't compute value of an expression involving an external symbol.
+
+

This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris + 2.6 and has been fixed in later (5.x) versions of the assembler, + starting with Solaris 7. + +

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 -m64 option enables 64-bit code generation. + However, if all you want is code tuned for the UltraSPARC CPU, you + should try the -mtune=ultrasparc option instead, which produces + code that, unlike full 64-bit code, can still run on non-UltraSPARC + machines. + +

When configuring on a Solaris 7 or later system that is running a kernel + that supports only 32-bit binaries, one must configure with + --disable-multilib, since we will not be able to build the + 64-bit target libraries. + +

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. + +

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. + +

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 + groff 1.19.1 without getting messages similar to the following: + + 

     ld: warning: relocation error: R_SPARC_UA32: ...
+        external symbolic relocation against non-allocatable section
+        .debug_info cannot be processed at runtime: relocation ignored.
+
+

To work around this problem, compile with -gstabs+ instead of + plain -g. + +

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 build 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: + + 

        % ./configure --build=sparc-sun-solaris2.7 --prefix=xxx
+
+

+ +

sparc-sun-solaris2.7

+ +

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. + +

Here are some workarounds to this problem: +

    +
  • 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. + +
  • Copy the original, unpatched Solaris 7 + /usr/ccs/bin/as into + /usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as, + adjusting the latter name to fit your local conventions and software + version numbers. + +
  • 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. +
+ +

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: + + 

     ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
+        symbol <unknown>:  offset 0xffffffff7ec133e7 is non-aligned.
+
+

This bug has been fixed in the final 5.0 version of the assembler. + +

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: + + 

     ld: fatal: relocation error: R_SPARC_DISP32:
+        file .libs/libstdc++.lax/libsupc++convenience.a/vterminate.o:
+          symbol <unknown>: offset 0xfccd33ad is non-aligned
+
+

This bug has been fixed in more recent revisions of the assembler. + +

+ +

sparc-*-linux*

+ +

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 sparc-*-* targets. + +

+ +

sparc64-*-solaris2*

+ +

When configuring the GNU Multiple Precision Library (GMP) or the + MPFR library, the canonical target triplet must be specified as + the build parameter on the configure line. For example + on a Solaris 7 system: + + 

        % ./configure --build=sparc64-sun-solaris2.7 --prefix=xxx
+
+

The following compiler flags must be specified in the configure + step in order to bootstrap this target with the Sun compiler: + + 

        % CC="cc -xarch=v9 -xildoff" srcdir/configure [options] [target]
+
+

-xarch=v9 specifies the SPARC-V9 architecture to the Sun toolchain + and -xildoff turns off the incremental linker. + +

+ +

sparcv9-*-solaris2*

+ +

This is a synonym for sparc64-*-solaris2*. + +

+ +

*-*-sysv*

+ +

On System V release 3, you may get this error message + while linking: + + 

     ld fatal: failed to write symbol name something
+       in strings table for file whatever
+
+

This probably indicates that the disk is full or your ulimit won't allow + the file to be as large as it needs to be. + +

This problem can also result because the kernel parameter MAXUMEM + is too small. If so, you must regenerate the kernel and make the value + much larger. The default value is reported to be 1024; a value of 32768 + is said to work. Smaller values may also work. + +

On System V, if you get an error like this, + + 

     /usr/local/lib/bison.simple: In function `yyparse':
+      /usr/local/lib/bison.simple:625: virtual memory exhausted
+
+

that too indicates a problem with disk space, ulimit, or MAXUMEM. + +

On a System V release 4 system, make sure /usr/bin precedes + /usr/ucb in PATH. The cc command in + /usr/ucb uses libraries which have bugs. + +

+ +

vax-dec-ultrix

+ +

Don't try compiling with VAX C (vcc). It produces incorrect code + in some cases (for example, when alloca is used). + +

+ +

*-*-vxworks*

+ +

Support for VxWorks is in flux. At present GCC supports only 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 “configlette” (see below). We are + not interested in supporting older, a.out or COFF-based, versions of + VxWorks in GCC 3. + +

VxWorks comes with an older version of GCC installed in + $WIND_BASE/host; we recommend you do not overwrite it. + Choose an installation prefix entirely outside $WIND_BASE. + Before running configure, create the directories prefix + and prefix/bin. Link or copy the appropriate assembler, + linker, etc. into prefix/bin, and set your PATH to + include that directory while running both configure and + make. + +

You must give configure the + --with-headers=$WIND_BASE/target/h switch so that it can + find the VxWorks system headers. Since VxWorks is a cross compilation + target only, you must also specify --target=target. + configure will attempt to create the directory + prefix/target/sys-include and copy files into it; + make sure the user running configure has sufficient privilege + to do so. + +

GCC's exception handling runtime requires a special “configlette” + module, contrib/gthr_supp_vxw_5x.c. Follow the instructions in + that file to add the module to your kernel build. (Future versions of + VxWorks will incorporate this module.) + +

+ +

x86_64-*-*, amd64-*-*

+ +

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 -m32 switch). + +

+ +

xtensa-*-elf

+ +

This target is intended for embedded Xtensa systems using the + `newlib' 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. + +

The Xtensa configuration information must be specified prior to + building GCC. The include/xtensa-config.h 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. + +

+ +

xtensa-*-linux*

+ +

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 + -fpic or -fPIC options are used. In other + respects, this target is the same as the + `xtensa-*-elf' target. + +

+ +

Microsoft Windows (32-bit)

+ +

Ports of GCC are included with the + Cygwin environment. + +

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. + +

+ +

OS/2

+ +

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 http://www.goof.com/pcg/os2/. + +

+ +

Older systems

+ +

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. + +

Starting with GCC 3.1, each release has a list of “obsoleted” systems. + Support for these systems is still present in that release, but + configure will fail unless the --enable-obsolete + option is given. Unless a maintainer steps forward, support for these + systems will be removed from the next release of GCC. + +

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 + old-releases directory on the GCC mirror sites. Header bugs may generally be avoided using + fixincludes, but bugs or deficiencies in libraries and the + operating system may still cause problems. + +

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 + following the usual requirements would be + likely to be accepted, since they should not affect the support for more + modern targets. + +

For some systems, old versions of GNU binutils may also be useful, + and are available from pub/binutils/old-releases on + sourceware.org mirror sites. + +

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. + +

+ +

all ELF targets (SVR4, Solaris 2, etc.)

+ +

C++ support is significantly better on ELF targets if you use the + GNU linker; duplicate copies of + inlines, vtables and template instantiations will be discarded + automatically. + +

+

Return to the GCC Installation page + + + + + + + diff -Nrcpad gcc-4.2.2/INSTALL/test.html gcc-4.2.3/INSTALL/test.html *** gcc-4.2.2/INSTALL/test.html Thu Jan 1 00:00:00 1970 --- gcc-4.2.3/INSTALL/test.html Fri Feb 1 17:06:59 2008 *************** *** 0 **** --- 1,234 ---- + + + Installing GCC: Testing + + + + + + + + + + +

Installing GCC: Testing

+ + 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 + gcc-testresults mailing list. + Some of these archived results are linked from the build status lists + at http://gcc.gnu.org/buildstat.html, 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. + +

First, you must have downloaded the testsuites. + These are part of the full distribution, but if you downloaded the + “core” compiler plus any front ends, you must download the testsuites + separately. + +

Second, you must have the testing tools installed. This includes + DejaGnu, Tcl, and Expect; + the DejaGnu site has links to these. + +

If the directories where runtest and expect were + installed are not in the PATH, you may need to set the following + environment variables appropriately, as in the following example (which + assumes that DejaGnu has been installed under /usr/local): + + 

          TCL_LIBRARY = /usr/local/share/tcl8.0
+           DEJAGNULIBS = /usr/local/share/dejagnu
+
+

(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.) + +

Finally, you can run the testsuite (which may take a long time): + 

          cd objdir; make -k check
+
+

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 + `WARNING: Couldn't find the global config file.' or + `WARNING: Couldn't find tool init file' that can be ignored. + +

0.1 How can you run the testsuite on selected tests?

+ +

In order to run sets of tests selectively, there are targets + `make check-gcc' and `make check-g++' + in the gcc subdirectory of the object directory. You can also + just run `make check' in a subdirectory of the object directory. + +

A more selective way to just run all gcc execute tests in the + testsuite is to use + + 

         make check-gcc RUNTESTFLAGS="execute.exp other-options"
+
+

Likewise, in order to run only the g++ “old-deja” tests in + the testsuite with filenames matching `9805*', you would use + + 

         make check-g++ RUNTESTFLAGS="old-deja.exp=9805* other-options"
+
+

The *.exp files are located in the testsuite directories of the GCC + source, the most important ones being compile.exp, + execute.exp, dg.exp and old-deja.exp. + To get a list of the possible *.exp files, pipe the + output of `make check' into a file and look at the + `Running ... .exp' lines. + +

0.2 Passing options and running multiple testsuites

+ +

You can pass multiple options to the testsuite using the + `--target_board' option of DejaGNU, either passed as part of + `RUNTESTFLAGS', or directly to runtest if you prefer to + work outside the makefiles. For example, + + 

         make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fno-strength-reduce"
+
+

will run the standard g++ testsuites (“unix” is the target name + for a standard native testsuite situation), passing + `-O3 -fno-strength-reduce' to the compiler on every test, i.e., + slashes separate options. + +

You can run the testsuites multiple times using combinations of options + with a syntax similar to the brace expansion of popular shells: + + 

         ..."--target_board=arm-sim/{-mhard-float,-msoft-float}{-O1,-O2,-O3,}"
+
+

(Note the empty option caused by the trailing comma in the final group.) + The following will run each testsuite eight times using the `arm-sim' + target, as if you had specified all possible combinations yourself: + + 

         --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
+
+

They can be combined as many times as you wish, in arbitrary ways. This + list: + + 

         ..."--target_board=unix/-Wextra{-O3,-fno-strength-reduce}{-fomit-frame-pointer,}"
+
+

will generate four combinations, all involving `-Wextra'. + +

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 make + do the parallel runs. Instead of using `--target_board', use a + special makefile target: + + 

         make -jN check-testsuite//test-target/option1/option2/...
+
+

For example, + + 

         make -j3 check-gcc//sh-hms-sim/{-m1,-m2,-m3,-m3e,-m4}/{,-nofpu}
+
+

will run three concurrent “make-gcc” testsuites, eventually testing all + ten combinations as described above. Note that this is currently only + supported in the gcc subdirectory. (To see how this works, try + typing echo before the example given here.) + +

0.3 Additional testing for Java Class Libraries

+ +

The Java runtime tests can be executed via `make check' + in the target/libjava/testsuite directory in + the build tree. + +

The Mauve Project 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 libjava/testsuite/libjava.mauve/mauve, or by + specifying the location of that tree when invoking `make', as in + `make MAUVEDIR=~/mauve check'. + +

Jacks + is a free testsuite that tests Java compiler front ends. This suite + can be run as part of libgcj testing by placing the Jacks tree within + the libjava testsuite at libjava/testsuite/libjava.jacks/jacks. + +

0.4 How to interpret test results

+ +

The result of running the testsuite are various *.sum and *.log + files in the testsuite subdirectories. The *.log files contain a + detailed log of the compiler invocations and the corresponding + results, the *.sum files summarize the results. These summaries + contain status codes for all tests: + +

    +
  • PASS: the test passed as expected +
  • XPASS: the test unexpectedly passed +
  • FAIL: the test unexpectedly failed +
  • XFAIL: the test failed as expected +
  • UNSUPPORTED: the test is not supported on this platform +
  • ERROR: the testsuite detected an error +
  • WARNING: the testsuite detected a possible problem +
+ +

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. + +

0.5 Submitting test results

+ +

If you want to report the results to the GCC project, use the + contrib/test_summary shell script. Start it in the objdir with + + 

         srcdir/contrib/test_summary -p your_commentary.txt \
+              -m gcc-testresults@gcc.gnu.org |sh
+
+

This script uses the Mail program to send the results, so + make sure it is in your PATH. The file your_commentary.txt 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. + +

+

Return to the GCC Installation page + + + + + + + + + + diff -Nrcpad gcc-4.2.2/LAST_UPDATED gcc-4.2.3/LAST_UPDATED *** gcc-4.2.2/LAST_UPDATED Sun Oct 7 21:23:17 2007 --- gcc-4.2.3/LAST_UPDATED Fri Feb 1 17:06:51 2008 *************** *** 1 **** ! Obtained from SVN: tags/gcc_4_2_2_release revision 129115 --- 1 ---- ! Obtained from SVN: tags/gcc_4_2_3_release revision 132046 diff -Nrcpad gcc-4.2.2/MD5SUMS gcc-4.2.3/MD5SUMS *** gcc-4.2.2/MD5SUMS Mon Oct 8 00:11:38 2007 --- gcc-4.2.3/MD5SUMS Fri Feb 1 18:46:00 2008 *************** *** 1,5 **** # This file contains the MD5 checksums of the files in the ! # gcc-4.2.2.tar.bz2 tarball. # # Besides verifying that all files in the tarball were correctly expanded, # it also can be used to determine if any files have changed since the --- 1,5 ---- # This file contains the MD5 checksums of the files in the ! # gcc-4.2.3.tar.bz2 tarball. # # Besides verifying that all files in the tarball were correctly expanded, # it also can be used to determine if any files have changed since the *************** *** 9,32 **** # md5sum -c MD5SUMS | grep -v "OK$" 8c00452ef1e298846493ec8b239f93e2 ABOUT-NLS ! 3d40011fdd9e30e9d4f909cc03f82dcf BUGS 59530bdf33659b29e73d4adb9f9f6552 COPYING 2d5025d4aa3495befef8f17206a5b0a1 COPYING.LIB ! 7b93a1c14103dd27153511e26be8a890 ChangeLog 09538b708302f1735f6fa05b622ecf5e ChangeLog.tree-ssa ! f0e63c08bc8d08ad59ba61ce41e28f0b FAQ 23b8927fe1fb0ab321c09a4f0500aa4c INSTALL/README ! 319c2136cfbbd92538d9b4074d33bcbc LAST_UPDATED 504884fee05251c1ce68d3d44917718f MAINTAINERS e038573d7ce023eed6f1a546f0cb3536 Makefile.def 34e1f150c69f192d1f087a786e09385e Makefile.in 766c8d66e07de3e49ca0e3a8534c85b8 Makefile.tpl ! 0be4146b6da165e629f2fe4a3a02ae3b NEWS 750a7546d281ac42eb2ce87949457731 README de94b5f5c3d835b587741180b2ded958 README.SCO b510a5285eb05298b5f3d9f5ae920588 boehm-gc/AmigaOS.c 2caafacabf758bb76a9dfce1fc544b97 boehm-gc/BCC_MAKEFILE ! 388272cf07e972f604f81a0ccad159fa boehm-gc/ChangeLog c18075e3729cd116028480307a8e845d boehm-gc/EMX_MAKEFILE 3b7cc3be9ed3c2135bbda990e8a69303 boehm-gc/MacOS.c 5cf7764626b7dd7272b2fe11403d1b6a boehm-gc/MacProjects.sit.hqx --- 9,43 ---- # md5sum -c MD5SUMS | grep -v "OK$" 8c00452ef1e298846493ec8b239f93e2 ABOUT-NLS ! 1d205c0517467755e6c601969039904b BUGS 59530bdf33659b29e73d4adb9f9f6552 COPYING 2d5025d4aa3495befef8f17206a5b0a1 COPYING.LIB ! 127bb48f3693dc96df7123b56ff034d4 ChangeLog 09538b708302f1735f6fa05b622ecf5e ChangeLog.tree-ssa ! f553d6e37d5c9805b8f9854539542e8c FAQ 23b8927fe1fb0ab321c09a4f0500aa4c INSTALL/README ! 38c1f828be410ee466ebb4d78d229553 INSTALL/binaries.html ! e662a18097ab7c31c94793fa1311f29e INSTALL/build.html ! 6da7a8a4cb2946419c8cda5c2fb207c0 INSTALL/configure.html ! ffece079958d4a09dab8a44eaeea60bf INSTALL/download.html ! 03e09a33b5ab0fa6a44d2a99c0077f4b INSTALL/finalinstall.html ! 104cd937760a8781ca92ae8a086f5ba7 INSTALL/gfdl.html ! 3b0ef58c4ffa841cbcab883afe0a8850 INSTALL/index.html ! 5de6f00c0fb817150d7b3c25fc0c9e37 INSTALL/old.html ! 8a5c10bd78979aa7b9d7da0395399f20 INSTALL/prerequisites.html ! 0dd988692162a478e69d2597c2c1675f INSTALL/specific.html ! be5ea5e1a3ff5bea9d9eb9365337fd3a INSTALL/test.html ! 07ef4af960defea869f923d3ad9ae87d LAST_UPDATED 504884fee05251c1ce68d3d44917718f MAINTAINERS e038573d7ce023eed6f1a546f0cb3536 Makefile.def 34e1f150c69f192d1f087a786e09385e Makefile.in 766c8d66e07de3e49ca0e3a8534c85b8 Makefile.tpl ! 63dc34f0633c1f50af4f6f9f2dfaf92a NEWS 750a7546d281ac42eb2ce87949457731 README de94b5f5c3d835b587741180b2ded958 README.SCO b510a5285eb05298b5f3d9f5ae920588 boehm-gc/AmigaOS.c 2caafacabf758bb76a9dfce1fc544b97 boehm-gc/BCC_MAKEFILE ! ffa01aeb60f5f4a1664a61c98d867c48 boehm-gc/ChangeLog c18075e3729cd116028480307a8e845d boehm-gc/EMX_MAKEFILE 3b7cc3be9ed3c2135bbda990e8a69303 boehm-gc/MacOS.c 5cf7764626b7dd7272b2fe11403d1b6a boehm-gc/MacProjects.sit.hqx *************** deb33a288bb6bee23ac46c1e0717708e boehm- *** 149,155 **** 8d5174061c55cce476c14c315fb5a302 boehm-gc/include/private/gc_hdrs.h 499f4837a20abd22b377f360db6b5461 boehm-gc/include/private/gc_locks.h 4f7c11f389c4b9cc843d53da0534fc0e boehm-gc/include/private/gc_pmark.h ! 9eedf58bbdf7de10ea5247371acf13d1 boehm-gc/include/private/gc_priv.h 48aed6d7458e0df7280717b2a918d430 boehm-gc/include/private/gcconfig.h 5549846c2f7dcd83f8550fd307f86c25 boehm-gc/include/private/pthread_stop_world.h c6d1a299be177e91e40ec5a8c3de616b boehm-gc/include/private/pthread_support.h --- 160,166 ---- 8d5174061c55cce476c14c315fb5a302 boehm-gc/include/private/gc_hdrs.h 499f4837a20abd22b377f360db6b5461 boehm-gc/include/private/gc_locks.h 4f7c11f389c4b9cc843d53da0534fc0e boehm-gc/include/private/gc_pmark.h ! 059f844c381994b5fbb6af92af0b6a2c boehm-gc/include/private/gc_priv.h 48aed6d7458e0df7280717b2a918d430 boehm-gc/include/private/gcconfig.h 5549846c2f7dcd83f8550fd307f86c25 boehm-gc/include/private/pthread_stop_world.h c6d1a299be177e91e40ec5a8c3de616b boehm-gc/include/private/pthread_support.h *************** ebb806366e4b75f72ac42bfcdda1d318 boehm- *** 170,176 **** 243e968dd0ce5897ecf1900c3ab8e5eb boehm-gc/pcr_interface.c 02b90724d8113cdaab4ca5b84e24cde0 boehm-gc/powerpc_darwin_mach_dep.s b3eb3643da5f28bdc4d5a57dfcf057ea boehm-gc/pthread_stop_world.c ! 0864a487714a7abb2496f746fb74ac76 boehm-gc/pthread_support.c 8df5132173bc2d55d2feaefc9067e97d boehm-gc/ptr_chck.c 89d7ce652a21c4bdfa74466317cf7a87 boehm-gc/real_malloc.c 62e563f3994c2834866b132defd3b9b4 boehm-gc/reclaim.c --- 181,187 ---- 243e968dd0ce5897ecf1900c3ab8e5eb boehm-gc/pcr_interface.c 02b90724d8113cdaab4ca5b84e24cde0 boehm-gc/powerpc_darwin_mach_dep.s b3eb3643da5f28bdc4d5a57dfcf057ea boehm-gc/pthread_stop_world.c ! 70d1c6f020259e4c0162b1f06fb0abe9 boehm-gc/pthread_support.c 8df5132173bc2d55d2feaefc9067e97d boehm-gc/ptr_chck.c 89d7ce652a21c4bdfa74466317cf7a87 boehm-gc/real_malloc.c 62e563f3994c2834866b132defd3b9b4 boehm-gc/reclaim.c *************** b4834cbbfc9ef7f3d1d4bd504d46bff1 boehm- *** 191,203 **** 40d32d7abf9aac98f33d23251e51ada6 boehm-gc/typd_mlc.c 44e275fac2f2c6dd7307f757bde00506 boehm-gc/version.h 2b15399d69a04edb706a80623096dd1b boehm-gc/win32_threads.c ! b634bc93697ffc3f197b3a5c9ec5e321 bugs.html b2a35e98453194ca837c363ee9c0d379 compile c9658176f5e7dea04e29a145f4e14ee0 config-ml.in 3e47cb5e8b78144a240bd27a1468d23b config.guess 46f36a6ce11978ea07e2199f3c5cd665 config.rpath 3de1c83afeb4d2b5510e593e33134479 config.sub ! 55c89c05854daeb5730767d6490e81fa config/ChangeLog 6c7b0890dc93bdd97ec3e90d8436b384 config/acinclude.m4 db0d80389bf92e481cc11a7231e49beb config/acx.m4 04bdbef77f5fd2e282f7dee0bde60444 config/codeset.m4 --- 202,214 ---- 40d32d7abf9aac98f33d23251e51ada6 boehm-gc/typd_mlc.c 44e275fac2f2c6dd7307f757bde00506 boehm-gc/version.h 2b15399d69a04edb706a80623096dd1b boehm-gc/win32_threads.c ! 9852a22284c27d0a3c77293be9b31b11 bugs.html b2a35e98453194ca837c363ee9c0d379 compile c9658176f5e7dea04e29a145f4e14ee0 config-ml.in 3e47cb5e8b78144a240bd27a1468d23b config.guess 46f36a6ce11978ea07e2199f3c5cd665 config.rpath 3de1c83afeb4d2b5510e593e33134479 config.sub ! 9e2fb038db0f3e7be8bd3c4ef45b5083 config/ChangeLog 6c7b0890dc93bdd97ec3e90d8436b384 config/acinclude.m4 db0d80389bf92e481cc11a7231e49beb config/acx.m4 04bdbef77f5fd2e282f7dee0bde60444 config/codeset.m4 *************** e47fe530a7ba5c354041bfc943d58132 config *** 264,270 **** cfd07f1c037572cf40f78bdc26ed29dc config/warnings.m4 538a1fbe5de517578aaebe3566458807 configure e78b6b151dc4fe35a3e8850d39f82279 configure.in ! ddbcfef14fcd85eb45adc8741692f4d7 contrib/ChangeLog 7af8d2979bf1a7cfa88e30d05fa22be2 contrib/ChangeLog.tree-ssa 90c0bf1648d0fd5e9aa319f0c4ad7613 contrib/analyze_brprob fe795a3c68f0a5514df4cb94cbb0032b contrib/compareSumTests3 --- 275,281 ---- cfd07f1c037572cf40f78bdc26ed29dc config/warnings.m4 538a1fbe5de517578aaebe3566458807 configure e78b6b151dc4fe35a3e8850d39f82279 configure.in ! 580fafcfe4de02f993c2cb143f510043 contrib/ChangeLog 7af8d2979bf1a7cfa88e30d05fa22be2 contrib/ChangeLog.tree-ssa 90c0bf1648d0fd5e9aa319f0c4ad7613 contrib/analyze_brprob fe795a3c68f0a5514df4cb94cbb0032b contrib/compareSumTests3 *************** a97cf630fc2119f8a1a0743f277f59a9 contri *** 281,292 **** 59304fc08afa489baa6b920cc76dc625 contrib/gthr_supp_vxw_5x.c fa945bac89ee68b410027dcfe1312f4b contrib/index-prop 1a7e182574673a0ba979ec4ebca2944c contrib/paranoia.cc ! c7f61742e45f8c07e07119b91546396a contrib/reghunt/ChangeLog ab31219466ac7df2a1aa15900540bc8a contrib/reghunt/README b66cd5ab901ec3494fd700125172dba0 contrib/reghunt/reg_periodic 624a99f8c633cfc4182fbe09295d30eb contrib/reghunt/reg_search d3dd0bcec99c2e140b86efb5f63860b4 contrib/reghunt/reg_test_template ! 94ce32f84bcdf503ca727dcddf3cbfa8 contrib/regression/ChangeLog 30553bfced1b2b46bf7ca01ef6ba69d1 contrib/regression/GCC_Regression_Tester.wdgt/Default.png ad38ddd771df222eb9d413e3c7f6a751 contrib/regression/GCC_Regression_Tester.wdgt/Icon.png 76ce1c6f8471e6c1bb07c9b9368042ce contrib/regression/GCC_Regression_Tester.wdgt/Info.plist --- 292,303 ---- 59304fc08afa489baa6b920cc76dc625 contrib/gthr_supp_vxw_5x.c fa945bac89ee68b410027dcfe1312f4b contrib/index-prop 1a7e182574673a0ba979ec4ebca2944c contrib/paranoia.cc ! 29230a9ef88c8deac4e1f9cad6ee5963 contrib/reghunt/ChangeLog ab31219466ac7df2a1aa15900540bc8a contrib/reghunt/README b66cd5ab901ec3494fd700125172dba0 contrib/reghunt/reg_periodic 624a99f8c633cfc4182fbe09295d30eb contrib/reghunt/reg_search d3dd0bcec99c2e140b86efb5f63860b4 contrib/reghunt/reg_test_template ! 57aef1629f9da838cec486919831d84a contrib/regression/ChangeLog 30553bfced1b2b46bf7ca01ef6ba69d1 contrib/regression/GCC_Regression_Tester.wdgt/Default.png ad38ddd771df222eb9d413e3c7f6a751 contrib/regression/GCC_Regression_Tester.wdgt/Icon.png 76ce1c6f8471e6c1bb07c9b9368042ce contrib/regression/GCC_Regression_Tester.wdgt/Info.plist *************** d5faa80d97899ae08accaff400923890 contri *** 305,311 **** 10240873a22da60b881e516003c1f688 contrib/warn_summary a9c51bc6c9c6d9b9d010ccd8bb4b465a depcomp bff9f3a357e53c4f37f47f0c4a20586f faq.html ! 4528432ba7d77817b65807dd529de137 fixincludes/ChangeLog d9ca7a44abbc50c35e309d86eeb70b39 fixincludes/Makefile.in 8f6ffb1014a722baf95411e040cdf203 fixincludes/README 455903ad4ff71fa5c5340ef7ae41a0e6 fixincludes/README-fixinc --- 316,322 ---- 10240873a22da60b881e516003c1f688 contrib/warn_summary a9c51bc6c9c6d9b9d010ccd8bb4b465a depcomp bff9f3a357e53c4f37f47f0c4a20586f faq.html ! d459c6f0cdac474fef5088c4e5e9482b fixincludes/ChangeLog d9ca7a44abbc50c35e309d86eeb70b39 fixincludes/Makefile.in 8f6ffb1014a722baf95411e040cdf203 fixincludes/README 455903ad4ff71fa5c5340ef7ae41a0e6 fixincludes/README-fixinc *************** b6494e752821a4f87a2114c27143856c fixinc *** 419,430 **** 4f59f83f073afacc3f59c39952ec8a7b fixincludes/tests/base/wchar.h f86a4ea6000eba71d34c1b9a7bcd2c14 fixincludes/tests/base/widec.h 174528657da1f7a179a039941810b764 gcc/ABOUT-GCC-NLS ! 6068ac325ef8d1e02292d229bf6d202d gcc/BASE-VER 59530bdf33659b29e73d4adb9f9f6552 gcc/COPYING a916467b91076e631dd8edb7424769c7 gcc/COPYING.LIB d32239bcb673463ab874e80d47fae504 gcc/COPYING3 6a6a8e020838b23406c81b19c1d46df6 gcc/COPYING3.LIB ! 831b8ee445ce07bd868d95465042d6af gcc/ChangeLog 0bb7e37d0205edea285403fa046364e9 gcc/ChangeLog-1997 3a822f7377be7a932e2cbeef86d78d2c gcc/ChangeLog-1998 261732ce4d6e6492812f8c483f59affd gcc/ChangeLog-1999 --- 430,441 ---- 4f59f83f073afacc3f59c39952ec8a7b fixincludes/tests/base/wchar.h f86a4ea6000eba71d34c1b9a7bcd2c14 fixincludes/tests/base/widec.h 174528657da1f7a179a039941810b764 gcc/ABOUT-GCC-NLS ! ea41a1828914ce8c0a01c12b0b97cbd2 gcc/BASE-VER 59530bdf33659b29e73d4adb9f9f6552 gcc/COPYING a916467b91076e631dd8edb7424769c7 gcc/COPYING.LIB d32239bcb673463ab874e80d47fae504 gcc/COPYING3 6a6a8e020838b23406c81b19c1d46df6 gcc/COPYING3.LIB ! 605926cb14b152491869a8746f3023a5 gcc/ChangeLog 0bb7e37d0205edea285403fa046364e9 gcc/ChangeLog-1997 3a822f7377be7a932e2cbeef86d78d2c gcc/ChangeLog-1998 261732ce4d6e6492812f8c483f59affd gcc/ChangeLog-1999 *************** edd13f5a74d6801758b97dea84454331 gcc/Ch *** 437,456 **** 65f4a1fcbbe29e4d63fb1b5ebffb79e2 gcc/ChangeLog-2006 98c5a6533d7e4507aba5dc4fd06014ed gcc/ChangeLog.lib f4dab29fb2c10234cb64e9c59a62f716 gcc/ChangeLog.tree-ssa ! 91fa3cb4c9355d0a52eff57867b42d07 gcc/DATESTAMP d41d8cd98f00b204e9800998ecf8427e gcc/DEV-PHASE 4804423c755a929408412852eb45e422 gcc/FSFChangeLog 5af5721f6387aa8aa5fb200e025dd573 gcc/FSFChangeLog.10 f7f665544fb6aa08551b37283f6c56de gcc/FSFChangeLog.11 d6c8d8f4cf325cd24a60d312bb247f46 gcc/LANGUAGES ! 977827694d02371222133e3828d74ba1 gcc/Makefile.in 00919fda1a585fdc4a1be1fec2eeb0bb gcc/ONEWS f88d9228718a255b827d6f417063d62d gcc/README.Portability f44aeb578969621358194ef6a8c67093 gcc/SERVICE 536a60e797f5f72f034a29844b7e0665 gcc/acinclude.m4 8e2bc73f67fed176b4c24e18ca707a7d gcc/aclocal.m4 4b3f30c21ae8661e7c9471611924cebb gcc/ada/9drpc.adb ! 715d5bf1cd1a9d85e9304d910547fe0c gcc/ada/ChangeLog ea6b5429aa670cb6f1b4f72087be2656 gcc/ada/ChangeLog.tree-ssa f96f3fa3178de7938cabe2209dd02bf1 gcc/ada/Make-lang.in 2843fbf4cb2164efcb352c10b2c74ede gcc/ada/Makefile.in --- 448,467 ---- 65f4a1fcbbe29e4d63fb1b5ebffb79e2 gcc/ChangeLog-2006 98c5a6533d7e4507aba5dc4fd06014ed gcc/ChangeLog.lib f4dab29fb2c10234cb64e9c59a62f716 gcc/ChangeLog.tree-ssa ! 94ddcad43836a21df5b3d5acedd3fed8 gcc/DATESTAMP d41d8cd98f00b204e9800998ecf8427e gcc/DEV-PHASE 4804423c755a929408412852eb45e422 gcc/FSFChangeLog 5af5721f6387aa8aa5fb200e025dd573 gcc/FSFChangeLog.10 f7f665544fb6aa08551b37283f6c56de gcc/FSFChangeLog.11 d6c8d8f4cf325cd24a60d312bb247f46 gcc/LANGUAGES ! 1d923260ee01c882ec2548ed6bda6c04 gcc/Makefile.in 00919fda1a585fdc4a1be1fec2eeb0bb gcc/ONEWS f88d9228718a255b827d6f417063d62d gcc/README.Portability f44aeb578969621358194ef6a8c67093 gcc/SERVICE 536a60e797f5f72f034a29844b7e0665 gcc/acinclude.m4 8e2bc73f67fed176b4c24e18ca707a7d gcc/aclocal.m4 4b3f30c21ae8661e7c9471611924cebb gcc/ada/9drpc.adb ! 6d4e4b7a55ad2e76e6c17f0a8e9873e1 gcc/ada/ChangeLog ea6b5429aa670cb6f1b4f72087be2656 gcc/ada/ChangeLog.tree-ssa f96f3fa3178de7938cabe2209dd02bf1 gcc/ada/Make-lang.in 2843fbf4cb2164efcb352c10b2c74ede gcc/ada/Makefile.in *************** e6eb80002e58829bab846f5b4a31ef54 gcc/ad *** 948,954 **** b34aa8e615d770870169becc32f4447f gcc/ada/elists.adb d76b5aa0629229aff763ea39469fe449 gcc/ada/elists.ads a2b470913de88e43d8a53051755fdc50 gcc/ada/elists.h ! 59557429f909b65310ea41c2996e1046 gcc/ada/env.c 510c6ca3ecf0e68d17cee32040665298 gcc/ada/env.h ca5eee8f61a033e55484a8cf77ffbf5a gcc/ada/err_vars.ads 3f413a1aeada3b29f068bd8f4572f42e gcc/ada/errno.c --- 959,965 ---- b34aa8e615d770870169becc32f4447f gcc/ada/elists.adb d76b5aa0629229aff763ea39469fe449 gcc/ada/elists.ads a2b470913de88e43d8a53051755fdc50 gcc/ada/elists.h ! f04d8e590283fdc14a8a903ce0006971 gcc/ada/env.c 510c6ca3ecf0e68d17cee32040665298 gcc/ada/env.h ca5eee8f61a033e55484a8cf77ffbf5a gcc/ada/err_vars.ads 3f413a1aeada3b29f068bd8f4572f42e gcc/ada/errno.c *************** b96f552c3d8f35984778bf894d7886fc gcc/bi *** 2207,2222 **** 5cd5930e3eb849371605836a983441a4 gcc/bt-load.c bec07403e1cfdef6db97722fa6cc0f14 gcc/builtin-attrs.def af874178d3d4b9754424d8ef022026b1 gcc/builtin-types.def ! c5d7ddc8168b8ee2316d7464eb27f18b gcc/builtins.c db3d4969a0e93cc4b0be0004f8c941c1 gcc/builtins.def 9291cdc501e013ab25611c73dfe389a7 gcc/c-aux-info.c ! 181ccc1571459f06d61dea13c8774f26 gcc/c-common.c 3087eb6dfdb77b30e46747d87e22c86e gcc/c-common.def 1389c0fceed9d399853fc97d172cf712 gcc/c-common.h 5dd0f256615c00addd02447d56547144 gcc/c-config-lang.in ddd059f15f902cf1bd04ffa470105cd3 gcc/c-convert.c c85ef762b29854c300b63c8d973b94cf gcc/c-cppbuiltin.c ! 5474ed36cc1af3cecc8f276f6cafedc5 gcc/c-decl.c df3af333ea468897e3b8fc99a968fb93 gcc/c-dump.c 81c4fa301a8756eb88afb800664e6ef4 gcc/c-errors.c e1ea9fda74ee718a50ad737ee60b83c0 gcc/c-format.c --- 2218,2233 ---- 5cd5930e3eb849371605836a983441a4 gcc/bt-load.c bec07403e1cfdef6db97722fa6cc0f14 gcc/builtin-attrs.def af874178d3d4b9754424d8ef022026b1 gcc/builtin-types.def ! 79bbef57ae83052bfd9c9c53827367ca gcc/builtins.c db3d4969a0e93cc4b0be0004f8c941c1 gcc/builtins.def 9291cdc501e013ab25611c73dfe389a7 gcc/c-aux-info.c ! f774e835c3d09c414f0e9677df5190e3 gcc/c-common.c 3087eb6dfdb77b30e46747d87e22c86e gcc/c-common.def 1389c0fceed9d399853fc97d172cf712 gcc/c-common.h 5dd0f256615c00addd02447d56547144 gcc/c-config-lang.in ddd059f15f902cf1bd04ffa470105cd3 gcc/c-convert.c c85ef762b29854c300b63c8d973b94cf gcc/c-cppbuiltin.c ! 5803b3e5e6ba4e0eb665909a6488ee09 gcc/c-decl.c df3af333ea468897e3b8fc99a968fb93 gcc/c-dump.c 81c4fa301a8756eb88afb800664e6ef4 gcc/c-errors.c e1ea9fda74ee718a50ad737ee60b83c0 gcc/c-format.c *************** d5c5d489b9251247fc4813ed9735dedf gcc/c- *** 2229,2235 **** e1d84a046fdb18c1af757f96cb5bed6b gcc/c-objc-common.c cfdcec78f33c2e39f85d03baedcca791 gcc/c-objc-common.h 898f7c9b50b6cf97a1e47a7dd5e53be7 gcc/c-omp.c ! 52b3f05af155bb96bc90be232168c650 gcc/c-opts.c 99e266b92de0c9e6e60d533b51287688 gcc/c-parser.c 70a832cd2f7c797bd07dd34307dbe4a8 gcc/c-pch.c be95d51bcc6719b2719ebff70b4faeb3 gcc/c-ppoutput.c --- 2240,2246 ---- e1d84a046fdb18c1af757f96cb5bed6b gcc/c-objc-common.c cfdcec78f33c2e39f85d03baedcca791 gcc/c-objc-common.h 898f7c9b50b6cf97a1e47a7dd5e53be7 gcc/c-omp.c ! 607742cfcf3bafe38138ce9c4b6d18ab gcc/c-opts.c 99e266b92de0c9e6e60d533b51287688 gcc/c-parser.c 70a832cd2f7c797bd07dd34307dbe4a8 gcc/c-pch.c be95d51bcc6719b2719ebff70b4faeb3 gcc/c-ppoutput.c *************** fc1c4bb5de51aa4586c4f761f34f6fcf gcc/c- *** 2239,2245 **** f8631d6672a1d2dd1e0cec443fc0d3a2 gcc/c-pretty-print.h b5b281ab09654fd5daeb52d2704555c0 gcc/c-semantics.c 6807e7402af5b98cf7d787219d9994c8 gcc/c-tree.h ! b6136f2e5d69ab598c285a7ee907ec2a gcc/c-typeck.c 0f67684af8210397e45cf5c6c34f373c gcc/c.opt 320b4c18959be8af1543ea2fdb9b5a76 gcc/caller-save.c 276f2c67235f21e27170c59933ec0fd0 gcc/calls.c --- 2250,2256 ---- f8631d6672a1d2dd1e0cec443fc0d3a2 gcc/c-pretty-print.h b5b281ab09654fd5daeb52d2704555c0 gcc/c-semantics.c 6807e7402af5b98cf7d787219d9994c8 gcc/c-tree.h ! 460e695d342a1691d309589b801a0628 gcc/c-typeck.c 0f67684af8210397e45cf5c6c34f373c gcc/c.opt 320b4c18959be8af1543ea2fdb9b5a76 gcc/caller-save.c 276f2c67235f21e27170c59933ec0fd0 gcc/calls.c *************** ab448c3733cc4817293dcfc5da8c10ea gcc/cf *** 2260,2272 **** 0fc1fe544d4c56c18487fbce3316b31b gcc/cgraph.c 8a217c9fc65846ab3e71c93d9a5066b1 gcc/cgraph.h 2b2aef9b2737f1458eefcaac7f566ce6 gcc/cgraphunit.c ! 17d7d659683504b54630b5c1939addbe gcc/collect2.c ea855a27372025f95b4f6ff536a5b6b2 gcc/collect2.h ! 36a6b81429ca3abe0c4713daabc8f3a8 gcc/combine.c ! a0a68f5efefea63e3bea2853d9bdf6d1 gcc/common.opt 162c077c493d89717647c605b5b81996 gcc/conditions.h 73d354125efd4a0c002238c5c78825e5 gcc/config.build ! 8d3842ce1a1d8703f7683df468143c67 gcc/config.gcc 294ae70d888372319947ce181205229b gcc/config.host 1d8b0cd5203b01f9dd0d113b9e4eaf3f gcc/config.in 8e697813dc96ca90f5d0f4c196efe2cc gcc/config/README --- 2271,2283 ---- 0fc1fe544d4c56c18487fbce3316b31b gcc/cgraph.c 8a217c9fc65846ab3e71c93d9a5066b1 gcc/cgraph.h 2b2aef9b2737f1458eefcaac7f566ce6 gcc/cgraphunit.c ! 43749488ecdd12ade16b4b12e6d1faef gcc/collect2.c ea855a27372025f95b4f6ff536a5b6b2 gcc/collect2.h ! 448dbc21bb39ef7a60fe80f9a4a16b5c gcc/combine.c ! 5af17703f8f30bd4149faaa24585dd21 gcc/common.opt 162c077c493d89717647c605b5b81996 gcc/conditions.h 73d354125efd4a0c002238c5c78825e5 gcc/config.build ! bee5012d4249d1c70e0b80b4475a4a30 gcc/config.gcc 294ae70d888372319947ce181205229b gcc/config.host 1d8b0cd5203b01f9dd0d113b9e4eaf3f gcc/config.in 8e697813dc96ca90f5d0f4c196efe2cc gcc/config/README *************** e83f5fbee3292540388507acfe709d3b gcc/co *** 2412,2426 **** 150ff06c89bf030644f21e036c4f3709 gcc/config/arm/xscale-coff.h 1ecddd99b880949a4497f44a6d1bb4b5 gcc/config/arm/xscale-elf.h c3c23856b0730cc23eb0d34d1c095631 gcc/config/avr/avr-protos.h ! 4fb2058991a217617183d480b234d59f gcc/config/avr/avr.c ! 89a7f91edd98ef980782c8a3a3aea81f gcc/config/avr/avr.h 2358ec5b4eaf8d97c55005fd1d96bf0f gcc/config/avr/avr.md ac844b94d5a40798808c5452fdb08e09 gcc/config/avr/avr.opt 86f767f9267f217566374f07f47077bc gcc/config/avr/constraints.md 4eb06ffe69d7cb76dda4cbe238fe3064 gcc/config/avr/libgcc.S 7d9c9d0aebe33d038c620f4f1e5c4e37 gcc/config/avr/predicates.md c8f4329d7e38c1ebe3b14b92f23eabfc gcc/config/avr/rtems.h ! d1dff726dd066f6fc01ffc5294138819 gcc/config/avr/t-avr 6aa29f64f366fd362ab1f548d54415cc gcc/config/avr/t-rtems 6f49e6e83e352ec8c25e3f6babe6ded5 gcc/config/bfin/bfin-modes.def 1f32d5ab545bc440d06cb442a85686ea gcc/config/bfin/bfin-protos.h --- 2423,2437 ---- 150ff06c89bf030644f21e036c4f3709 gcc/config/arm/xscale-coff.h 1ecddd99b880949a4497f44a6d1bb4b5 gcc/config/arm/xscale-elf.h c3c23856b0730cc23eb0d34d1c095631 gcc/config/avr/avr-protos.h ! 322ad64f4923c81442c3abdeb0980c31 gcc/config/avr/avr.c ! ac0f93537cead33b2b25f0b5df193a9e gcc/config/avr/avr.h 2358ec5b4eaf8d97c55005fd1d96bf0f gcc/config/avr/avr.md ac844b94d5a40798808c5452fdb08e09 gcc/config/avr/avr.opt 86f767f9267f217566374f07f47077bc gcc/config/avr/constraints.md 4eb06ffe69d7cb76dda4cbe238fe3064 gcc/config/avr/libgcc.S 7d9c9d0aebe33d038c620f4f1e5c4e37 gcc/config/avr/predicates.md c8f4329d7e38c1ebe3b14b92f23eabfc gcc/config/avr/rtems.h ! 496d1f490b018e205455eb9ad34297c6 gcc/config/avr/t-avr 6aa29f64f366fd362ab1f548d54415cc gcc/config/avr/t-rtems 6f49e6e83e352ec8c25e3f6babe6ded5 gcc/config/bfin/bfin-modes.def 1f32d5ab545bc440d06cb442a85686ea gcc/config/bfin/bfin-protos.h *************** d5352240b5cbe81191816502585d61e8 gcc/co *** 2502,2508 **** 1149a8352429d8477be1860c3bef0134 gcc/config/fr30/crti.asm 9555f1d0e4779becaabcae67ca84cb03 gcc/config/fr30/crtn.asm c58f03b63b4c0c2e64f4cec6b4f12c0b gcc/config/fr30/fr30-protos.h ! cd06fc0feec2e8e69c0bc0326bcb1a22 gcc/config/fr30/fr30.c c627601b7f3b0fb3f40d2b2b09a5374f gcc/config/fr30/fr30.h ac165874266f21753f6c918d9c32a469 gcc/config/fr30/fr30.md adcef6619daa932b1cf9faf22b8bdaf5 gcc/config/fr30/fr30.opt --- 2513,2519 ---- 1149a8352429d8477be1860c3bef0134 gcc/config/fr30/crti.asm 9555f1d0e4779becaabcae67ca84cb03 gcc/config/fr30/crtn.asm c58f03b63b4c0c2e64f4cec6b4f12c0b gcc/config/fr30/fr30-protos.h ! 6310277ae559d22cef3ca8e93c081dd4 gcc/config/fr30/fr30.c c627601b7f3b0fb3f40d2b2b09a5374f gcc/config/fr30/fr30.h ac165874266f21753f6c918d9c32a469 gcc/config/fr30/fr30.md adcef6619daa932b1cf9faf22b8bdaf5 gcc/config/fr30/fr30.opt *************** ab27a55034a909397036bc1c8e571856 gcc/co *** 2586,2593 **** ea5193e2314b486fedd2c427bebb814b gcc/config/i386/darwin64.h ee31756c9d90bc91a4442f55a3074f78 gcc/config/i386/djgpp.h fce27d1975ee7b2919e4426ae0001452 gcc/config/i386/djgpp.opt ! 0665edeb471e6a32da61aff51d715bcf gcc/config/i386/driver-i386.c ! 048c09c6fc9052c121bbe8ec77ddb71c gcc/config/i386/emmintrin.h 52db53cf5d98ae0bb8cd318225e82f2b gcc/config/i386/freebsd.h 49d7fe5ffb8749f9463703fbc27e2ff8 gcc/config/i386/freebsd64.h 24e11d7e075dfbaab35c083a8db69796 gcc/config/i386/gas.h --- 2597,2604 ---- ea5193e2314b486fedd2c427bebb814b gcc/config/i386/darwin64.h ee31756c9d90bc91a4442f55a3074f78 gcc/config/i386/djgpp.h fce27d1975ee7b2919e4426ae0001452 gcc/config/i386/djgpp.opt ! 2530026916ac425c0c5318cb44483151 gcc/config/i386/driver-i386.c ! 78b98fd274718ad2baa196a8e11ff76b gcc/config/i386/emmintrin.h 52db53cf5d98ae0bb8cd318225e82f2b gcc/config/i386/freebsd.h 49d7fe5ffb8749f9463703fbc27e2ff8 gcc/config/i386/freebsd64.h 24e11d7e075dfbaab35c083a8db69796 gcc/config/i386/gas.h *************** f4f2db284c5d175d36c0fec534830572 gcc/co *** 2605,2613 **** f1be9e9dbf092b26488d3768a0d21a59 gcc/config/i386/i386-interix3.h 62fd35b65df9e09cd4fb1d3e052ba51d gcc/config/i386/i386-modes.def d4bc940ca347c0d172cfd7dac640198e gcc/config/i386/i386-protos.h ! b6e33fd66a9e57900dbce61b56275b27 gcc/config/i386/i386.c d200526f60c4aab5d842c2012f06a344 gcc/config/i386/i386.h ! a65b3494e87bd4d561d9ea846623aeae gcc/config/i386/i386.md 30a11808e7a70e8cd3d88b010e517fb7 gcc/config/i386/i386.opt c1c177c416019e20a833a9a743f26772 gcc/config/i386/i386elf.h 78552f28c68b7dabc12d91cffc43d757 gcc/config/i386/k6.md --- 2616,2624 ---- f1be9e9dbf092b26488d3768a0d21a59 gcc/config/i386/i386-interix3.h 62fd35b65df9e09cd4fb1d3e052ba51d gcc/config/i386/i386-modes.def d4bc940ca347c0d172cfd7dac640198e gcc/config/i386/i386-protos.h ! 1fb1fce02e0c6b04c89c544ffa965a7a gcc/config/i386/i386.c d200526f60c4aab5d842c2012f06a344 gcc/config/i386/i386.h ! 31d2031501aa5a683e5f7fe8717b9125 gcc/config/i386/i386.md 30a11808e7a70e8cd3d88b010e517fb7 gcc/config/i386/i386.opt c1c177c416019e20a833a9a743f26772 gcc/config/i386/i386elf.h 78552f28c68b7dabc12d91cffc43d757 gcc/config/i386/k6.md *************** e2d68df3ca94c2d72ed25ce4f9a22c29 gcc/co *** 2653,2659 **** 3162ab821e194548dc3e77c0a90e11ad gcc/config/i386/sol2-cn.asm 2f69702bcb85ac597f5c1bfba8836700 gcc/config/i386/sol2-gc1.asm cdf261738cfdd22bfc708a01a32f2eb0 gcc/config/i386/sol2.h ! 847568aa8522fee3394358e45176019c gcc/config/i386/sse.md 77e5d31334a08851d6ce5df20c229e97 gcc/config/i386/sync.md 8b496e023f59646e462649d745a891b4 gcc/config/i386/sysv4-cpp.h 0e4bc5c8954c6d0b5b29d440e728d0a0 gcc/config/i386/sysv4.h --- 2664,2670 ---- 3162ab821e194548dc3e77c0a90e11ad gcc/config/i386/sol2-cn.asm 2f69702bcb85ac597f5c1bfba8836700 gcc/config/i386/sol2-gc1.asm cdf261738cfdd22bfc708a01a32f2eb0 gcc/config/i386/sol2.h ! cce24592e25b70ce09dc2228d0603864 gcc/config/i386/sse.md 77e5d31334a08851d6ce5df20c229e97 gcc/config/i386/sync.md 8b496e023f59646e462649d745a891b4 gcc/config/i386/sysv4-cpp.h 0e4bc5c8954c6d0b5b29d440e728d0a0 gcc/config/i386/sysv4.h *************** b2d4d8496fc666f096e6beb8a2bd5a1f gcc/co *** 2715,2721 **** c517746d9f7377ff4ba8008dfd9b437a gcc/config/ia64/ia64-c.c 2ce3617eaff76a6ff7c9e58039b2cc45 gcc/config/ia64/ia64-modes.def f2653fe94091c5ad087d14e319dd3cb8 gcc/config/ia64/ia64-protos.h ! a1f2a23cd1752e14eb4b3b34777acff7 gcc/config/ia64/ia64.c f3561a52625561b3e72d5b9df11ac091 gcc/config/ia64/ia64.h 22e122cc71956d454372a5f044f7bb88 gcc/config/ia64/ia64.md e5217fdb6dc575bbbe4e8a985625eab4 gcc/config/ia64/ia64.opt --- 2726,2732 ---- c517746d9f7377ff4ba8008dfd9b437a gcc/config/ia64/ia64-c.c 2ce3617eaff76a6ff7c9e58039b2cc45 gcc/config/ia64/ia64-modes.def f2653fe94091c5ad087d14e319dd3cb8 gcc/config/ia64/ia64-protos.h ! b26a8e7d19d732020dda7e4a039c3421 gcc/config/ia64/ia64.c f3561a52625561b3e72d5b9df11ac091 gcc/config/ia64/ia64.h 22e122cc71956d454372a5f044f7bb88 gcc/config/ia64/ia64.md e5217fdb6dc575bbbe4e8a985625eab4 gcc/config/ia64/ia64.opt *************** bf61eaef24e43774ae0178636ef58882 gcc/co *** 2884,2892 **** d51b6d8d52f3417d6ffa37cb66db1cfc gcc/config/mips/mips-modes.def cfb94e785549e0afef83193560406aa1 gcc/config/mips/mips-protos.h be4a81b64764bb9f2e8db0ff71604b21 gcc/config/mips/mips-ps-3d.md ! 7454e184f16e9a1eb2b3f3547a64afc4 gcc/config/mips/mips.c b0278a69a1d46182d4770168a96f9c98 gcc/config/mips/mips.h ! b51d078e6b9993ba14f46d7a8d92b87c gcc/config/mips/mips.md ea252d7176b8eac91502e85ae08ee7e5 gcc/config/mips/mips.opt 03c8fb3041bfcb2f2356b14d2faad5c4 gcc/config/mips/mips16.S 4ac52f9f7e3df664020892c36d0d8c6d gcc/config/mips/netbsd.h --- 2895,2903 ---- d51b6d8d52f3417d6ffa37cb66db1cfc gcc/config/mips/mips-modes.def cfb94e785549e0afef83193560406aa1 gcc/config/mips/mips-protos.h be4a81b64764bb9f2e8db0ff71604b21 gcc/config/mips/mips-ps-3d.md ! 7c4b146e9e2adda822e5e268858d539b gcc/config/mips/mips.c b0278a69a1d46182d4770168a96f9c98 gcc/config/mips/mips.h ! 786e06a44323be134978261f155bd175 gcc/config/mips/mips.md ea252d7176b8eac91502e85ae08ee7e5 gcc/config/mips/mips.opt 03c8fb3041bfcb2f2356b14d2faad5c4 gcc/config/mips/mips16.S 4ac52f9f7e3df664020892c36d0d8c6d gcc/config/mips/netbsd.h *************** a4210fa3a3f4165356d6a813b0b4edc5 gcc/co *** 2955,2988 **** eefd6081497d56467864a111613f397b gcc/config/pa/lib2funcs.asm 52aa8211ab4116065e45b378223eddd3 gcc/config/pa/linux-unwind.h c2cc9c83c626de0329e1bfbdec7c6cfb gcc/config/pa/milli64.S ! ec72ef3582cd6e7c0c972fc3d66e5be0 gcc/config/pa/pa-64.h ! 43523505c26257460b5645d777d3f17f gcc/config/pa/pa-hpux.h c648bc371bab81fa1f4acd6c4eb8f0db gcc/config/pa/pa-hpux.opt ! 525af2e61b5a080f153af570e5cc4888 gcc/config/pa/pa-hpux10.h d452d460c0195601ba6c082db4f4712a gcc/config/pa/pa-hpux1010.h af2a4676245f1f7fd4a5fdea710ab6a6 gcc/config/pa/pa-hpux1010.opt ! 353b508fd998242158b4e2d98cad01f2 gcc/config/pa/pa-hpux11.h fafe040d7a38b97e371a3c84845e4c5f gcc/config/pa/pa-hpux1111.h 6b7808fef171673f40789b8c0da45349 gcc/config/pa/pa-hpux1111.opt 217a72bceca0c1711fbad3a7a23e4551 gcc/config/pa/pa-linux.h 01b8e14468e166bb285428fdc6a20bd3 gcc/config/pa/pa-modes.def a81e3d2ac855c4207c39f363e23a4767 gcc/config/pa/pa-osf.h c0f1cc0f27d9ce8d0ec3a466f18d12a8 gcc/config/pa/pa-pro-end.h ! 7005490b5ec2b25bb4fe48c6705673b8 gcc/config/pa/pa-protos.h ! ebc3416d7c77ff7b3d28e3945aff5826 gcc/config/pa/pa.c ! 99e8607e5d9cda159bab573518c7ab1e gcc/config/pa/pa.h ! 002242fc8f70151bb91434f015ee5310 gcc/config/pa/pa.md c17a7721fbfc548f190112cc544e0d7b gcc/config/pa/pa.opt 012a1e54461f76d78cd598a9cb40b3bf gcc/config/pa/pa32-linux.h ! aa71fb9e974c0c0c8b003a41ef915009 gcc/config/pa/pa32-regs.h 43ce51b476aa3150cfe2ee28da998234 gcc/config/pa/pa64-hpux.h 9b1e38a2cb5e56e0ebbb1c06868399dc gcc/config/pa/pa64-hpux.opt 920f9702b9ea8edb3a7a6356990d4e6b gcc/config/pa/pa64-linux.h ! a72b5c6ee7898b3539c3e1106247f99c gcc/config/pa/pa64-regs.h a9a6afd79b827565ffb8de8330b4cfe6 gcc/config/pa/pa64-start.h 0bda28b81f711b8e481df375d7a0dc63 gcc/config/pa/predicates.md 0a463340b1a50c32b330e9e0392a8147 gcc/config/pa/quadlib.c ! 7dd4b4a1e6e1ac332ae3ea17491143f7 gcc/config/pa/som.h f5636be1c6a19b843caa9492b7d07efd gcc/config/pa/stublib.c 504fb8ee781c6f20c7a2b7ecfb8f3554 gcc/config/pa/t-dce-thr da2ee7905442cc7ee74f75effe75a892 gcc/config/pa/t-hpux-shlib --- 2966,2999 ---- eefd6081497d56467864a111613f397b gcc/config/pa/lib2funcs.asm 52aa8211ab4116065e45b378223eddd3 gcc/config/pa/linux-unwind.h c2cc9c83c626de0329e1bfbdec7c6cfb gcc/config/pa/milli64.S ! feac6aba9a4a0c5389d44e887e20875a gcc/config/pa/pa-64.h ! b4877f831d02c39f839ad367e7d0838b gcc/config/pa/pa-hpux.h c648bc371bab81fa1f4acd6c4eb8f0db gcc/config/pa/pa-hpux.opt ! b1cb84a09e0ad8799534deb0e0327280 gcc/config/pa/pa-hpux10.h d452d460c0195601ba6c082db4f4712a gcc/config/pa/pa-hpux1010.h af2a4676245f1f7fd4a5fdea710ab6a6 gcc/config/pa/pa-hpux1010.opt ! 2b0bc28ecb5acd37a78fc58efb03d46f gcc/config/pa/pa-hpux11.h fafe040d7a38b97e371a3c84845e4c5f gcc/config/pa/pa-hpux1111.h 6b7808fef171673f40789b8c0da45349 gcc/config/pa/pa-hpux1111.opt 217a72bceca0c1711fbad3a7a23e4551 gcc/config/pa/pa-linux.h 01b8e14468e166bb285428fdc6a20bd3 gcc/config/pa/pa-modes.def a81e3d2ac855c4207c39f363e23a4767 gcc/config/pa/pa-osf.h c0f1cc0f27d9ce8d0ec3a466f18d12a8 gcc/config/pa/pa-pro-end.h ! 2e85705ec836d1d4da6669268c8f4179 gcc/config/pa/pa-protos.h ! 677e7b97bc75b65d8e20bd15880f6316 gcc/config/pa/pa.c ! f7175812bb72b2fb2c3659ac64112bea gcc/config/pa/pa.h ! d6ab5a8720021ac74f50f3112282e898 gcc/config/pa/pa.md c17a7721fbfc548f190112cc544e0d7b gcc/config/pa/pa.opt 012a1e54461f76d78cd598a9cb40b3bf gcc/config/pa/pa32-linux.h ! bbc969f1a9f67fead333fb501458bcd1 gcc/config/pa/pa32-regs.h 43ce51b476aa3150cfe2ee28da998234 gcc/config/pa/pa64-hpux.h 9b1e38a2cb5e56e0ebbb1c06868399dc gcc/config/pa/pa64-hpux.opt 920f9702b9ea8edb3a7a6356990d4e6b gcc/config/pa/pa64-linux.h ! 6c1fefc48da2bb9099e7cb131d147e8e gcc/config/pa/pa64-regs.h a9a6afd79b827565ffb8de8330b4cfe6 gcc/config/pa/pa64-start.h 0bda28b81f711b8e481df375d7a0dc63 gcc/config/pa/predicates.md 0a463340b1a50c32b330e9e0392a8147 gcc/config/pa/quadlib.c ! f8eefb3db148e0ec5bb2de180bcacc48 gcc/config/pa/som.h f5636be1c6a19b843caa9492b7d07efd gcc/config/pa/stublib.c 504fb8ee781c6f20c7a2b7ecfb8f3554 gcc/config/pa/t-dce-thr da2ee7905442cc7ee74f75effe75a892 gcc/config/pa/t-hpux-shlib *************** a0eab4ecd90b8d75781bc97425670fee gcc/co *** 3061,3067 **** e4bf9c999af85898a03f9872ade1c4e3 gcc/config/rs6000/kaos-ppc.h 1338876bdb72ff4bdb57ab6ad4c39f31 gcc/config/rs6000/libgcc-ppc-glibc.ver 7aa6f4e782960be3e2b43998ef395330 gcc/config/rs6000/libgcc-ppc64.ver ! d39e3badbb09a745faa6186468eac002 gcc/config/rs6000/linux-unwind.h a0d6ee4e2d79f2bd65d0538df57b58ce gcc/config/rs6000/linux.h d41dcfaf5e872e971926da02b11d0827 gcc/config/rs6000/linux64.h 5b8c153b2d5d87288c6e70572df32eba gcc/config/rs6000/linux64.opt --- 3072,3078 ---- e4bf9c999af85898a03f9872ade1c4e3 gcc/config/rs6000/kaos-ppc.h 1338876bdb72ff4bdb57ab6ad4c39f31 gcc/config/rs6000/libgcc-ppc-glibc.ver 7aa6f4e782960be3e2b43998ef395330 gcc/config/rs6000/libgcc-ppc64.ver ! 25195ca81edb343a027fb8bf69f17f0f gcc/config/rs6000/linux-unwind.h a0d6ee4e2d79f2bd65d0538df57b58ce gcc/config/rs6000/linux.h d41dcfaf5e872e971926da02b11d0827 gcc/config/rs6000/linux64.h 5b8c153b2d5d87288c6e70572df32eba gcc/config/rs6000/linux64.opt *************** f9e52339211ae496fea3a7b503e008b0 gcc/co *** 3150,3174 **** ff5707d296f8d84d86bb161fa39ae0b4 gcc/config/s390/tpf.h 249beaf3a96676e58fd434f66c957716 gcc/config/s390/tpf.md be092bb5b940bfb50916a5d306bd6a43 gcc/config/s390/tpf.opt ! 8fd793367df6580533e599c1f0d1e562 gcc/config/score/crti.asm ec50410126c38795e6348a39c1cfc428 gcc/config/score/crtn.asm ! c0129810f7a7d60344a18bca886e36bb gcc/config/score/elf.h ! 51f9dc9ec2c2c7c3c5a2090839efb6cf gcc/config/score/mac.md ! 821ce4e61be33fa9537ec23c4ba12d67 gcc/config/score/misc.md ! e4c6d60e3e9155ebe25490a37fc7c48e gcc/config/score/mul-div.S ! df8f3a300f61ed85f9f2b03698bc71f0 gcc/config/score/predicates.md ! 95745d1af6408a11005bde8e2ebab852 gcc/config/score/score-conv.h ! 6a9f7cef96d2ebb1076629c1d1490e6b gcc/config/score/score-mdaux.c ! a031a70c651342d17f3f22c42b0e51f6 gcc/config/score/score-mdaux.h 8fca7916d119c2032fcdc726235b2d8a gcc/config/score/score-modes.def ! 3ee82d0f1b073d4f6650766b47d6b0e4 gcc/config/score/score-protos.h ! e669ebeef04c20d42624a45aaba0a1ef gcc/config/score/score-version.h ! 8ace294ea0dd6f33f528ddeeeb2be1f1 gcc/config/score/score.c ! e57651cb543ccfdce24bb9b8e9d5c8a7 gcc/config/score/score.h ! 9e80258dc9c3e17ac3475c2b414700a6 gcc/config/score/score.md ! 90fd1ed26020bff42bf35f622689a966 gcc/config/score/score.opt ! dc1866e8c57ba6b922db4ad30b06a94a gcc/config/score/score7.md ! b71a304a6060350544531de9450621f8 gcc/config/score/t-score-elf fd737535bed370fcf59e86b9fc12ec2f gcc/config/sh/coff.h 94639a9bc81af49ca956c9dd51361f31 gcc/config/sh/crt1.asm a69c9b8dbc8a7fc15ed8c56d4271b19e gcc/config/sh/crti.asm --- 3161,3184 ---- ff5707d296f8d84d86bb161fa39ae0b4 gcc/config/s390/tpf.h 249beaf3a96676e58fd434f66c957716 gcc/config/s390/tpf.md be092bb5b940bfb50916a5d306bd6a43 gcc/config/s390/tpf.opt ! 5fab480b67eaf508c6c7d0067f219f9f gcc/config/score/crti.asm ec50410126c38795e6348a39c1cfc428 gcc/config/score/crtn.asm ! c4c4675b2fc1810c6f5c116a7b7ce97b gcc/config/score/elf.h ! 6894d56d512d42e64ba1c6084793bd3a gcc/config/score/mul-div.S ! ebb4a6ade490e173bf32fe757b13b7eb gcc/config/score/predicates.md ! b91325948c6abf538f17c0774033e8a8 gcc/config/score/score-conv.h ! 7a1f3dcfd6dd42a718b018798f0aed77 gcc/config/score/score-generic.md 8fca7916d119c2032fcdc726235b2d8a gcc/config/score/score-modes.def ! 1a541267efef1a8f74945a4033a39b3d gcc/config/score/score-protos.h ! 2d12603511627297a73d575b75dd3e54 gcc/config/score/score.c ! 1817113fe570e4cc8c872623d3963e8f gcc/config/score/score.h ! 1ddfab0671396d7a7f8dfe54f1651830 gcc/config/score/score.md ! 709384cbfe4a2fa8792d194d6ff145d9 gcc/config/score/score.opt ! b8ecd0b34fe537b03d6bb8eb6ac3152f gcc/config/score/score3.c ! a626a27f2020ae33553de2b6be8187d9 gcc/config/score/score3.h ! 56e00e7e137a25da88c2a9b72a75aba6 gcc/config/score/score7.c ! 65cd1e53813f3a4d197fbd42baacc278 gcc/config/score/score7.h ! 32641d49aee70bbb7d983707662650b9 gcc/config/score/t-score-elf fd737535bed370fcf59e86b9fc12ec2f gcc/config/sh/coff.h 94639a9bc81af49ca956c9dd51361f31 gcc/config/sh/crt1.asm a69c9b8dbc8a7fc15ed8c56d4271b19e gcc/config/sh/crti.asm *************** ed2c03e911ff55520e06b22d18f27b2b gcc/co *** 3465,3472 **** 0c49731d95e228dbbfcb9d1eaf2777c3 gcc/config/xtensa/t-linux 983bb5eba8c08d163d416681540fd896 gcc/config/xtensa/t-xtensa 2987032035986548bdd79cd71334262d gcc/config/xtensa/xtensa-protos.h ! 268e28c617792fa966f8abcba92b043a gcc/config/xtensa/xtensa.c ! f976679ce0446705fe3b052c4cd4480e gcc/config/xtensa/xtensa.h 058a81f6c3aea294a8f8bdb57aaf9c20 gcc/config/xtensa/xtensa.md 251bc8bed847c25c9a8dc6fda95d358e gcc/config/xtensa/xtensa.opt f52033b9b24d005d9fcd20353269de69 gcc/configure --- 3475,3482 ---- 0c49731d95e228dbbfcb9d1eaf2777c3 gcc/config/xtensa/t-linux 983bb5eba8c08d163d416681540fd896 gcc/config/xtensa/t-xtensa 2987032035986548bdd79cd71334262d gcc/config/xtensa/xtensa-protos.h ! bef9428d9f40092e4793410610dad475 gcc/config/xtensa/xtensa.c ! a3ae5f9d88f409d3ebb47a2d2a642438 gcc/config/xtensa/xtensa.h 058a81f6c3aea294a8f8bdb57aaf9c20 gcc/config/xtensa/xtensa.md 251bc8bed847c25c9a8dc6fda95d358e gcc/config/xtensa/xtensa.opt f52033b9b24d005d9fcd20353269de69 gcc/configure *************** ad9a4a9f779ce78f7a8b5c44e75460ba gcc/co *** 3477,3483 **** 2b8d458570138701d894bd7d582c8121 gcc/coretypes.h 102303053b83fa43400ade985599af22 gcc/coverage.c 837f358341b0c8f32e120aa51fe433aa gcc/coverage.h ! 52a3605e06c16f3866eb23e10a782efb gcc/cp/ChangeLog bd4aeac90a5befe0218090fe3d3d6542 gcc/cp/ChangeLog-1993 08674355375d2734400e90d47d048ccc gcc/cp/ChangeLog-1994 ba73c2557bcf66206e3cb4f90a4f81a1 gcc/cp/ChangeLog-1995 --- 3487,3493 ---- 2b8d458570138701d894bd7d582c8121 gcc/coretypes.h 102303053b83fa43400ade985599af22 gcc/coverage.c 837f358341b0c8f32e120aa51fe433aa gcc/coverage.h ! acc43bf89f2bf72367a2adfa133d838f gcc/cp/ChangeLog bd4aeac90a5befe0218090fe3d3d6542 gcc/cp/ChangeLog-1993 08674355375d2734400e90d47d048ccc gcc/cp/ChangeLog-1994 ba73c2557bcf66206e3cb4f90a4f81a1 gcc/cp/ChangeLog-1995 *************** cd053832db241cc208a442bf688c6bae gcc/cp *** 3493,3502 **** df30dd47773ff2170eb33bdbb02a384e gcc/cp/ChangeLog.tree-ssa f5ca50cb75c35f8ad13871678db00e7a gcc/cp/Make-lang.in 722817c6da9fa9d73d9f114ae094ed4f gcc/cp/NEWS ! 76e819bcb2333e61178a731ab1ca5e28 gcc/cp/call.c 9f7a823f536eacdd59e2fc31ef4da831 gcc/cp/cfns.gperf 5cf817bda5279d277269588c836977b3 gcc/cp/cfns.h ! 30bc563ca61caa63e6c6eb2c164054a7 gcc/cp/class.c 7c8aed891facdeabc51625d3fae43390 gcc/cp/config-lang.in ec24859eeaa664762832b72863e41c5c gcc/cp/cp-gimplify.c 42f4d69e6a7cb2405d40b8000bd32d23 gcc/cp/cp-lang.c --- 3503,3512 ---- df30dd47773ff2170eb33bdbb02a384e gcc/cp/ChangeLog.tree-ssa f5ca50cb75c35f8ad13871678db00e7a gcc/cp/Make-lang.in 722817c6da9fa9d73d9f114ae094ed4f gcc/cp/NEWS ! 82b55321e651fa7a8a55d466303a6f50 gcc/cp/call.c 9f7a823f536eacdd59e2fc31ef4da831 gcc/cp/cfns.gperf 5cf817bda5279d277269588c836977b3 gcc/cp/cfns.h ! 1c1ac7548d7ab53273d8c9d372b9b064 gcc/cp/class.c 7c8aed891facdeabc51625d3fae43390 gcc/cp/config-lang.in ec24859eeaa664762832b72863e41c5c gcc/cp/cp-gimplify.c 42f4d69e6a7cb2405d40b8000bd32d23 gcc/cp/cp-lang.c *************** a08719b73994ba139a75cc53c3df29cc gcc/cp *** 3505,3517 **** 31a5455362fb929835a322c445764029 gcc/cp/cp-tree.def 5792d663126d3cd0adb64667b83e164d gcc/cp/cp-tree.h 922b27c48e847864b6e2a47e928a906c gcc/cp/cvt.c ! 3bde4d5611269af01dba53323117e45e gcc/cp/cxx-pretty-print.c ! f7c1c009d094ae2bf65af9b4341b9827 gcc/cp/cxx-pretty-print.h ! 2d5a5de891feaeac2d74acbbfaff18af gcc/cp/decl.c 728e54789136185f784710b266d2ad2c gcc/cp/decl.h 270a9f35a1ff645a0407d4ffd13d51c0 gcc/cp/decl2.c 7e27b4d053dc2aa31cf11969f4c73af7 gcc/cp/dump.c ! 0d33934b7a91d57839592f89bebc3b3a gcc/cp/error.c 2c3b6ade41b4a93d603c3feae508c19b gcc/cp/except.c 849b4509b6355a052bdeadf2a9071bb3 gcc/cp/expr.c 68e9144ee6fa6fb1d969aa5c37740686 gcc/cp/friend.c --- 3515,3527 ---- 31a5455362fb929835a322c445764029 gcc/cp/cp-tree.def 5792d663126d3cd0adb64667b83e164d gcc/cp/cp-tree.h 922b27c48e847864b6e2a47e928a906c gcc/cp/cvt.c ! 91a739d531c1bec6ff780e8654a6ba7f gcc/cp/cxx-pretty-print.c ! f7d7f01ec17cd9c2860e48582e01562f gcc/cp/cxx-pretty-print.h ! 428b602e320621ea719cf9f460e184fa gcc/cp/decl.c 728e54789136185f784710b266d2ad2c gcc/cp/decl.h 270a9f35a1ff645a0407d4ffd13d51c0 gcc/cp/decl2.c 7e27b4d053dc2aa31cf11969f4c73af7 gcc/cp/dump.c ! c0015863d42509b3d8f822d885c21c1c gcc/cp/error.c 2c3b6ade41b4a93d603c3feae508c19b gcc/cp/except.c 849b4509b6355a052bdeadf2a9071bb3 gcc/cp/expr.c 68e9144ee6fa6fb1d969aa5c37740686 gcc/cp/friend.c *************** f7c1c009d094ae2bf65af9b4341b9827 gcc/cp *** 3521,3545 **** db351e219e7f0551df84e3cb0d2f9574 gcc/cp/lex.c 25e87ce6e3a3bf9317a3ce30007ddfe3 gcc/cp/mangle.c 695c127fa6bc9f2fbe6c1ae551b1d7dc gcc/cp/method.c ! 8701ccbc43208c0518752b546ddd6739 gcc/cp/name-lookup.c ! 8a1bb9ab3967e3724fc8695485b5d0a5 gcc/cp/name-lookup.h 01adceacc7eb5d2cb288c197b6f324f3 gcc/cp/operators.def 65c13cec58a02a7ea36aadd54289a144 gcc/cp/optimize.c ! 3ef3cbc15a368340e61f905b1c8ed899 gcc/cp/parser.c ! df11957fb21cee845335ba237bd52b90 gcc/cp/pt.c a93f3e25e9cd01d1114798cd81240ac8 gcc/cp/ptree.c a36ff4be202979e5a882790c1d8afce6 gcc/cp/repo.c f9ab9e782c773d158c8547ac26b56118 gcc/cp/rtti.c a089f723a9070a5a7db0ead1d788482d gcc/cp/search.c 995ce354c93d094c759d158752594a02 gcc/cp/semantics.c c4b26660d51becbec6235018528f10c4 gcc/cp/tree.c ! 41868925a41899d36984caae471ce2ed gcc/cp/typeck.c 6459047a268824324386392cbaae1ef1 gcc/cp/typeck2.c 64da48e50a2e31ba217b49357f2ec9c2 gcc/cppdefault.c 11a2c0e70231b23b97dc21cf5ba8d083 gcc/cppdefault.h 8336cf156ec6050dfe9a10ab7a467a9c gcc/cppspec.c f6bc4281ae72764a3a93ded7290024e2 gcc/crtstuff.c ! 5a3d91ef07e2cf0def1ea405c9e67b6f gcc/cse.c 986e8178e9e25a7a5219e184088e386d gcc/cselib.c e9b2b0fe649752b0f9022444aafd0f9d gcc/cselib.h 1ded054093de910d9786c62bc4fe8cc6 gcc/cstamp-h.in --- 3531,3555 ---- db351e219e7f0551df84e3cb0d2f9574 gcc/cp/lex.c 25e87ce6e3a3bf9317a3ce30007ddfe3 gcc/cp/mangle.c 695c127fa6bc9f2fbe6c1ae551b1d7dc gcc/cp/method.c ! a3ca8e8a27eeff8fba8010e0fa2a9f7a gcc/cp/name-lookup.c ! 4d4687857762aecdbaf42bb8e9164190 gcc/cp/name-lookup.h 01adceacc7eb5d2cb288c197b6f324f3 gcc/cp/operators.def 65c13cec58a02a7ea36aadd54289a144 gcc/cp/optimize.c ! 17846794a8213ba335f4ac89a3bb4357 gcc/cp/parser.c ! 65a6d7e59a323dddf0e7cf6bb1d1478b gcc/cp/pt.c a93f3e25e9cd01d1114798cd81240ac8 gcc/cp/ptree.c a36ff4be202979e5a882790c1d8afce6 gcc/cp/repo.c f9ab9e782c773d158c8547ac26b56118 gcc/cp/rtti.c a089f723a9070a5a7db0ead1d788482d gcc/cp/search.c 995ce354c93d094c759d158752594a02 gcc/cp/semantics.c c4b26660d51becbec6235018528f10c4 gcc/cp/tree.c ! c0406c25aadfdddf4519640ced392775 gcc/cp/typeck.c 6459047a268824324386392cbaae1ef1 gcc/cp/typeck2.c 64da48e50a2e31ba217b49357f2ec9c2 gcc/cppdefault.c 11a2c0e70231b23b97dc21cf5ba8d083 gcc/cppdefault.h 8336cf156ec6050dfe9a10ab7a467a9c gcc/cppspec.c f6bc4281ae72764a3a93ded7290024e2 gcc/crtstuff.c ! 56111201f2e871626898ce78bca171b1 gcc/cse.c 986e8178e9e25a7a5219e184088e386d gcc/cselib.c e9b2b0fe649752b0f9022444aafd0f9d gcc/cselib.h 1ded054093de910d9786c62bc4fe8cc6 gcc/cstamp-h.in *************** b71dd04e05b9b1f8af0b0d47e0c5736d gcc/de *** 3552,3558 **** 35312233067ac28d4ce48c197a550fd7 gcc/defaults.h 75b5263c4d18f83c74901201b089bf08 gcc/df-core.c 10300d2ec6d153dc3b03f6621ad93ee0 gcc/df-problems.c ! d8c667265e01065b73c867175e83fe63 gcc/df-scan.c 36f0d9580452732a528cd07c9b4eb236 gcc/df.h 6edc812517ef31f9278dd387a6bef9d2 gcc/dfp.c ac9ceda1d42fb9720d3cf1ebedde4716 gcc/dfp.h --- 3562,3568 ---- 35312233067ac28d4ce48c197a550fd7 gcc/defaults.h 75b5263c4d18f83c74901201b089bf08 gcc/df-core.c 10300d2ec6d153dc3b03f6621ad93ee0 gcc/df-problems.c ! 4d0052419f7cc4666f6ad3b987b4a79f gcc/df-scan.c 36f0d9580452732a528cd07c9b4eb236 gcc/df.h 6edc812517ef31f9278dd387a6bef9d2 gcc/dfp.c ac9ceda1d42fb9720d3cf1ebedde4716 gcc/dfp.h *************** ede23db52c73d2fda739a3d4cedfd465 gcc/do *** 3568,3605 **** 73b7f9aa052dde14853d1817153dfd24 gcc/doc/configterms.texi 9857c78ed214089bcdecbe1a7d47b723 gcc/doc/contrib.texi 532efd24ba5590c6aed6cc4fa92638d8 gcc/doc/contribute.texi ! 709b68cc9ef0165f3cb09615227fcf73 gcc/doc/cpp.1 ! 428121bb87b0efa1bc47c8fa356608d1 gcc/doc/cpp.info cbc6be853dc401fe1dd4fdd28079abcf gcc/doc/cpp.texi 8462a717da44ca316c8c9ac975457a32 gcc/doc/cppenv.texi ! a3afbb49a6a1be49384b790c089c4bd9 gcc/doc/cppinternals.info 2256b44c22f96b6bdaa3dbdf1a6916e7 gcc/doc/cppinternals.texi be5487defb69ea8435a0e8e09a857424 gcc/doc/cppopts.texi ! a54af3c91292bbd50e93129d6f490c5f gcc/doc/extend.texi 217f881d5138ae57b1df76f41cf3f22b gcc/doc/fragments.texi b0318dd829535c6d2e012cb04c0144bb gcc/doc/frontends.texi ! d182b9d97af4ee2e0b978d001dd68dbe gcc/doc/fsf-funding.7 ! ad9db52aee02901fc8c24e487d135bd0 gcc/doc/g++.1 ! ad9db52aee02901fc8c24e487d135bd0 gcc/doc/gcc.1 ! 2d64c7c49510b057f83bd15eeeffc7e4 gcc/doc/gcc.info d2c734f3b4c929d4f677d1f872822a2b gcc/doc/gcc.texi ! 5ee51e0a67afcf3a2709e976f293e491 gcc/doc/gccinstall.info ! c4abd25478424c0126fcb755a67ef560 gcc/doc/gccint.info 475386803c9221e724714638dcd2920b gcc/doc/gccint.texi ! 92de7887cbdeed48b7486087d1b9c3fd gcc/doc/gcj-dbtool.1 ! c7e2ad53223b38a4a3c25f975f4705f3 gcc/doc/gcj.1 ! 27310b80e68a78de9bbe1b513a9d1135 gcc/doc/gcj.info ! 4ba6c072ccca99fbb057b603573134c8 gcc/doc/gcjh.1 ! e3c341cf0d6dbee088c3d003d39b841a gcc/doc/gcov.1 e622c53d6a4ac7ef73beac35b69c7764 gcc/doc/gcov.texi ! ffb7063043b672d317ed3ed606195387 gcc/doc/gfdl.7 ! 02d2791b20bcc3751828af4ae0d8e9b4 gcc/doc/gfortran.1 ! 268d7e853aac90130aebc3045e7fdbdb gcc/doc/gij.1 ! 92a078fa21964bd35e355a0491510e02 gcc/doc/gjnih.1 290370669f02bef1502ada9273e5261f gcc/doc/gnu.texi ! 51b7911a898f235b6a47e7a5bf4edcb5 gcc/doc/gpl.7 ! a16a8db92de62cdf6a0db8ab51a60c7e gcc/doc/grmic.1 ! 997ec040f176bf3710dbe0150e39c651 gcc/doc/grmiregistry.1 34c6068d2011a627de76d1dc46b17017 gcc/doc/gty.texi 12712ad63a56e9d549562b21b42b1454 gcc/doc/headerdirs.texi f9a96e5b17478ac8e83051e30d4d0245 gcc/doc/hostconfig.texi --- 3578,3614 ---- 73b7f9aa052dde14853d1817153dfd24 gcc/doc/configterms.texi 9857c78ed214089bcdecbe1a7d47b723 gcc/doc/contrib.texi 532efd24ba5590c6aed6cc4fa92638d8 gcc/doc/contribute.texi ! 6d5b55e661b1b8bda5ea0694c4dc489f gcc/doc/cpp.1 ! f1623c0c74b5cb11797f608274840be1 gcc/doc/cpp.info cbc6be853dc401fe1dd4fdd28079abcf gcc/doc/cpp.texi 8462a717da44ca316c8c9ac975457a32 gcc/doc/cppenv.texi ! 026336885c3d00c3e296b0c06251ff46 gcc/doc/cppinternals.info 2256b44c22f96b6bdaa3dbdf1a6916e7 gcc/doc/cppinternals.texi be5487defb69ea8435a0e8e09a857424 gcc/doc/cppopts.texi ! a22aed9f9b351c833d3980875e859cc9 gcc/doc/extend.texi 217f881d5138ae57b1df76f41cf3f22b gcc/doc/fragments.texi b0318dd829535c6d2e012cb04c0144bb gcc/doc/frontends.texi ! 1c35f23babb924aa13ae456f87c7d4ce gcc/doc/fsf-funding.7 ! 3f8c7a49df280e2f825577dac35e9f9c gcc/doc/g++.1 ! 3f8c7a49df280e2f825577dac35e9f9c gcc/doc/gcc.1 ! 51b631d968b5d97535595974f1305a02 gcc/doc/gcc.info d2c734f3b4c929d4f677d1f872822a2b gcc/doc/gcc.texi ! a283a7b158ad7e9dad858cce5b8a25eb gcc/doc/gccinstall.info ! 9d080ff19a5b4c1dbd438c1931a491b9 gcc/doc/gccint.info 475386803c9221e724714638dcd2920b gcc/doc/gccint.texi ! 0e49b73a2c1c975fc1318df9555a4e50 gcc/doc/gcj-dbtool.1 ! 7e27019019325687df5b35e167cdc2a6 gcc/doc/gcj.1 ! 1757899884c6cce61b4182463808d8fd gcc/doc/gcj.info ! c1beb9bf1dabcbdb22f0c527969a7977 gcc/doc/gcjh.1 ! fc48179f2e8905c40d0d13377fd3d59a gcc/doc/gcov.1 e622c53d6a4ac7ef73beac35b69c7764 gcc/doc/gcov.texi ! 6ad4f80c3a063e57aeac40c1dc646dcc gcc/doc/gfdl.7 ! 48f6c78a0b30c2ed555e2d313379b821 gcc/doc/gij.1 ! 28a1eaccf029e00273b7331f40dd8249 gcc/doc/gjnih.1 290370669f02bef1502ada9273e5261f gcc/doc/gnu.texi ! 8b50e2ccfc4d9839c17c47b3bc0c06a6 gcc/doc/gpl.7 ! 8b979f0c428eddb64032c0f4690a9161 gcc/doc/grmic.1 ! 19f8546127dfe4370fcda4cd281c0975 gcc/doc/grmiregistry.1 34c6068d2011a627de76d1dc46b17017 gcc/doc/gty.texi 12712ad63a56e9d549562b21b42b1454 gcc/doc/headerdirs.texi f9a96e5b17478ac8e83051e30d4d0245 gcc/doc/hostconfig.texi *************** b5123edff0a56625ffa9b55deb3718db gcc/do *** 3611,3622 **** 9b944bdd1febe1cdf64a5f66d31bd3c9 gcc/doc/include/texinfo.tex 86355f77ae147b0b5ac0b6127c8259f8 gcc/doc/install-old.texi 1a82358ed7dae91539691a1af67f8514 gcc/doc/install.texi ! 1162ed64135d69ec08d395465dfbabe6 gcc/doc/install.texi2html 5407c66b804884426ce94dcac22864d1 gcc/doc/interface.texi ! ab57eff3d2dd242360220b72a508fffe gcc/doc/invoke.texi ! 2c16cef76ab8aeea60b01a7de736e684 gcc/doc/jcf-dump.1 ! 01f09ed11e703392a6c91d70d8eb7f0e gcc/doc/jv-convert.1 ! 7650b709146ed04ff8ed39a2b90c3f38 gcc/doc/jv-scan.1 a01aca1d7da7f482653b521ba6447f85 gcc/doc/languages.texi 94d3193a8b450e3924b75f70cbd3d15a gcc/doc/libgcc.texi 8bfb3c328f6864b21dea9f1be1a1dba1 gcc/doc/loop.texi --- 3620,3631 ---- 9b944bdd1febe1cdf64a5f66d31bd3c9 gcc/doc/include/texinfo.tex 86355f77ae147b0b5ac0b6127c8259f8 gcc/doc/install-old.texi 1a82358ed7dae91539691a1af67f8514 gcc/doc/install.texi ! e972d32b01cd5ea63aa42d394ac78395 gcc/doc/install.texi2html 5407c66b804884426ce94dcac22864d1 gcc/doc/interface.texi ! fdf342753d8d7b4c51375d1623ea1d5a gcc/doc/invoke.texi ! efd42061e3a0605afa005262a477978c gcc/doc/jcf-dump.1 ! 9d9136bf90e103a2bf1c4485e7452193 gcc/doc/jv-convert.1 ! 527c636681226948251b419608d913da gcc/doc/jv-scan.1 a01aca1d7da7f482653b521ba6447f85 gcc/doc/languages.texi 94d3193a8b450e3924b75f70cbd3d15a gcc/doc/libgcc.texi 8bfb3c328f6864b21dea9f1be1a1dba1 gcc/doc/loop.texi *************** b7b91eb62a2d1571dbbd93f52d1d2f2f gcc/do *** 3626,3636 **** 85f8b02236f60f8ad69fae27fe728387 gcc/doc/options.texi 8ecdc751017c0e983d211239c000a69e gcc/doc/passes.texi 72136dc6e58c1bb1790f0f25bbaf8897 gcc/doc/portability.texi ! 7efefc3919f60a15e7cfbbd7a780da8e gcc/doc/rtl.texi d57122b80f1dd7815e0cf707c38d0170 gcc/doc/service.texi dba33abe7502e73947104d60b83c8a82 gcc/doc/sourcebuild.texi 66fac86cbf26f84a3d2b3a56a1ad5237 gcc/doc/standards.texi ! c1201a64baf08a5314c67fa137c9bc19 gcc/doc/tm.texi 020d10a66d88db4028207eaf3b768ea1 gcc/doc/tree-ssa.texi 0436252d52c0ee2481d0c8855f6b6505 gcc/doc/trouble.texi 5e63fd82090d1809d58c203b3e6408ee gcc/dojump.c --- 3635,3645 ---- 85f8b02236f60f8ad69fae27fe728387 gcc/doc/options.texi 8ecdc751017c0e983d211239c000a69e gcc/doc/passes.texi 72136dc6e58c1bb1790f0f25bbaf8897 gcc/doc/portability.texi ! 6e93442b76989e5ba80dc6411909e640 gcc/doc/rtl.texi d57122b80f1dd7815e0cf707c38d0170 gcc/doc/service.texi dba33abe7502e73947104d60b83c8a82 gcc/doc/sourcebuild.texi 66fac86cbf26f84a3d2b3a56a1ad5237 gcc/doc/standards.texi ! 1199a5a00585757a3755e78189262c4d gcc/doc/tm.texi 020d10a66d88db4028207eaf3b768ea1 gcc/doc/tree-ssa.texi 0436252d52c0ee2481d0c8855f6b6505 gcc/doc/trouble.texi 5e63fd82090d1809d58c203b3e6408ee gcc/dojump.c *************** c1201a64baf08a5314c67fa137c9bc19 gcc/do *** 3644,3650 **** cad19c5cb5454be317610ee35fb8cbd2 gcc/dwarf2.h 9064f68ca2351c31353d3126c6d62f64 gcc/dwarf2asm.c 12623788973040394670a1e63f06da0c gcc/dwarf2asm.h ! d72ce701b4b9b6a30e0fb559e115499f gcc/dwarf2out.c 8c6fb78bd7e6ae9abfd537da81095407 gcc/dwarf2out.h bcbd7ccf5266d57efc4344be4bbdbe76 gcc/emit-rtl.c e6fb11c03b1729374ef7151184f01619 gcc/emit-rtl.h --- 3653,3659 ---- cad19c5cb5454be317610ee35fb8cbd2 gcc/dwarf2.h 9064f68ca2351c31353d3126c6d62f64 gcc/dwarf2asm.c 12623788973040394670a1e63f06da0c gcc/dwarf2asm.h ! c0646eb334934340a74476fad85a6c45 gcc/dwarf2out.c 8c6fb78bd7e6ae9abfd537da81095407 gcc/dwarf2out.h bcbd7ccf5266d57efc4344be4bbdbe76 gcc/emit-rtl.c e6fb11c03b1729374ef7151184f01619 gcc/emit-rtl.h *************** b791bcc5591c43b1d412ff4477f21c33 gcc/et *** 3657,3671 **** 3272f2c2a9da3cdbfb574acff06d14f8 gcc/except.h deb8c51a50bb70ca3d47d40fd6800b6b gcc/explow.c 61ba0aab775b882f7f1ba6ec9767ebf8 gcc/expmed.c ! f303d32a8d6c0e32433b9e2a8a355c9d gcc/expr.c fa8bc55126adc104027e69e7190caa1e gcc/expr.h 4779c96407d2ea94260874e60f83cdff gcc/final.c 2df372b895b6e2aa483288c7d61f8ce3 gcc/fix-header.c 6e91d9edba224d5114b9d4cc242f0fab gcc/fixproto ! eb81349e947ad9dc45096f3ea2191029 gcc/flags.h 6b7b5855e4b02f10a0064337d9dcf3b8 gcc/flow.c ! 8c0428640b3714838e664d4ead267695 gcc/fold-const.c ! 4a3864858337e4fba3f8db7d919c3218 gcc/fortran/ChangeLog a7663343404e5c8cd4fe22f4e5f8039b gcc/fortran/ChangeLog-2002 aaf400b0b954b39bafbe84581b01c429 gcc/fortran/ChangeLog-2003 83b581736c856dc0853389ea0c7cb007 gcc/fortran/ChangeLog-2004 --- 3666,3680 ---- 3272f2c2a9da3cdbfb574acff06d14f8 gcc/except.h deb8c51a50bb70ca3d47d40fd6800b6b gcc/explow.c 61ba0aab775b882f7f1ba6ec9767ebf8 gcc/expmed.c ! d45b5d1828fea3066c5b932f2a7b0321 gcc/expr.c fa8bc55126adc104027e69e7190caa1e gcc/expr.h 4779c96407d2ea94260874e60f83cdff gcc/final.c 2df372b895b6e2aa483288c7d61f8ce3 gcc/fix-header.c 6e91d9edba224d5114b9d4cc242f0fab gcc/fixproto ! 4884331af448707ebda6e4ae6a1510f4 gcc/flags.h 6b7b5855e4b02f10a0064337d9dcf3b8 gcc/flow.c ! 4916428cd705a39cfe7ddf84b51126af gcc/fold-const.c ! 34deb38afd85635e0d4bb6aabe446e00 gcc/fortran/ChangeLog a7663343404e5c8cd4fe22f4e5f8039b gcc/fortran/ChangeLog-2002 aaf400b0b954b39bafbe84581b01c429 gcc/fortran/ChangeLog-2003 83b581736c856dc0853389ea0c7cb007 gcc/fortran/ChangeLog-2004 *************** ca25cae8843a637e27fc1efc03b8fef3 gcc/fo *** 3687,3693 **** bb619c766947e0a7fc8060a57fb10add gcc/fortran/expr.c b2e31d3b73576e38cc0a56bd9f19e1de gcc/fortran/f95-lang.c 58dd6c8323a858eb51b306faed9612e4 gcc/fortran/gfortran.h - 7663a107422e9c01a8b648481a37aad5 gcc/fortran/gfortran.info e0990a0c09420bd6ae560075331e7c9a gcc/fortran/gfortran.texi 98bf0daedf53d5cc40e7c2089a52d6a6 gcc/fortran/gfortranspec.c 2cb1ef5ffea5bac62c52bb2d4b4f50b5 gcc/fortran/interface.c --- 3696,3701 ---- *************** fba73a1c888edf17d4e46c1e0e5fd8e5 gcc/fo *** 3723,3729 **** fed85a05c974ef6cae34560f97123a90 gcc/fortran/trans-const.h a8823f14da08500143633d3e78dbbd23 gcc/fortran/trans-decl.c c766afd08405d1bb91033219e8cb5a27 gcc/fortran/trans-expr.c ! 4e26da7cd06b2a0b7c2f484fcf383894 gcc/fortran/trans-intrinsic.c f8b7b8f36409b389bd1aacb691b69a80 gcc/fortran/trans-io.c 1916d076c5f4dc1293e503d3eec73bc5 gcc/fortran/trans-openmp.c 73ba9a2e1f71464df6aada618075599c gcc/fortran/trans-stmt.c --- 3731,3737 ---- fed85a05c974ef6cae34560f97123a90 gcc/fortran/trans-const.h a8823f14da08500143633d3e78dbbd23 gcc/fortran/trans-decl.c c766afd08405d1bb91033219e8cb5a27 gcc/fortran/trans-expr.c ! c8e7eca22518f9f75064a694226509e2 gcc/fortran/trans-intrinsic.c f8b7b8f36409b389bd1aacb691b69a80 gcc/fortran/trans-io.c 1916d076c5f4dc1293e503d3eec73bc5 gcc/fortran/trans-openmp.c 73ba9a2e1f71464df6aada618075599c gcc/fortran/trans-stmt.c *************** cc95f29129034395fb7ab2de8553fc48 gcc/ge *** 3762,3771 **** a504c0e6b9775455bc08734178436152 gcc/genextract.c e916713c67d4bd0ee15de2e23d625b1a gcc/genflags.c 2f040b7eb179e8fa2e8ef30656e60f03 gcc/gengenrtl.c ! a85d31f1ab60b42214cfaf9c9fe40659 gcc/gengtype-lex.c 67f888500fe73b5704073b4e876a6ae4 gcc/gengtype-lex.l ! a0624ae5dd68d1b2c076ddb6337ff2be gcc/gengtype-yacc.c ! dc8282bbdb8de525e408eefb30f7b069 gcc/gengtype-yacc.h a20fb29a30faeaef067d811b79e67666 gcc/gengtype-yacc.y 3cba1bc4fd8429b37879f7c05fc27e8e gcc/gengtype.c 78910da08fd3cb67199c647879202694 gcc/gengtype.h --- 3770,3779 ---- a504c0e6b9775455bc08734178436152 gcc/genextract.c e916713c67d4bd0ee15de2e23d625b1a gcc/genflags.c 2f040b7eb179e8fa2e8ef30656e60f03 gcc/gengenrtl.c ! c29fb4a75dcf062eed387a5bc1cf207b gcc/gengtype-lex.c 67f888500fe73b5704073b4e876a6ae4 gcc/gengtype-lex.l ! 1e5d721749347a19b6a9994cae316c1e gcc/gengtype-yacc.c ! cdcd49da243520ba661261c5ddf185e5 gcc/gengtype-yacc.h a20fb29a30faeaef067d811b79e67666 gcc/gengtype-yacc.y 3cba1bc4fd8429b37879f7c05fc27e8e gcc/gengtype.c 78910da08fd3cb67199c647879202694 gcc/gengtype.h *************** e96e65653e0042e015e4adb5040a1c49 gcc/gt *** 3824,3830 **** f11c5e848450fadda50fac2c6aeec00a gcc/hosthooks-def.h a31a1f832beee0163b6a3c429b0c0c9c gcc/hosthooks.h b006d6f3b12aee15b5728fa15cb0014e gcc/hwint.h ! 798b4f63ff8c87c34358946e68f470cc gcc/ifcvt.c efcd5fc5a33c16e53d40956708382775 gcc/input.h dfb133ecdcbc0c3e28c82cf0b5762954 gcc/insn-addr.h 24bfa9a5002b1054febdb16f8950b693 gcc/insn-notes.def --- 3832,3838 ---- f11c5e848450fadda50fac2c6aeec00a gcc/hosthooks-def.h a31a1f832beee0163b6a3c429b0c0c9c gcc/hosthooks.h b006d6f3b12aee15b5728fa15cb0014e gcc/hwint.h ! 4b39d56b154e9e64538a399558ed92c3 gcc/ifcvt.c efcd5fc5a33c16e53d40956708382775 gcc/input.h dfb133ecdcbc0c3e28c82cf0b5762954 gcc/insn-addr.h 24bfa9a5002b1054febdb16f8950b693 gcc/insn-notes.def *************** ae608d3ad6fb1699c0225bdab8f41c09 gcc/in *** 3836,3850 **** 47b8f544d22485d8fc6e91049e9571d5 gcc/ipa-inline.c e871bc2d8f99871a8eac3e3e36e3c294 gcc/ipa-prop.c 6a0b050b9591e8dfeb6a72ccef9384fd gcc/ipa-prop.h ! ffed106a1068160b09e3add06a31d776 gcc/ipa-pure-const.c 80c8e68261891f2e85e093830c5d0447 gcc/ipa-reference.c cff9b112acbaa59b4c325fb101097a0b gcc/ipa-reference.h 948e67c84a1bcaa47fe321184a806a3b gcc/ipa-type-escape.c 87e8d1ef59ee4ea447c9ff53fbcc8e2f gcc/ipa-type-escape.h ! 74290107667ada435988f4d5e8f6c9b6 gcc/ipa-utils.c 0a560ed855154305631effc8e1132ac0 gcc/ipa-utils.h b9d3caa111bbee8bb5b62950f2318e65 gcc/ipa.c ! 5522e29f38da70564f6d4b8a8211a779 gcc/java/ChangeLog 5daac56e6d929be638ed287da3720f51 gcc/java/ChangeLog.tree-ssa ce5cf5bd30896ab97d0efd12a7fa8ed0 gcc/java/Make-lang.in c49035c21a3b9e912fd5738f9c52270c gcc/java/boehm.c --- 3844,3858 ---- 47b8f544d22485d8fc6e91049e9571d5 gcc/ipa-inline.c e871bc2d8f99871a8eac3e3e36e3c294 gcc/ipa-prop.c 6a0b050b9591e8dfeb6a72ccef9384fd gcc/ipa-prop.h ! f9d3fac42ec04a2ebd381075bac65c6f gcc/ipa-pure-const.c 80c8e68261891f2e85e093830c5d0447 gcc/ipa-reference.c cff9b112acbaa59b4c325fb101097a0b gcc/ipa-reference.h 948e67c84a1bcaa47fe321184a806a3b gcc/ipa-type-escape.c 87e8d1ef59ee4ea447c9ff53fbcc8e2f gcc/ipa-type-escape.h ! f93a834c932bc07a662916c68007c6ad gcc/ipa-utils.c 0a560ed855154305631effc8e1132ac0 gcc/ipa-utils.h b9d3caa111bbee8bb5b62950f2318e65 gcc/ipa.c ! 2a35826dea00d68fb414156024cfd4d6 gcc/java/ChangeLog 5daac56e6d929be638ed287da3720f51 gcc/java/ChangeLog.tree-ssa ce5cf5bd30896ab97d0efd12a7fa8ed0 gcc/java/Make-lang.in c49035c21a3b9e912fd5738f9c52270c gcc/java/boehm.c *************** e49b868f3fdee716c94cef954336d19d gcc/ja *** 3891,3897 **** 0751a49281d91ad1b2564c188871490d gcc/java/mangle.c b0805f3c9a4b058552106d347622f464 gcc/java/mangle_name.c e04b5f4b69a05131c366dade007182cc gcc/java/parse-scan.y ! 210e111a87ccda6aba421c6745ef8e52 gcc/java/parse.c e1108e20b775a165ff8e40cb38ad27bd gcc/java/parse.h a91f6d53f966d5aa2aaced1b7e3b2239 gcc/java/parse.y 58a9907634ce73db7508dc565328bf80 gcc/java/resource.c --- 3899,3905 ---- 0751a49281d91ad1b2564c188871490d gcc/java/mangle.c b0805f3c9a4b058552106d347622f464 gcc/java/mangle_name.c e04b5f4b69a05131c366dade007182cc gcc/java/parse-scan.y ! bf66cc79d9c6a030f7b77fa4bbcff845 gcc/java/parse.c e1108e20b775a165ff8e40cb38ad27bd gcc/java/parse.h a91f6d53f966d5aa2aaced1b7e3b2239 gcc/java/parse.y 58a9907634ce73db7508dc565328bf80 gcc/java/resource.c *************** af2dcd3fb8d615cbfd27e3e8b86c7c94 gcc/mi *** 3940,3946 **** 73c2f788be90880f320b5961df41aab1 gcc/mode-classes.def f83eacbf09f2401e9c15b76c5e43d652 gcc/mode-switching.c e02964e349aefe59e752510c396a7853 gcc/modulo-sched.c ! 8b5d5c662c1a942441cdaceebeef1388 gcc/objc/ChangeLog 55692b17b3d7d7442f7be5648f7ed2ba gcc/objc/Make-lang.in aa5319dd541cdb0eb8622f9adf66b761 gcc/objc/README a5357fd1d3ec609df43d565aef4721ab gcc/objc/config-lang.in --- 3948,3954 ---- 73c2f788be90880f320b5961df41aab1 gcc/mode-classes.def f83eacbf09f2401e9c15b76c5e43d652 gcc/mode-switching.c e02964e349aefe59e752510c396a7853 gcc/modulo-sched.c ! bc3f7c6262dc4aac737597b9e6697a3d gcc/objc/ChangeLog 55692b17b3d7d7442f7be5648f7ed2ba gcc/objc/Make-lang.in aa5319dd541cdb0eb8622f9adf66b761 gcc/objc/README a5357fd1d3ec609df43d565aef4721ab gcc/objc/config-lang.in *************** a5357fd1d3ec609df43d565aef4721ab gcc/ob *** 3949,3955 **** 250fcdcac6e85e806d739ccd66f4bb60 gcc/objc/objc-act.h 0c8ad7b2520bb944fa58e1b400102d68 gcc/objc/objc-lang.c 6779d586f851c44361fe2884d2d9192c gcc/objc/objc-tree.def ! 53ecd663a17c18e25662fa9a86fd66e9 gcc/objcp/ChangeLog ca080f4d714c85a0819b409e167aaee1 gcc/objcp/Make-lang.in a38210df778da649005bd4c671dabc41 gcc/objcp/config-lang.in b69e6fb8f98a0eca7d27309f950a6974 gcc/objcp/lang-specs.h --- 3957,3963 ---- 250fcdcac6e85e806d739ccd66f4bb60 gcc/objc/objc-act.h 0c8ad7b2520bb944fa58e1b400102d68 gcc/objc/objc-lang.c 6779d586f851c44361fe2884d2d9192c gcc/objc/objc-tree.def ! 69b09e14f3dc01bda521c0b728b9f707 gcc/objcp/ChangeLog ca080f4d714c85a0819b409e167aaee1 gcc/objcp/Make-lang.in a38210df778da649005bd4c671dabc41 gcc/objcp/config-lang.in b69e6fb8f98a0eca7d27309f950a6974 gcc/objcp/lang-specs.h *************** d135f0d89724d19dc0c8d23173dc1c41 gcc/op *** 3965,4018 **** 8e4bfd0e82a8e783ee867ddee4b3ef96 gcc/optc-gen.awk 54745cbdebaf92357aeaaa4699024722 gcc/opth-gen.awk 86a6b88a9a66cafa3bf6d25007c0202c gcc/opts-common.c ! 8dbfdfe035b68d4e0a709f0315eb64af gcc/opts.c 61f97043dcb18b09f46fb199d35c00a3 gcc/opts.h 91995da152d1c4c080855f95aeaac3b5 gcc/output.h 1b6d132076d8681fd12145c2cdf73408 gcc/params.c b20b14439709c6947adb98a9a3f4b87f gcc/params.def 25d2bde163e7f842f1699430c6193bcd gcc/params.h 2f9a34dd0ef0633fe17d8230fa96a4f8 gcc/passes.c ! 1adc35236b7c5e1aa2f49ba30eabeb2e gcc/po/ChangeLog 954b21fb36cc0d8e9f6e2d6507152f23 gcc/po/EXCLUDES ! 0871a11186201bcab9a90596334446a9 gcc/po/be.gmo ! 079912ba8ac2ef6e32252140e45804a8 gcc/po/be.po ! afe18aab9562f2b847bec0d7b692053c gcc/po/ca.gmo ! 823520f6502108c85f34b98e4e06eb9e gcc/po/ca.po ! 372a16c83d3965f1bf19664412583a99 gcc/po/da.gmo ! 444105f4b4127d4d40ac83b7d9087696 gcc/po/da.po ! d8954d8cbf98e10de7a838b682e47e0d gcc/po/de.gmo ! 0b36c517b4163a856925bbb45a273393 gcc/po/de.po ! 607cdb2b2f657347f7107310379c659b gcc/po/el.gmo ! 40e8390bf78856940e88ac31f02000c2 gcc/po/el.po ! 5cc615e60071484292901ae9b9d6f3e4 gcc/po/es.gmo ! 923f9976a77c57c16aea0884d27b1e95 gcc/po/es.po 79e2a622a92feeb1346166134cdedf33 gcc/po/exgettext ! 442e30501221b8fe8c2216bf71f31a5b gcc/po/fr.gmo ! ac28a6fae679e1c45c97f303bfeb05b9 gcc/po/fr.po ! 39aaa610847c84089a280f6740c10296 gcc/po/gcc.pot ! 4489ac70919875d09b30fa9b269d4634 gcc/po/ja.gmo ! 569b183c658f8f76eb1450aa302586ad gcc/po/ja.po ! 69ef288304847c936395d07bb0b2519e gcc/po/nl.gmo ! 705ebb0b95f0b73214d85c0f69e6dfc7 gcc/po/nl.po ! d753f8f5331705c0e5f6aaaa07512e71 gcc/po/ru.gmo ! 0f81b274fa1044cc5d9ad2e21e298c57 gcc/po/ru.po bab53e4447aead83f382c207a53692c7 gcc/po/rw.gmo cba3487b06398c4c5e1c95083136541b gcc/po/rw.po ! 9da011cae009eefc650ca7e89948254d gcc/po/sr.gmo ! 8aab38551bb93057efad2189456e5ecf gcc/po/sr.po ! 9027a4f042863c73ad26bdf36e04a4c1 gcc/po/sv.gmo ! a0b271b74aacbffaba279840477f5219 gcc/po/sv.po ! 1d89d51f55f72d759d13436d4f09ed96 gcc/po/tr.gmo ! a7c985050d409d6243128a705182012d gcc/po/tr.po ! db8a14965bddd5c90500464beb2f3222 gcc/po/zh_CN.gmo ! 796c0907a6bb5e4f9ad76a361ea34e4a gcc/po/zh_CN.po ! 6e66f9abfc4bf18ac191e683f8894627 gcc/po/zh_TW.gmo ! c1ef0e1f371af78e325067d849382376 gcc/po/zh_TW.po eb853723e5beb197875f5d3643bee768 gcc/pointer-set.c a049d9941190718304dfa68922439964 gcc/pointer-set.h 69eff7144a87ddf87345beb502fee9ca gcc/postreload-gcse.c b3e127baaeede3081f353c80a6ca30b4 gcc/postreload.c ! ec8d5c412f972184dcff70bc129fc872 gcc/predict.c a1f6b6717d3791c7f02d5fe553c6b420 gcc/predict.def 54c14ce7c3a8cedc8c68ad4832585cc0 gcc/predict.h b1e205b6ebb16720a8d796b4a8bed5c9 gcc/prefix.c --- 3973,4026 ---- 8e4bfd0e82a8e783ee867ddee4b3ef96 gcc/optc-gen.awk 54745cbdebaf92357aeaaa4699024722 gcc/opth-gen.awk 86a6b88a9a66cafa3bf6d25007c0202c gcc/opts-common.c ! 866da111ca0f76b54093bae5dd9d0f62 gcc/opts.c 61f97043dcb18b09f46fb199d35c00a3 gcc/opts.h 91995da152d1c4c080855f95aeaac3b5 gcc/output.h 1b6d132076d8681fd12145c2cdf73408 gcc/params.c b20b14439709c6947adb98a9a3f4b87f gcc/params.def 25d2bde163e7f842f1699430c6193bcd gcc/params.h 2f9a34dd0ef0633fe17d8230fa96a4f8 gcc/passes.c ! 13041225304ab9f427646c58875530a6 gcc/po/ChangeLog 954b21fb36cc0d8e9f6e2d6507152f23 gcc/po/EXCLUDES ! 68531c9f2f3b048184f7ff5467c27949 gcc/po/be.gmo ! 969dd156fd5dcc847b692490ab254205 gcc/po/be.po ! 76c18449fe8515feb55fba59bffeccd3 gcc/po/ca.gmo ! f4b68072fa7c741c9c6536b765627fba gcc/po/ca.po ! ea41df5d8d94b7edb70ae845d2e564c3 gcc/po/da.gmo ! eedf1f541d49561542a128c1ad91b20a gcc/po/da.po ! 424170daed612ff7ed7a7381aa534b2a gcc/po/de.gmo ! b3f63b1796cbb9017bc79a535522be56 gcc/po/de.po ! 76e657b0d7015aacbb1498178f3e442c gcc/po/el.gmo ! 449408137e3ae80446a81acc2f849172 gcc/po/el.po ! d69d83469a5a72d659e470bbf0f222c4 gcc/po/es.gmo ! fe9a8754b8397852798763f8169b94bb gcc/po/es.po 79e2a622a92feeb1346166134cdedf33 gcc/po/exgettext ! 6ec4c750ce6563abbf250d7684888c8f gcc/po/fr.gmo ! d1920617494b77e7f006cc52056b0b1c gcc/po/fr.po ! b7ada1e47d5f80cc149ebd69575e54ef gcc/po/gcc.pot ! 9801dc1e0b66f30f2f4e6e411a22050d gcc/po/ja.gmo ! 3db4b70d0a37144a6e5a5e7fe06c24a9 gcc/po/ja.po ! 1a96db80d600d089a09b78a047b807ce gcc/po/nl.gmo ! 15cd728becdf98e55af3bd0ad6f22408 gcc/po/nl.po ! e39983f872c4546c7ac7d3684078395e gcc/po/ru.gmo ! 3667e4ab028c6bb8e9a9904ba22d7229 gcc/po/ru.po bab53e4447aead83f382c207a53692c7 gcc/po/rw.gmo cba3487b06398c4c5e1c95083136541b gcc/po/rw.po ! 62a91d50db7f19d8c32a97eaecc5c801 gcc/po/sr.gmo ! 4a5d0c2241da654ba59a31f4b0e8c2d7 gcc/po/sr.po ! 28e6520397ffe752b9f7aab02a2468b4 gcc/po/sv.gmo ! edcf3468b569340869b902135af08264 gcc/po/sv.po ! 36cd0ef728cf9ce82f032eda9279f9f2 gcc/po/tr.gmo ! a7a26a69e307e644f946e00a7956aec9 gcc/po/tr.po ! 7faab09137be85b2340a580c079dcdc5 gcc/po/zh_CN.gmo ! 6a212b8f9485f99c07322e8b032278d8 gcc/po/zh_CN.po ! d3a7f5589c24b08227c755c2c134efd7 gcc/po/zh_TW.gmo ! 5dfa5760fe68b4ed309a978041fa13e5 gcc/po/zh_TW.po eb853723e5beb197875f5d3643bee768 gcc/pointer-set.c a049d9941190718304dfa68922439964 gcc/pointer-set.h 69eff7144a87ddf87345beb502fee9ca gcc/postreload-gcse.c b3e127baaeede3081f353c80a6ca30b4 gcc/postreload.c ! 95d55198e892747beaa2865e9cf5ad95 gcc/predict.c a1f6b6717d3791c7f02d5fe553c6b420 gcc/predict.def 54c14ce7c3a8cedc8c68ad4832585cc0 gcc/predict.h b1e205b6ebb16720a8d796b4a8bed5c9 gcc/prefix.c *************** add895c069b51dc4228d617f0b0601d4 gcc/re *** 4034,4050 **** 8401e7fdfa4e016df2d82f6b935e5ee8 gcc/regmove.c 65888a784994df4a67fd4e8015be3fcb gcc/regrename.c fb565e7677d93f3321d15e9350e390aa gcc/regs.h ! 5b88a863c185c77d9ccbfb6f5f4a90cb gcc/reload.c 4ed5f9db30b49e8d254acf5e051484e0 gcc/reload.h 12ab2492957954af69a8fd126842c99b gcc/reload1.c a81f43abc400de3c4cb65e58e2423fb4 gcc/reorg.c ! 60089c8d751cc2561532300917348d65 gcc/resource.c 54902725f5c6a113b64364ffe1d7b6cf gcc/resource.h a41d5668a938b281be8ee435ea1f5a0a gcc/rtl-error.c 616d1dc08bc423c6d2b4a5f22001797b gcc/rtl-factoring.c 8a83ddb069ed825c60ee0c1918bf4a47 gcc/rtl.c 93fcc90ade3ab536b35dd6e7c2e606ec gcc/rtl.def ! 67b1372cf18290235e15685b74f08d71 gcc/rtl.h d114a815f57f0eed90bf4c769dc7121b gcc/rtlanal.c 6054388d8a17ce8570188eccb02510a4 gcc/rtlhooks-def.h ac5602d49752967631aa5bdf5c44c3e7 gcc/rtlhooks.c --- 4042,4058 ---- 8401e7fdfa4e016df2d82f6b935e5ee8 gcc/regmove.c 65888a784994df4a67fd4e8015be3fcb gcc/regrename.c fb565e7677d93f3321d15e9350e390aa gcc/regs.h ! 333c25e6b36f2e74c09f25fdf4e43084 gcc/reload.c 4ed5f9db30b49e8d254acf5e051484e0 gcc/reload.h 12ab2492957954af69a8fd126842c99b gcc/reload1.c a81f43abc400de3c4cb65e58e2423fb4 gcc/reorg.c ! 44c71baebf1637cf3b29eff3518f346d gcc/resource.c 54902725f5c6a113b64364ffe1d7b6cf gcc/resource.h a41d5668a938b281be8ee435ea1f5a0a gcc/rtl-error.c 616d1dc08bc423c6d2b4a5f22001797b gcc/rtl-factoring.c 8a83ddb069ed825c60ee0c1918bf4a47 gcc/rtl.c 93fcc90ade3ab536b35dd6e7c2e606ec gcc/rtl.def ! 40798c8d1ffaeaad3e4bea817c945d0b gcc/rtl.h d114a815f57f0eed90bf4c769dc7121b gcc/rtlanal.c 6054388d8a17ce8570188eccb02510a4 gcc/rtlhooks-def.h ac5602d49752967631aa5bdf5c44c3e7 gcc/rtlhooks.c *************** da1dd0bf9076c8c3ff6467798c4b14a3 gcc/st *** 4081,4087 **** 345d20da5b7897e6236de754fc996eb0 gcc/target.h 1c609c6e05c35743d33b3ca41a50ace0 gcc/targhooks.c 003c193760f694030a2194033851caee gcc/targhooks.h ! c681f283b490579932501646f2794ade gcc/testsuite/ChangeLog 84188c97269b593eb46274047b401b48 gcc/testsuite/ChangeLog.tree-ssa c2eb2f892b7b914e0a687ca43783d1f3 gcc/testsuite/README 728a7ee145c744b1a6d095227d991e8d gcc/testsuite/README.QMTEST --- 4089,4095 ---- 345d20da5b7897e6236de754fc996eb0 gcc/target.h 1c609c6e05c35743d33b3ca41a50ace0 gcc/targhooks.c 003c193760f694030a2194033851caee gcc/targhooks.h ! 164bbefc85feca5670219228ee6b2a15 gcc/testsuite/ChangeLog 84188c97269b593eb46274047b401b48 gcc/testsuite/ChangeLog.tree-ssa c2eb2f892b7b914e0a687ca43783d1f3 gcc/testsuite/README 728a7ee145c744b1a6d095227d991e8d gcc/testsuite/README.QMTEST *************** f1e6899a021674b5b21a2c30a8ce73e6 gcc/te *** 6938,6943 **** --- 6946,6952 ---- 48dde4679a9c2fd89e9213a130223e9e gcc/testsuite/g++.dg/conversion/nullptr2.C 6c0d033c15abd71959655beebc0c3522 gcc/testsuite/g++.dg/conversion/op1.C 3691f2fae514386b7e94bd8db99acd68 gcc/testsuite/g++.dg/conversion/op2.C + 7fc0616b77be1d282a71cb29e276be55 gcc/testsuite/g++.dg/conversion/op4.C 23830a13c326c99bae67e56e30ebc0b4 gcc/testsuite/g++.dg/conversion/ptrmem1.C 6e5e81ebfb94f64d88135e578c526065 gcc/testsuite/g++.dg/conversion/reinterpret1.C da446c68ad3e26a27f1f02cfb80bb439 gcc/testsuite/g++.dg/conversion/reinterpret2.C *************** f50cc26d9a41a3cc4afb62032326372f gcc/te *** 6994,6999 **** --- 7003,7009 ---- de7626032b99ed0b36b4dc7fb3f18f9d gcc/testsuite/g++.dg/debug/typedef3.C 261cdcb5a7c5cf143b8af9beb8258ebc gcc/testsuite/g++.dg/debug/using1.C 06ba44c6640fe57a83e614bcb293ca4d gcc/testsuite/g++.dg/debug/using2.C + e3e47848d7edc7d04e996db8969c01c0 gcc/testsuite/g++.dg/debug/using3.C c30457cdd7ee7c935f79e462e1c7414b gcc/testsuite/g++.dg/dg.exp 562ca7c694e89bb3ac76711c239d5c5e gcc/testsuite/g++.dg/eh/alias1.C 7a789c5f5b392854e4bcc712122b232c gcc/testsuite/g++.dg/eh/arm-vfp-unwind.C *************** f10d716b3c09f9b7a5dda32ab1762b8a gcc/te *** 7033,7039 **** 2fa97d2eb1070b8ff9ed142189631d04 gcc/testsuite/g++.dg/eh/fp-regs.C fa7c4733d09d80ea62bb08bcfe896fbb gcc/testsuite/g++.dg/eh/goto1.C 83a9a4f114479e6635dd508a4994d73d gcc/testsuite/g++.dg/eh/ia64-1.C ! e1578c0312b46ace361d602e2eb677a5 gcc/testsuite/g++.dg/eh/ia64-2.C 8c375c2c927706fd09f5bb467654b648 gcc/testsuite/g++.dg/eh/loop1.C 741a6b9a2519e96d9a6a3d7503d9cdfa gcc/testsuite/g++.dg/eh/loop2.C 85b9081854ce258c515f0bcfcd1b89c6 gcc/testsuite/g++.dg/eh/new1.C --- 7043,7049 ---- 2fa97d2eb1070b8ff9ed142189631d04 gcc/testsuite/g++.dg/eh/fp-regs.C fa7c4733d09d80ea62bb08bcfe896fbb gcc/testsuite/g++.dg/eh/goto1.C 83a9a4f114479e6635dd508a4994d73d gcc/testsuite/g++.dg/eh/ia64-1.C ! 770672d287d134821ae3d85a07f18e95 gcc/testsuite/g++.dg/eh/ia64-2.C 8c375c2c927706fd09f5bb467654b648 gcc/testsuite/g++.dg/eh/loop1.C 741a6b9a2519e96d9a6a3d7503d9cdfa gcc/testsuite/g++.dg/eh/loop2.C 85b9081854ce258c515f0bcfcd1b89c6 gcc/testsuite/g++.dg/eh/new1.C *************** c77f4b5da310cb17818365cde0e153dd gcc/te *** 7072,7078 **** 1ff41980dd5d1398018fd0852361341a gcc/testsuite/g++.dg/eh/unexpected1.C 75e632be1251d6094d2cf9147ed3621d gcc/testsuite/g++.dg/eh/unwind1.C 03f11e36f8513bd32a5ba62702e7fb8b gcc/testsuite/g++.dg/eh/weak1-a.cc ! 046dc8aec968c2de00cd9df5e0148290 gcc/testsuite/g++.dg/eh/weak1.C 4cf16a5e56e9a805e8cab8129d3ec12c gcc/testsuite/g++.dg/expr/anew1.C c272c27e69863d4ba063be24a228ce5f gcc/testsuite/g++.dg/expr/anew2.C 88cfba5bf8bdd95998bb48be16446076 gcc/testsuite/g++.dg/expr/anew3.C --- 7082,7088 ---- 1ff41980dd5d1398018fd0852361341a gcc/testsuite/g++.dg/eh/unexpected1.C 75e632be1251d6094d2cf9147ed3621d gcc/testsuite/g++.dg/eh/unwind1.C 03f11e36f8513bd32a5ba62702e7fb8b gcc/testsuite/g++.dg/eh/weak1-a.cc ! 9503a91187d131f3bfc7c44340baac57 gcc/testsuite/g++.dg/eh/weak1.C 4cf16a5e56e9a805e8cab8129d3ec12c gcc/testsuite/g++.dg/expr/anew1.C c272c27e69863d4ba063be24a228ce5f gcc/testsuite/g++.dg/expr/anew2.C 88cfba5bf8bdd95998bb48be16446076 gcc/testsuite/g++.dg/expr/anew3.C *************** cac7810767ae23faa6823a798e9c3cea gcc/te *** 7340,7345 **** --- 7350,7356 ---- 0217210e867cc6de19f825b9e4b680d3 gcc/testsuite/g++.dg/ext/typeof7.C a9d136cfb86815cbf4d2e46089c90ce0 gcc/testsuite/g++.dg/ext/typeof8.C d7e6d10c23ed31b44c2e6c3268ab2b30 gcc/testsuite/g++.dg/ext/typeof9.C + 8f368ee52bff2600a087163d174828d3 gcc/testsuite/g++.dg/ext/va-arg1.C 1e6ab4b0a8dd095b526fad3f97ec5a91 gcc/testsuite/g++.dg/ext/vector1.C 3f2ba0450158ad5c221f98dd0e641cbf gcc/testsuite/g++.dg/ext/vector2.C 06e44a4208434952189cfd9cd55ae2d8 gcc/testsuite/g++.dg/ext/vector3.C *************** d7e6d10c23ed31b44c2e6c3268ab2b30 gcc/te *** 7349,7354 **** --- 7360,7366 ---- a7cd8c7f7fec871a0af30c9bd8122ba5 gcc/testsuite/g++.dg/ext/visibility/anon1.C f4d13decfaa5840017b392ae099bdac9 gcc/testsuite/g++.dg/ext/visibility/anon2.C 251258dca8835128a261b3557e780874 gcc/testsuite/g++.dg/ext/visibility/anon3.C + 2b43cd0224b885985e8b61dcb08b9f0c gcc/testsuite/g++.dg/ext/visibility/anon6.C baebe8b558d0ca0786152594a8fc8041 gcc/testsuite/g++.dg/ext/visibility/arm1.C 06b4df0aabdec7190ff116eb91fec899 gcc/testsuite/g++.dg/ext/visibility/arm2.C dd565fa017d33c361fc6bf98dcb7e8c5 gcc/testsuite/g++.dg/ext/visibility/arm3.C *************** da4518aa692947ef4c1cc1de9617e5d0 gcc/te *** 7363,7368 **** --- 7375,7381 ---- f6ac3f034af2478f3ae3854a6b304cdb gcc/testsuite/g++.dg/ext/visibility/local1.C d7e8086561549b3830b812ca5fcd9dd6 gcc/testsuite/g++.dg/ext/visibility/memfuncts.C 47546be923a94711f1c67844ab30b6b5 gcc/testsuite/g++.dg/ext/visibility/namespace1.C + eb42889d7ff5930cf589d7b103805b82 gcc/testsuite/g++.dg/ext/visibility/namespace2.C 9a8d2d6de4dd65f8d370f81892ab674c gcc/testsuite/g++.dg/ext/visibility/new1.C f281064d572b9d936c2688733534f68b gcc/testsuite/g++.dg/ext/visibility/noPLT.C a8d59950cbc8ed898d19dfae9f599221 gcc/testsuite/g++.dg/ext/visibility/pragma-override1.C *************** b879c3972fcf09a0bef4781d973dea10 gcc/te *** 7896,7901 **** --- 7909,7915 ---- 4bcc868b38c719f7e50e39d9f302169b gcc/testsuite/g++.dg/opt/const2.C 45fe728a90ca30ef5afd18351211d63f gcc/testsuite/g++.dg/opt/const3.C 6b2e1cf4863e58457238c73c49085813 gcc/testsuite/g++.dg/opt/const4.C + 21c55b941a72d23fcdeb0dbff8b7b415 gcc/testsuite/g++.dg/opt/const5.C 8a6577c2e8b91d69c2d55b8ed2488fc8 gcc/testsuite/g++.dg/opt/copysign-1.C fe3330f4dcc4be90e5790ce38f643df9 gcc/testsuite/g++.dg/opt/covariant1.C 2b8e568482a37c0e98a0154aa649f58b gcc/testsuite/g++.dg/opt/crash1.C *************** e1eac1beda3a4145544bb54bc5a9b600 gcc/te *** 8099,8104 **** --- 8113,8119 ---- 58bd7d16ec53ed8a6a7fa2324262edb7 gcc/testsuite/g++.dg/other/error13.C 199a456577f88591ddb34aaf3dc0fce4 gcc/testsuite/g++.dg/other/error14.C a3f17494f8e1b20ef3cdd8667b5a3fbc gcc/testsuite/g++.dg/other/error16.C + 711e0290c8826b0e1a3830f597efd7aa gcc/testsuite/g++.dg/other/error19.C a7f642f46d2d9259194f51e24e5b9ee6 gcc/testsuite/g++.dg/other/error2.C 3820027b29c821fc3271c5cd12393a28 gcc/testsuite/g++.dg/other/error3.C 2a54dfbc2f51bbaad10a9a32a8c1f212 gcc/testsuite/g++.dg/other/error4.C *************** e789e85b8e83c35e7e483d4d892e55fd gcc/te *** 8186,8192 **** 195390f264266be35f2d327ceae6b25a gcc/testsuite/g++.dg/other/typedef1.C 257a7ccb9a00dcf8f78b7667d6ccb94f gcc/testsuite/g++.dg/other/ucnid-1.C 5c2adc76f21ce8f7182fe1930db8db73 gcc/testsuite/g++.dg/other/unreachable1.C ! 46ad651b7e23f3fa24cd0791421b81e5 gcc/testsuite/g++.dg/other/unused1.C 6aa48be6aef2630759f48ff66b6424bd gcc/testsuite/g++.dg/other/vararg-1.C 60563e69386b8a906233c2d479c02e6b gcc/testsuite/g++.dg/other/vararg-2.C a6a9e2f5bcb753435ad581ee25ed4d6b gcc/testsuite/g++.dg/other/virtual1.C --- 8201,8207 ---- 195390f264266be35f2d327ceae6b25a gcc/testsuite/g++.dg/other/typedef1.C 257a7ccb9a00dcf8f78b7667d6ccb94f gcc/testsuite/g++.dg/other/ucnid-1.C 5c2adc76f21ce8f7182fe1930db8db73 gcc/testsuite/g++.dg/other/unreachable1.C ! 0e5cd2d64aeb89eb996d838918376c19 gcc/testsuite/g++.dg/other/unused1.C 6aa48be6aef2630759f48ff66b6424bd gcc/testsuite/g++.dg/other/vararg-1.C 60563e69386b8a906233c2d479c02e6b gcc/testsuite/g++.dg/other/vararg-2.C a6a9e2f5bcb753435ad581ee25ed4d6b gcc/testsuite/g++.dg/other/virtual1.C *************** d803021f22dfc38b8a134bf943ae1777 gcc/te *** 8310,8315 **** --- 8325,8331 ---- 4da688072d086cf75b2f22024c74296a gcc/testsuite/g++.dg/parse/crash33.C a082e1ec4d2ff1d8b432964e3209d790 gcc/testsuite/g++.dg/parse/crash37.C ea254dd6e59a027998efd9cbcb6f405d gcc/testsuite/g++.dg/parse/crash4.C + dac388429deb82f9694f4378a50eac14 gcc/testsuite/g++.dg/parse/crash40.C ca305e88317a3cd781d4bd8bf8fc3fc4 gcc/testsuite/g++.dg/parse/crash5.C 3cae354cb01ecb5097fe78c4d17c8ccd gcc/testsuite/g++.dg/parse/crash6.C 34393b72e5dec85fca930dee15e2f669 gcc/testsuite/g++.dg/parse/crash7.C *************** a4ca49fa3677bf87a27b0e961eab1cee gcc/te *** 8592,8597 **** --- 8608,8614 ---- f03a5377eca516c74e77fcf76b40f948 gcc/testsuite/g++.dg/rtti/typeid2.C 3e23755748cd7e94d3bc13c5d2f78cc9 gcc/testsuite/g++.dg/rtti/typeid3.C f45226306cb853d7f47a657db3e4f853 gcc/testsuite/g++.dg/rtti/typeid4.C + fa4939a5b9ad3f1e2d86d16ba8f86a6f gcc/testsuite/g++.dg/rtti/typeid6.C 3c2de2b26bcb38e1fa16fbf23d65049d gcc/testsuite/g++.dg/special/conpr-1.C c93d73da1aa0fb227f2ba91f6a99c670 gcc/testsuite/g++.dg/special/conpr-2.C 2d8ae59b7352068b0fab22f68c6ddc93 gcc/testsuite/g++.dg/special/conpr-2a.cc *************** fb2e00c0df67ca0bdb82db579b06a881 gcc/te *** 8663,8668 **** --- 8680,8686 ---- 7bea6580b2b65de331f30831724d355f gcc/testsuite/g++.dg/template/arg2.C f455d543dc6a4d6f270fe652fcc368e7 gcc/testsuite/g++.dg/template/arg3.C c306ff6eb2399c47b955c0f32952ba01 gcc/testsuite/g++.dg/template/arg4.C + f90e567b7331a6236abd917963c61a0f gcc/testsuite/g++.dg/template/arg6.C 99d7b1deba3ad5e11fcbd2dc7d70e9ee gcc/testsuite/g++.dg/template/array1-1.C 075227803fea6455eb958b3d2d173e9b gcc/testsuite/g++.dg/template/array1-2.C 2960ad36eda739b652d2efa379834c5c gcc/testsuite/g++.dg/template/array10.C *************** b4c360f4d0cd0589e95ae87a4d8e500e gcc/te *** 8844,8849 **** --- 8862,8869 ---- d6f93055afe5bb78dbd6073dd989bdef gcc/testsuite/g++.dg/template/error26.C 0e96862a75ffea6e3b8357e5251534dd gcc/testsuite/g++.dg/template/error3.C 1c44a4e548dcd05ce209cc978411cde0 gcc/testsuite/g++.dg/template/error30.C + 0f550f42a764725b5ef085971e281ea8 gcc/testsuite/g++.dg/template/error31.C + 7b9093b26f8920c628c47bed533cc022 gcc/testsuite/g++.dg/template/error35.C 85340063cfaafdde79cb0b7bff303541 gcc/testsuite/g++.dg/template/error4.C a988dc6a097a8766258a32544791c7db gcc/testsuite/g++.dg/template/error5.C 8f931fa8690071fcefc2b1d1d7483bfc gcc/testsuite/g++.dg/template/error6.C *************** a028161f345a592e44b9dd2c85780ba8 gcc/te *** 8994,8999 **** --- 9014,9020 ---- 1cf2f3c9d70e586c16763a10c08d9972 gcc/testsuite/g++.dg/template/nested2.C 2dd76004142f83b603103df120fab7a4 gcc/testsuite/g++.dg/template/nested3.C b12c9a151e46871b430564ee47c57714 gcc/testsuite/g++.dg/template/nested4.C + 73ab67ac2716db374ac0d80e7ae5b200 gcc/testsuite/g++.dg/template/nested5.C 57b33208329c8d10ea904c3d123076a9 gcc/testsuite/g++.dg/template/new1.C b8243d46589815a568bb0992cb04adec gcc/testsuite/g++.dg/template/new2.C 6740416d263e80004be36d0766c39e7f gcc/testsuite/g++.dg/template/new3.C *************** e425d7fc584cf8535f3eee565f58f091 gcc/te *** 9306,9311 **** --- 9327,9333 ---- 7212556766805451a098e554a8ab648e gcc/testsuite/g++.dg/tls/trivial.C 3358654c15c735005d99a7184705a067 gcc/testsuite/g++.dg/torture/dg-torture.exp e9780c172c681062c7a2b35fc6317156 gcc/testsuite/g++.dg/torture/pr32563.C + 85e911bb9e21255ea86be27fe65584a1 gcc/testsuite/g++.dg/torture/pr34953.C 2a1f9c8b1ccb241e4745f1e06c56fac3 gcc/testsuite/g++.dg/tree-ssa/20040317-1.C d4c530769d43a1d750e74fd5f10a662c gcc/testsuite/g++.dg/tree-ssa/block1.C 92014ea122d687546fe3649560d8b2a7 gcc/testsuite/g++.dg/tree-ssa/builtin1.C *************** d38f2baba123fd53fd6d8366b82adf54 gcc/te *** 9431,9436 **** --- 9453,9459 ---- f203af23e924be80d891b0c53a7bee3e gcc/testsuite/g++.dg/warn/Wstrict-aliasing-5.C c92cdb0aebb5d139da6039eb73219857 gcc/testsuite/g++.dg/warn/Wstrict-aliasing-6.C 3bed4d82e24bcdb77b538920a6cdfdeb gcc/testsuite/g++.dg/warn/Wstrict-aliasing-7.C + 71435332433246858548fb92a3a29591 gcc/testsuite/g++.dg/warn/Wstrict-aliasing-8.C b2ac295c001e28b6659dd1cbaecfc2a9 gcc/testsuite/g++.dg/warn/Wstring-literal-comparison-1.C c608f5d02a06d2e24d8ab0ca0d977f67 gcc/testsuite/g++.dg/warn/Wstring-literal-comparison-2.C a0b497dc1f8dc8ce49f81bc391f0deb1 gcc/testsuite/g++.dg/warn/Wstring-literal-comparison-3.C *************** c0116d02edfe6d83a6e0319b7ae43310 gcc/te *** 11323,11329 **** ea73badcef0f5166a559e07a0c263a92 gcc/testsuite/g++.old-deja/g++.ns/using7.C e592ac6b9789af1e806b4791c984da05 gcc/testsuite/g++.old-deja/g++.ns/using8.C 10a3890377e72341f4119f4affe2c8cb gcc/testsuite/g++.old-deja/g++.ns/using9.C ! 361d3c45470151930a8737d2a84cfc11 gcc/testsuite/g++.old-deja/g++.oliva/ChangeLog c17ab5a5d39a20786219d5cb72e8a956 gcc/testsuite/g++.old-deja/g++.oliva/ctor1.C 2a6be2a8952603f1259d7023b81ce14b gcc/testsuite/g++.old-deja/g++.oliva/delete1.C 8c0b3f49c2e5d5c224c1e0aae235e1d8 gcc/testsuite/g++.old-deja/g++.oliva/delete2.C --- 11346,11352 ---- ea73badcef0f5166a559e07a0c263a92 gcc/testsuite/g++.old-deja/g++.ns/using7.C e592ac6b9789af1e806b4791c984da05 gcc/testsuite/g++.old-deja/g++.ns/using8.C 10a3890377e72341f4119f4affe2c8cb gcc/testsuite/g++.old-deja/g++.ns/using9.C ! 72edc0523b5cf1ec9add1533e8fd37f1 gcc/testsuite/g++.old-deja/g++.oliva/ChangeLog c17ab5a5d39a20786219d5cb72e8a956 gcc/testsuite/g++.old-deja/g++.oliva/ctor1.C 2a6be2a8952603f1259d7023b81ce14b gcc/testsuite/g++.old-deja/g++.oliva/delete1.C 8c0b3f49c2e5d5c224c1e0aae235e1d8 gcc/testsuite/g++.old-deja/g++.oliva/delete2.C *************** a7fab87a8c390c4617ffe8f8ce708234 gcc/te *** 13131,13136 **** --- 13154,13161 ---- f03eacba1bbcd93a953ba065e48971d7 gcc/testsuite/gcc.c-torture/compile/20070419-1.c 5d6ece76aad43ec91311b4383720f21d gcc/testsuite/gcc.c-torture/compile/20070827-1.c c296f54c866c7e6e437f4de195bc9cc4 gcc/testsuite/gcc.c-torture/compile/20070925-1.c + 1013b465af9c38b5c22712a1be4121ee gcc/testsuite/gcc.c-torture/compile/20071102-1.c + 953aeba6096373c8d9bd146dccfa4759 gcc/testsuite/gcc.c-torture/compile/20080114-1.c ab32e65ea5976f9083dc8234dae65343 gcc/testsuite/gcc.c-torture/compile/900116-1.c 19f66edc69de3cb6b5ca746e4dc7d9b5 gcc/testsuite/gcc.c-torture/compile/900216-1.c 9c85c5a027876d1435b0499666da5dd8 gcc/testsuite/gcc.c-torture/compile/900313-1.c *************** b65cd2dfd7772968b2a0a769f4fdd212 gcc/te *** 13520,13526 **** 8414734b4834207fc1850e1e31d51d45 gcc/testsuite/gcc.c-torture/compile/pr27341-1.c e534cfe0451d578c8bd575b6c72d4b3f gcc/testsuite/gcc.c-torture/compile/pr27341-2.c 4a29668fb24ae53cf0bea8d0de6d2bfa gcc/testsuite/gcc.c-torture/compile/pr27373.c ! 1bd589c09ee77141509b8d214086f050 gcc/testsuite/gcc.c-torture/compile/pr27528.c 2e6835d1b25845717344c8965a30d964 gcc/testsuite/gcc.c-torture/compile/pr27571.c d468b3d1f591e59d79f6ac4bdb2b938e gcc/testsuite/gcc.c-torture/compile/pr27863.c df619b73313365417d2e65df26d9cacc gcc/testsuite/gcc.c-torture/compile/pr27889.c --- 13545,13551 ---- 8414734b4834207fc1850e1e31d51d45 gcc/testsuite/gcc.c-torture/compile/pr27341-1.c e534cfe0451d578c8bd575b6c72d4b3f gcc/testsuite/gcc.c-torture/compile/pr27341-2.c 4a29668fb24ae53cf0bea8d0de6d2bfa gcc/testsuite/gcc.c-torture/compile/pr27373.c ! b25244c37bcc4b8ca2185de9d14fceb5 gcc/testsuite/gcc.c-torture/compile/pr27528.c 2e6835d1b25845717344c8965a30d964 gcc/testsuite/gcc.c-torture/compile/pr27571.c d468b3d1f591e59d79f6ac4bdb2b938e gcc/testsuite/gcc.c-torture/compile/pr27863.c df619b73313365417d2e65df26d9cacc gcc/testsuite/gcc.c-torture/compile/pr27889.c *************** c2a05ca65901fd8dea80ad2a9a960f66 gcc/te *** 13542,13547 **** --- 13567,13573 ---- 85222c4acc03142d2e6a89c2b8f66687 gcc/testsuite/gcc.c-torture/compile/pr31953.c e6fbdd8c3514630b61c04483b6f5c9f4 gcc/testsuite/gcc.c-torture/compile/pr32169.c 188920fae00d95d4e39a5f3415b24815 gcc/testsuite/gcc.c-torture/compile/pr33382.c + 734fa642c271718ddf067a92aa58981b gcc/testsuite/gcc.c-torture/compile/pr34030.c b9e6ce52b90320c1c3803c25113844c5 gcc/testsuite/gcc.c-torture/compile/pta-1.c 8d869e3426345f0cf8837c5eaafd43b5 gcc/testsuite/gcc.c-torture/compile/simd-1.c 7249a75cf6b955efed52b5ec5cee3a79 gcc/testsuite/gcc.c-torture/compile/simd-2.c *************** f65a0e374ec285a6654aa47a054707b0 gcc/te *** 13946,13951 **** --- 13972,13978 ---- 63a1dbcaa742f75a8a48d1e4a3e44a93 gcc/testsuite/gcc.c-torture/execute/20070201-1.c 5569d39aa5a51b9eb17169c403021e09 gcc/testsuite/gcc.c-torture/execute/20070517-1.c e5b4685ba40ad7e05f982d75ff7896cb gcc/testsuite/gcc.c-torture/execute/20070614-1.c + f2ae8018b0ca00588fe7dfdbe6ed01e5 gcc/testsuite/gcc.c-torture/execute/20080122-1.c 65f01ac7346bd4d47ed9c1ca94ab74ff gcc/testsuite/gcc.c-torture/execute/900409-1.c 5aefab4daab0bd29ecf2a389f3c44f40 gcc/testsuite/gcc.c-torture/execute/920202-1.c 655936aaf9a63e991a555cbc16738485 gcc/testsuite/gcc.c-torture/execute/920302-1.c *************** d7d9ce89ee3d3fe0e8938f62790f051e gcc/te *** 14284,14290 **** 1dda6f7a5d9ce23a5db5f59c430ae29e gcc/testsuite/gcc.c-torture/execute/builtins/abs-3-lib.c 8784d3bd9b264b3c2abfb7b7ea25ccb6 gcc/testsuite/gcc.c-torture/execute/builtins/abs-3.c 30caf0ee310178672ba91b754d7959ef gcc/testsuite/gcc.c-torture/execute/builtins/builtins.exp ! b2f01a311d0be15915da9c4f8cea407b gcc/testsuite/gcc.c-torture/execute/builtins/chk.h f36e146a2aececdc84d9199d53a363ec gcc/testsuite/gcc.c-torture/execute/builtins/complex-1-lib.c 8b5a662c0134cd00115a5866e1c0b6c9 gcc/testsuite/gcc.c-torture/execute/builtins/complex-1.c 90337ef4b3870f5eb8816e67bf132f5b gcc/testsuite/gcc.c-torture/execute/builtins/fprintf-lib.c --- 14311,14317 ---- 1dda6f7a5d9ce23a5db5f59c430ae29e gcc/testsuite/gcc.c-torture/execute/builtins/abs-3-lib.c 8784d3bd9b264b3c2abfb7b7ea25ccb6 gcc/testsuite/gcc.c-torture/execute/builtins/abs-3.c 30caf0ee310178672ba91b754d7959ef gcc/testsuite/gcc.c-torture/execute/builtins/builtins.exp ! ac07f2c8ec1fcd57019151c99bf70a1c gcc/testsuite/gcc.c-torture/execute/builtins/chk.h f36e146a2aececdc84d9199d53a363ec gcc/testsuite/gcc.c-torture/execute/builtins/complex-1-lib.c 8b5a662c0134cd00115a5866e1c0b6c9 gcc/testsuite/gcc.c-torture/execute/builtins/complex-1.c 90337ef4b3870f5eb8816e67bf132f5b gcc/testsuite/gcc.c-torture/execute/builtins/fprintf-lib.c *************** fbd89da6790b4772f3f6c3580a2bb177 gcc/te *** 14346,14356 **** 8e258d2fc5daa60d7007d842cf555b36 gcc/testsuite/gcc.c-torture/execute/builtins/snprintf-chk-lib.c d071205c9510611d08a780090a75fadb gcc/testsuite/gcc.c-torture/execute/builtins/snprintf-chk.c 8e258d2fc5daa60d7007d842cf555b36 gcc/testsuite/gcc.c-torture/execute/builtins/sprintf-chk-lib.c ! eb8018c5c3f69cd285e9b5f69355afbf gcc/testsuite/gcc.c-torture/execute/builtins/sprintf-chk.c 8beff4ed5536d77b3917ad34bd3ca734 gcc/testsuite/gcc.c-torture/execute/builtins/sprintf-lib.c aa92bdcd5fbfe3cb673a1970666031da gcc/testsuite/gcc.c-torture/execute/builtins/sprintf.c 8e258d2fc5daa60d7007d842cf555b36 gcc/testsuite/gcc.c-torture/execute/builtins/stpcpy-chk-lib.c ! e80e46c86eb537086359835e3c3c6474 gcc/testsuite/gcc.c-torture/execute/builtins/stpcpy-chk.c 8e258d2fc5daa60d7007d842cf555b36 gcc/testsuite/gcc.c-torture/execute/builtins/strcat-chk-lib.c 1b9c36f8a2ff3a8a83023d84ce3c90ac gcc/testsuite/gcc.c-torture/execute/builtins/strcat-chk.c d30a8e27b147083b189425af5fe05b2b gcc/testsuite/gcc.c-torture/execute/builtins/strcat-lib.c --- 14373,14383 ---- 8e258d2fc5daa60d7007d842cf555b36 gcc/testsuite/gcc.c-torture/execute/builtins/snprintf-chk-lib.c d071205c9510611d08a780090a75fadb gcc/testsuite/gcc.c-torture/execute/builtins/snprintf-chk.c 8e258d2fc5daa60d7007d842cf555b36 gcc/testsuite/gcc.c-torture/execute/builtins/sprintf-chk-lib.c ! a1b58e654aa1ee2b258aef72b271b55e gcc/testsuite/gcc.c-torture/execute/builtins/sprintf-chk.c 8beff4ed5536d77b3917ad34bd3ca734 gcc/testsuite/gcc.c-torture/execute/builtins/sprintf-lib.c aa92bdcd5fbfe3cb673a1970666031da gcc/testsuite/gcc.c-torture/execute/builtins/sprintf.c 8e258d2fc5daa60d7007d842cf555b36 gcc/testsuite/gcc.c-torture/execute/builtins/stpcpy-chk-lib.c ! 8faea3c5de7b993193a0e5aa96080bb0 gcc/testsuite/gcc.c-torture/execute/builtins/stpcpy-chk.c 8e258d2fc5daa60d7007d842cf555b36 gcc/testsuite/gcc.c-torture/execute/builtins/strcat-chk-lib.c 1b9c36f8a2ff3a8a83023d84ce3c90ac gcc/testsuite/gcc.c-torture/execute/builtins/strcat-chk.c d30a8e27b147083b189425af5fe05b2b gcc/testsuite/gcc.c-torture/execute/builtins/strcat-lib.c *************** ff52ed0b06289edabcc2b0f6f8f448b1 gcc/te *** 14362,14368 **** f04fadc50b6e98e48602a5d15661e114 gcc/testsuite/gcc.c-torture/execute/builtins/strcpy-2-lib.c 12a68323d77bf047184825e4c1543639 gcc/testsuite/gcc.c-torture/execute/builtins/strcpy-2.c 8e258d2fc5daa60d7007d842cf555b36 gcc/testsuite/gcc.c-torture/execute/builtins/strcpy-chk-lib.c ! e41eb12ddc5fb3d06194511a30f0cc47 gcc/testsuite/gcc.c-torture/execute/builtins/strcpy-chk.c f04fadc50b6e98e48602a5d15661e114 gcc/testsuite/gcc.c-torture/execute/builtins/strcpy-lib.c 0fb0648c98cfe654d7afe0fa00e80ef0 gcc/testsuite/gcc.c-torture/execute/builtins/strcpy.c 4991954f9732f6d3d1f60cb416a07430 gcc/testsuite/gcc.c-torture/execute/builtins/strcspn-lib.c --- 14389,14395 ---- f04fadc50b6e98e48602a5d15661e114 gcc/testsuite/gcc.c-torture/execute/builtins/strcpy-2-lib.c 12a68323d77bf047184825e4c1543639 gcc/testsuite/gcc.c-torture/execute/builtins/strcpy-2.c 8e258d2fc5daa60d7007d842cf555b36 gcc/testsuite/gcc.c-torture/execute/builtins/strcpy-chk-lib.c ! d331a83bf0bbf9852015239b13dbf902 gcc/testsuite/gcc.c-torture/execute/builtins/strcpy-chk.c f04fadc50b6e98e48602a5d15661e114 gcc/testsuite/gcc.c-torture/execute/builtins/strcpy-lib.c 0fb0648c98cfe654d7afe0fa00e80ef0 gcc/testsuite/gcc.c-torture/execute/builtins/strcpy.c 4991954f9732f6d3d1f60cb416a07430 gcc/testsuite/gcc.c-torture/execute/builtins/strcspn-lib.c *************** c57dee1df489b70fa8d7fbdc0b505efd gcc/te *** 14633,14641 **** 2dfccb1970f967ad4ac9f6156747b98e gcc/testsuite/gcc.c-torture/execute/pr31136.c 26771f8bff4c4c78f76c5e1f62c63951 gcc/testsuite/gcc.c-torture/execute/pr31448.c 7805f8639c582612b3b186389c026f95 gcc/testsuite/gcc.c-torture/execute/pr31605.c ! 8f0868c1d7dfc98216ed4246215a4924 gcc/testsuite/gcc.c-torture/execute/pr32500.c ebd84d8000d69d97c5201c5d43ce6acb gcc/testsuite/gcc.c-torture/execute/pr33142.c 72c00306fd8d986befd3a99155d5300f gcc/testsuite/gcc.c-torture/execute/pr33382.c ecfc31f12ce09d6ccbcced04ff04deba gcc/testsuite/gcc.c-torture/execute/pr7284-1.c 89f3c7ee990221eeb33cb08a0772e024 gcc/testsuite/gcc.c-torture/execute/pr7284-1.x f4610e3bba97324f7005c428fe41e597 gcc/testsuite/gcc.c-torture/execute/printf-1.c --- 14660,14676 ---- 2dfccb1970f967ad4ac9f6156747b98e gcc/testsuite/gcc.c-torture/execute/pr31136.c 26771f8bff4c4c78f76c5e1f62c63951 gcc/testsuite/gcc.c-torture/execute/pr31448.c 7805f8639c582612b3b186389c026f95 gcc/testsuite/gcc.c-torture/execute/pr31605.c ! eba8b48678f36c3b71094bab10593a19 gcc/testsuite/gcc.c-torture/execute/pr32500.c ! 68b362756f7215a41409a0140d6337f3 gcc/testsuite/gcc.c-torture/execute/pr33099.c ebd84d8000d69d97c5201c5d43ce6acb gcc/testsuite/gcc.c-torture/execute/pr33142.c + d082ead1ed41374865d9ec6834e3a6d2 gcc/testsuite/gcc.c-torture/execute/pr33381.c 72c00306fd8d986befd3a99155d5300f gcc/testsuite/gcc.c-torture/execute/pr33382.c + 7e23aa461193085ca858ef46015635d0 gcc/testsuite/gcc.c-torture/execute/pr34070-1.c + 91167b216833ddba70a5902c3e4536c4 gcc/testsuite/gcc.c-torture/execute/pr34070-2.c + 281cdbfa776ef9b3ffe184023bb013f7 gcc/testsuite/gcc.c-torture/execute/pr34130.c + 89372dd3de06cc33b22e953e5e3ae4bc gcc/testsuite/gcc.c-torture/execute/pr34456.c + 01aa598710310e5a7b6317dd682b7ff3 gcc/testsuite/gcc.c-torture/execute/pr34768-1.c + 8613ebbe9a1d857ff130cabe7d53ee16 gcc/testsuite/gcc.c-torture/execute/pr34768-2.c ecfc31f12ce09d6ccbcced04ff04deba gcc/testsuite/gcc.c-torture/execute/pr7284-1.c 89f3c7ee990221eeb33cb08a0772e024 gcc/testsuite/gcc.c-torture/execute/pr7284-1.x f4610e3bba97324f7005c428fe41e597 gcc/testsuite/gcc.c-torture/execute/printf-1.c *************** af59ad0b143483efd888a257a65c26fc gcc/te *** 15305,15310 **** --- 15340,15346 ---- b5ad199b445f815305d03f992fd70017 gcc/testsuite/gcc.dg/Wstrict-overflow-18.c b52d121e1316dbd9e52693b569b05bc6 gcc/testsuite/gcc.dg/Wstrict-overflow-19.c 9391f3a448b1237ff2144b2525ab77a0 gcc/testsuite/gcc.dg/Wstrict-overflow-2.c + 4285b79df21aa7bdaf2de8d693439bc2 gcc/testsuite/gcc.dg/Wstrict-overflow-21.c bb2099f1da2a18a8306bbf5e15b7e411 gcc/testsuite/gcc.dg/Wstrict-overflow-3.c 43d27c6b3c5f95da1becd819eb01bc7c gcc/testsuite/gcc.dg/Wstrict-overflow-4.c 78e163530595bd814f038df2ea425bbd gcc/testsuite/gcc.dg/Wstrict-overflow-6.c *************** e370903640e76bf4ef407aafe0286689 gcc/te *** 15393,15399 **** a5a76a31878bcc44537a13babdf4eac9 gcc/testsuite/gcc.dg/asmreg-1.c a26027e8bb2354fa867e30c37ca5de94 gcc/testsuite/gcc.dg/assign-warn-1.c 3e3451f76bb51f79a1a86c662b672aaa gcc/testsuite/gcc.dg/assign-warn-2.c ! 0995442e27d091d9fc4f5e286fd8e86e gcc/testsuite/gcc.dg/assign-warn-3.c bfcf3d61cfaeb70ffaf79290c46dc732 gcc/testsuite/gcc.dg/attr-alias-1.c e1871215b9eef07b10dc8c1bf21c038a gcc/testsuite/gcc.dg/attr-alias-2.c 19782fec9e9e327ec4805b8e282f8df8 gcc/testsuite/gcc.dg/attr-alias-3.c --- 15429,15435 ---- a5a76a31878bcc44537a13babdf4eac9 gcc/testsuite/gcc.dg/asmreg-1.c a26027e8bb2354fa867e30c37ca5de94 gcc/testsuite/gcc.dg/assign-warn-1.c 3e3451f76bb51f79a1a86c662b672aaa gcc/testsuite/gcc.dg/assign-warn-2.c ! 35a862f8ff096f4ef8c22c99afe897e6 gcc/testsuite/gcc.dg/assign-warn-3.c bfcf3d61cfaeb70ffaf79290c46dc732 gcc/testsuite/gcc.dg/attr-alias-1.c e1871215b9eef07b10dc8c1bf21c038a gcc/testsuite/gcc.dg/attr-alias-2.c 19782fec9e9e327ec4805b8e282f8df8 gcc/testsuite/gcc.dg/attr-alias-3.c *************** ce354ccb3e1bed31286dc21c6b83f645 gcc/te *** 16476,16481 **** --- 16512,16518 ---- c3d0e5f87b23f96c728ab8dd3707bb9b gcc/testsuite/gcc.dg/empty1.c 959121eabe31d6444e7adffe039b0bdd gcc/testsuite/gcc.dg/empty2.c f46331dedfa15ae75ea7543b07fd7d45 gcc/testsuite/gcc.dg/enum-compat-1.c + c098ce6d3967a1bd0e4ccb722d146dd8 gcc/testsuite/gcc.dg/enum-incomplete-1.c ba60814aadf21741cc3e6781a96f6801 gcc/testsuite/gcc.dg/enum1.c 36d60a18cc2d81c2f3553d9d74463b9e gcc/testsuite/gcc.dg/enum2.c a50b0f335a12a722f789c3ed820f2f93 gcc/testsuite/gcc.dg/enum3.c *************** e4ba881665ef030f84ea9dcf900d3b19 gcc/te *** 16629,16634 **** --- 16666,16672 ---- 1cf9e5c4ca991ae1427cec43e737b17a gcc/testsuite/gcc.dg/fwrapv-2.c 45fef48ca8279d632a39944292d31d44 gcc/testsuite/gcc.dg/glibc-uclibc-1.c 284a79575a3c4010b6473dfb5f754f4e gcc/testsuite/gcc.dg/glibc-uclibc-2.c + b4349fffa1c9af61128746fdbc8891f1 gcc/testsuite/gcc.dg/globalreg-1.c 644bbd61aaed9ff26399d6df215c0bf6 gcc/testsuite/gcc.dg/gnu-cond-expr-1.c a8582cd0b161ca78615629575be48ebd gcc/testsuite/gcc.dg/gnu-cond-expr-2.c 182acc593171594b059c21f3e6add5a9 gcc/testsuite/gcc.dg/gnu-cond-expr-3.c *************** b7f0fbd7e8fabadddf5296da3d7ccec6 gcc/te *** 16854,16860 **** c0e78df24f77e92ad5b9cb0808778c9f gcc/testsuite/gcc.dg/label-decl-2.c 51f9d0596a8219a81f4e562e99d6567c gcc/testsuite/gcc.dg/label-decl-3.c d4e500abbaab94e2aa8034e74b2020c1 gcc/testsuite/gcc.dg/label-decl-4.c ! 26de2e6c82e17f1796ce34a166aa7a3d gcc/testsuite/gcc.dg/large-size-array-2.c 8b84904c2e80dc5c4389ac11dd7dd67f gcc/testsuite/gcc.dg/large-size-array.c a1511014730573ca08fa055a4f00aa75 gcc/testsuite/gcc.dg/lazy-ptr-test.c a2385eedd735afde625296ec7c33f79d gcc/testsuite/gcc.dg/local1.c --- 16892,16899 ---- c0e78df24f77e92ad5b9cb0808778c9f gcc/testsuite/gcc.dg/label-decl-2.c 51f9d0596a8219a81f4e562e99d6567c gcc/testsuite/gcc.dg/label-decl-3.c d4e500abbaab94e2aa8034e74b2020c1 gcc/testsuite/gcc.dg/label-decl-4.c ! 2576b86d15dfafad85f9430882c9f0da gcc/testsuite/gcc.dg/large-size-array-2.c ! 0c703ea168624c15b4fc96ec8d4bf62b gcc/testsuite/gcc.dg/large-size-array-4.c 8b84904c2e80dc5c4389ac11dd7dd67f gcc/testsuite/gcc.dg/large-size-array.c a1511014730573ca08fa055a4f00aa75 gcc/testsuite/gcc.dg/lazy-ptr-test.c a2385eedd735afde625296ec7c33f79d gcc/testsuite/gcc.dg/local1.c *************** fb2a64e28af210271512e32c8451c2f2 gcc/te *** 16977,16982 **** --- 17016,17022 ---- 77874127e73f5ada2c09e438669a508b gcc/testsuite/gcc.dg/old-style-prom-2.c c631142fa2ddf4f0ab0fc3420576c02c gcc/testsuite/gcc.dg/old-style-prom-3.c 958025f542696e48d89f0fdd5d94a4a3 gcc/testsuite/gcc.dg/old-style-then-proto-1.c + 2ccf4779da433efac9356b52e777a76c gcc/testsuite/gcc.dg/out-of-bounds-1.c d524cbf9b3805a6b9bbfc037661424cc gcc/testsuite/gcc.dg/overflow-1.c 1bef7f403044d1646079b0bf7ffe725c gcc/testsuite/gcc.dg/overflow-2.c 8fcf44c68bdaf41d825e1f466241f51b gcc/testsuite/gcc.dg/overflow-warn-1.c *************** e3dcbccbd31fac91ba40b78e77eac7de gcc/te *** 17274,17285 **** 0a0e3c4374cb90b75ff5b67ef56a253c gcc/testsuite/gcc.dg/pr28706.c b26a5109baf18ac16bb86d7d94a27896 gcc/testsuite/gcc.dg/pr28712.c 0f5d0ea66f65798abba5fa2cc198c910 gcc/testsuite/gcc.dg/pr28726.c 779db5f723f6a79c6be21e7b2b8012ba gcc/testsuite/gcc.dg/pr28839.c e8c37d720ed122aba160a22c70b198ac gcc/testsuite/gcc.dg/pr28888.c ca06792b688f53956ed815725a0335e8 gcc/testsuite/gcc.dg/pr28911.c d0e97ea1d56239299a14668f6dce570b gcc/testsuite/gcc.dg/pr28935.c fa5c8aebace3e5a4d550811e31ea349b gcc/testsuite/gcc.dg/pr29091.c ! bbf8dbc39f902dfd17428fa794bcf815 gcc/testsuite/gcc.dg/pr29254.c 161eff1fb461cde37dc4b366730b1d6d gcc/testsuite/gcc.dg/pr29299.c d5763ed115978d48b488b6f1cc01cfe9 gcc/testsuite/gcc.dg/pr29330.c f1e44da34ca91b1612fcd1cabc5ab5b3 gcc/testsuite/gcc.dg/pr29581-1.c --- 17314,17327 ---- 0a0e3c4374cb90b75ff5b67ef56a253c gcc/testsuite/gcc.dg/pr28706.c b26a5109baf18ac16bb86d7d94a27896 gcc/testsuite/gcc.dg/pr28712.c 0f5d0ea66f65798abba5fa2cc198c910 gcc/testsuite/gcc.dg/pr28726.c + a0dfbf73790362d18d55550373fe12b6 gcc/testsuite/gcc.dg/pr28796-1.c + 0046877724d70707323198d18406a1da gcc/testsuite/gcc.dg/pr28796-2.c 779db5f723f6a79c6be21e7b2b8012ba gcc/testsuite/gcc.dg/pr28839.c e8c37d720ed122aba160a22c70b198ac gcc/testsuite/gcc.dg/pr28888.c ca06792b688f53956ed815725a0335e8 gcc/testsuite/gcc.dg/pr28911.c d0e97ea1d56239299a14668f6dce570b gcc/testsuite/gcc.dg/pr28935.c fa5c8aebace3e5a4d550811e31ea349b gcc/testsuite/gcc.dg/pr29091.c ! edd66cac2bfded4fef1f06a475a9bdac gcc/testsuite/gcc.dg/pr29254.c 161eff1fb461cde37dc4b366730b1d6d gcc/testsuite/gcc.dg/pr29299.c d5763ed115978d48b488b6f1cc01cfe9 gcc/testsuite/gcc.dg/pr29330.c f1e44da34ca91b1612fcd1cabc5ab5b3 gcc/testsuite/gcc.dg/pr29581-1.c *************** b137bd663dec3939cc84b218db9e163b gcc/te *** 17302,17307 **** --- 17344,17353 ---- 94df861bd4c5add00dc383dc9e638b1c gcc/testsuite/gcc.dg/pr32450.c 11d491a6e08e1972d2394481024e644c gcc/testsuite/gcc.dg/pr32912-1.c 9a03c8496e9bf8af73734f0ac1076fdc gcc/testsuite/gcc.dg/pr32912-2.c + 544f0999d7a5be9daa161485ac791102 gcc/testsuite/gcc.dg/pr33826.c + 7afabd1a5ebe90ffc4d586806392a5ef gcc/testsuite/gcc.dg/pr34003-1.c + e1e3e91fd38a1ce34ce2e947ff49accb gcc/testsuite/gcc.dg/pr34003-2.c + 1afc1c341ec098c5b1e39b5175972b11 gcc/testsuite/gcc.dg/pr34174-1.c 3d08410b2dd57259aa63f0e1c64b376e gcc/testsuite/gcc.dg/pr8788-1.c 49409fb9111f01e98641b341056e15c6 gcc/testsuite/gcc.dg/pr8927-1.c 3825638bdc3a2a004aba9b3d95352327 gcc/testsuite/gcc.dg/pr9365-1.c *************** d964e9c3d529c43e9ae498a35fdf5775 gcc/te *** 17450,17455 **** --- 17496,17502 ---- 0986d290d402950e77d607406eefd46e gcc/testsuite/gcc.dg/struct-parse-1.c 71292c55dd1485a06682c239f2a42f0a gcc/testsuite/gcc.dg/struct-ret-1.c 75f0ab76aad50d990bf2113b93b3fbea gcc/testsuite/gcc.dg/struct-ret-2.c + bb0209154dca405a17a7cf2a64a3e176 gcc/testsuite/gcc.dg/struct-ret-3.c 765a678087a365e079632bb3e65e37d4 gcc/testsuite/gcc.dg/struct-ret-libc.c b395e1fd82ba2ecd040d7df5a10e4f26 gcc/testsuite/gcc.dg/struct-semi-1.c d416a52e3a0f366d984c22f7c57f08a6 gcc/testsuite/gcc.dg/struct-semi-2.c *************** af880fd7ebbdfbb729ee37825f5025fe gcc/te *** 17593,17598 **** --- 17640,17646 ---- 51df53c1b7cb0aa6bc2ea8d99040237a gcc/testsuite/gcc.dg/torture/pr30364-1.c 2d94b1ef317322ed352055416171e51b gcc/testsuite/gcc.dg/torture/pr30364-2.c c079abf84672f70737a6d273e95e0f08 gcc/testsuite/gcc.dg/torture/pr30364-3.c + 1dd47e2aa44e1c22e60b0d209862f5ea gcc/testsuite/gcc.dg/torture/pr33848.c d870c565ecc3624fb4fbcb1510c36484 gcc/testsuite/gcc.dg/torture/tree-loop-1.c 36de78b1e0dee582fcda7292901df258 gcc/testsuite/gcc.dg/trampoline-1.c 6d50839b8de376e357caa647c5713316 gcc/testsuite/gcc.dg/transparent-union-1.c *************** fe4d77243db6adfc8ac770e580ccf037 gcc/te *** 17622,17628 **** 25a6fe9c58987eea0de5e8c176beeec8 gcc/testsuite/gcc.dg/tree-ssa/20030711-1.c 2a41a0df036e3c2179f676ff0af9ae43 gcc/testsuite/gcc.dg/tree-ssa/20030711-2.c 7073ea58fbbee855b92e3cb63dd7387b gcc/testsuite/gcc.dg/tree-ssa/20030711-3.c ! 7a838a4110c0140ce4fce12282c6820d gcc/testsuite/gcc.dg/tree-ssa/20030714-1.c 814f77f173e73a4c135e681a08c162f5 gcc/testsuite/gcc.dg/tree-ssa/20030714-2.c 6f78c6ee1aeba3f64403762efc5766e6 gcc/testsuite/gcc.dg/tree-ssa/20030728-1.c 227900d9c56ccd16fafdcf63d6ff451c gcc/testsuite/gcc.dg/tree-ssa/20030729-1.c --- 17670,17676 ---- 25a6fe9c58987eea0de5e8c176beeec8 gcc/testsuite/gcc.dg/tree-ssa/20030711-1.c 2a41a0df036e3c2179f676ff0af9ae43 gcc/testsuite/gcc.dg/tree-ssa/20030711-2.c 7073ea58fbbee855b92e3cb63dd7387b gcc/testsuite/gcc.dg/tree-ssa/20030711-3.c ! 9aeaeac5f08b0b79b1488f602ec92611 gcc/testsuite/gcc.dg/tree-ssa/20030714-1.c 814f77f173e73a4c135e681a08c162f5 gcc/testsuite/gcc.dg/tree-ssa/20030714-2.c 6f78c6ee1aeba3f64403762efc5766e6 gcc/testsuite/gcc.dg/tree-ssa/20030728-1.c 227900d9c56ccd16fafdcf63d6ff451c gcc/testsuite/gcc.dg/tree-ssa/20030729-1.c *************** b442bff76932567fa8623be9c295e028 gcc/te *** 17801,17810 **** ab7b2a63365850db570957bed19564f1 gcc/testsuite/gcc.dg/tree-ssa/loadpre22.c 313479c39265e4c3a43ec145b5e82bcb gcc/testsuite/gcc.dg/tree-ssa/loadpre3.c ec072eed09216f7b36f2dd685fa136b3 gcc/testsuite/gcc.dg/tree-ssa/loadpre4.c ! 37cd5134fb61d3e9fd30624821f8e941 gcc/testsuite/gcc.dg/tree-ssa/loadpre5.c 91b29a283f52f5a2c5c8e5ea509ac90d gcc/testsuite/gcc.dg/tree-ssa/loadpre6.c 67a3a5e81e75a062881030b789cc1edd gcc/testsuite/gcc.dg/tree-ssa/loadpre7.c ! 84efc61b240a158d99ec4d6a1a3e968e gcc/testsuite/gcc.dg/tree-ssa/loadpre8.c 67d6a0b1852bc2a0c41b74d786851cd1 gcc/testsuite/gcc.dg/tree-ssa/loop-1.c a20b82d50cecd650ee2d79ab5f30afb6 gcc/testsuite/gcc.dg/tree-ssa/loop-10.c 2397e463b954e4ab2a6dba26099cddc1 gcc/testsuite/gcc.dg/tree-ssa/loop-11.c --- 17849,17858 ---- ab7b2a63365850db570957bed19564f1 gcc/testsuite/gcc.dg/tree-ssa/loadpre22.c 313479c39265e4c3a43ec145b5e82bcb gcc/testsuite/gcc.dg/tree-ssa/loadpre3.c ec072eed09216f7b36f2dd685fa136b3 gcc/testsuite/gcc.dg/tree-ssa/loadpre4.c ! d4dfbcb17eb35ddc89a7eeab0050a30e gcc/testsuite/gcc.dg/tree-ssa/loadpre5.c 91b29a283f52f5a2c5c8e5ea509ac90d gcc/testsuite/gcc.dg/tree-ssa/loadpre6.c 67a3a5e81e75a062881030b789cc1edd gcc/testsuite/gcc.dg/tree-ssa/loadpre7.c ! bf14458245eeca13cf12674c608f4b71 gcc/testsuite/gcc.dg/tree-ssa/loadpre8.c 67d6a0b1852bc2a0c41b74d786851cd1 gcc/testsuite/gcc.dg/tree-ssa/loop-1.c a20b82d50cecd650ee2d79ab5f30afb6 gcc/testsuite/gcc.dg/tree-ssa/loop-10.c 2397e463b954e4ab2a6dba26099cddc1 gcc/testsuite/gcc.dg/tree-ssa/loop-11.c *************** eb9c1311998bc6254de2257d8b81b708 gcc/te *** 17813,17822 **** dbcf8238ea96138e49a0ac7641c0037f gcc/testsuite/gcc.dg/tree-ssa/loop-16.c 692623f0ff4512d7053a4588f058a67c gcc/testsuite/gcc.dg/tree-ssa/loop-17.c 07c6f151734702cc3cad422f9c212f43 gcc/testsuite/gcc.dg/tree-ssa/loop-18.c ! c274c0c1ac07d02b551cab41a459d491 gcc/testsuite/gcc.dg/tree-ssa/loop-19.c 5eccaa1fa115a69ac4de124179dfd766 gcc/testsuite/gcc.dg/tree-ssa/loop-2.c 2638caccdf3d2e055ed3ba3b65572ef1 gcc/testsuite/gcc.dg/tree-ssa/loop-20.c ! 0ebe46127cdc105e26c0fed596a4c4a5 gcc/testsuite/gcc.dg/tree-ssa/loop-3.c 0375640d1c5c7d00918e8431e355828d gcc/testsuite/gcc.dg/tree-ssa/loop-4.c 25a7902a50a8278cbb4968e662ac92d4 gcc/testsuite/gcc.dg/tree-ssa/loop-5.c 095cb95a63149add48ddb64e9602ea8e gcc/testsuite/gcc.dg/tree-ssa/loop-6.c --- 17861,17870 ---- dbcf8238ea96138e49a0ac7641c0037f gcc/testsuite/gcc.dg/tree-ssa/loop-16.c 692623f0ff4512d7053a4588f058a67c gcc/testsuite/gcc.dg/tree-ssa/loop-17.c 07c6f151734702cc3cad422f9c212f43 gcc/testsuite/gcc.dg/tree-ssa/loop-18.c ! 9b186f4c02afa016a3ee82103576c6e6 gcc/testsuite/gcc.dg/tree-ssa/loop-19.c 5eccaa1fa115a69ac4de124179dfd766 gcc/testsuite/gcc.dg/tree-ssa/loop-2.c 2638caccdf3d2e055ed3ba3b65572ef1 gcc/testsuite/gcc.dg/tree-ssa/loop-20.c ! 5f7dcb96335babc92f47e49c3f621bed gcc/testsuite/gcc.dg/tree-ssa/loop-3.c 0375640d1c5c7d00918e8431e355828d gcc/testsuite/gcc.dg/tree-ssa/loop-4.c 25a7902a50a8278cbb4968e662ac92d4 gcc/testsuite/gcc.dg/tree-ssa/loop-5.c 095cb95a63149add48ddb64e9602ea8e gcc/testsuite/gcc.dg/tree-ssa/loop-6.c *************** d1b86f5e6ac8c7113d7830755fe5dd01 gcc/te *** 17926,17931 **** --- 17974,17980 ---- 1d5d7a36026dd194a0e407d0531c5df5 gcc/testsuite/gcc.dg/tree-ssa/pr27781.c 86fe38e2176f3e0ac19a7f6d1d1fde86 gcc/testsuite/gcc.dg/tree-ssa/pr28410.c f5de7ca48e45fa07564a59ee1e11e628 gcc/testsuite/gcc.dg/tree-ssa/pr31966.c + 9937232fcfc497ab921b9b542b61e1db gcc/testsuite/gcc.dg/tree-ssa/pr33714.c 1308402259df43bc62a12a140a85edd8 gcc/testsuite/gcc.dg/tree-ssa/pta-fp.c 352d7dea1ea1592106214f1b7e49f869 gcc/testsuite/gcc.dg/tree-ssa/reassoc-1.c b377fb4c31906d65575445e72a020475 gcc/testsuite/gcc.dg/tree-ssa/reassoc-10.c *************** c6005f208bd52ddbcfe313a6eee2bdf9 gcc/te *** 18148,18153 **** --- 18197,18203 ---- 566df733f0bacf93dfac3fb773125579 gcc/testsuite/gcc.dg/vect/pr25413a.c 0a3b12235a37e6d1f5e960368776d7ba gcc/testsuite/gcc.dg/vect/pr27151.c 0bae89d3a1a0e6a8b5c396322f679388 gcc/testsuite/gcc.dg/vect/pr28952.c + 2cad6423cfe40a5c8bb14f6ed407cdbe gcc/testsuite/gcc.dg/vect/pr33369.c 0706a6b1e589668022cd055b960dd18d gcc/testsuite/gcc.dg/vect/section-anchors-pr27770.c adb16856fa65b43291c83096b3538800 gcc/testsuite/gcc.dg/vect/section-anchors-vect-69.c 38653ea337561bdc3facb737a4d31ce5 gcc/testsuite/gcc.dg/vect/trapv-vect-reduc-4.c *************** ffc64e916f7d29e08d6398ca928ccee4 gcc/te *** 18276,18282 **** fd0cc4ec8bf1c73a32089a2c01823b69 gcc/testsuite/gcc.dg/vect/vect-ifcvt-5.c c2e8f59f6567847e6b16b110468e5732 gcc/testsuite/gcc.dg/vect/vect-ifcvt-6.c 9f2bb901451d9f53fd5521daee7a3fe3 gcc/testsuite/gcc.dg/vect/vect-ifcvt-7.c ! 9598f4e8250f9eeca9799022fdb55049 gcc/testsuite/gcc.dg/vect/vect-ifcvt-9.c aeedd7475fcd3ff3e15672d73b8be20d gcc/testsuite/gcc.dg/vect/vect-recip.c 8609778490e019c523231aeab59ae494 gcc/testsuite/gcc.dg/vect/vect-reduc-1.c 7bcbbbf10ad3817c6d9270e35bec2474 gcc/testsuite/gcc.dg/vect/vect-reduc-1char.c --- 18326,18332 ---- fd0cc4ec8bf1c73a32089a2c01823b69 gcc/testsuite/gcc.dg/vect/vect-ifcvt-5.c c2e8f59f6567847e6b16b110468e5732 gcc/testsuite/gcc.dg/vect/vect-ifcvt-6.c 9f2bb901451d9f53fd5521daee7a3fe3 gcc/testsuite/gcc.dg/vect/vect-ifcvt-7.c ! 23fe6592bb4a0d3f1605d236dfdd958d gcc/testsuite/gcc.dg/vect/vect-ifcvt-9.c aeedd7475fcd3ff3e15672d73b8be20d gcc/testsuite/gcc.dg/vect/vect-recip.c 8609778490e019c523231aeab59ae494 gcc/testsuite/gcc.dg/vect/vect-reduc-1.c 7bcbbbf10ad3817c6d9270e35bec2474 gcc/testsuite/gcc.dg/vect/vect-reduc-1char.c *************** e09aee999f6555d054fbc943434e9e4e gcc/te *** 18737,18743 **** 24b74aeb573670bebe702939cddf8159 gcc/testsuite/gcc.target/i386/pr19236-1.c 5195656eeba8721ee73be40d2f471bc5 gcc/testsuite/gcc.target/i386/pr20204.c fdacb6b61a5d36e161500b14166654ae gcc/testsuite/gcc.target/i386/pr21101.c ! fb5ac9503ce60bf2d3106e1e1e07ea98 gcc/testsuite/gcc.target/i386/pr21291.c e41aa30b7c11d3abfaec9393cd5ffb83 gcc/testsuite/gcc.target/i386/pr21518.c 036875bffbf4f4acfbb2f1daa06251d4 gcc/testsuite/gcc.target/i386/pr22362.c da34aa28d537d18fc2a008104a8373ff gcc/testsuite/gcc.target/i386/pr22432.c --- 18787,18793 ---- 24b74aeb573670bebe702939cddf8159 gcc/testsuite/gcc.target/i386/pr19236-1.c 5195656eeba8721ee73be40d2f471bc5 gcc/testsuite/gcc.target/i386/pr20204.c fdacb6b61a5d36e161500b14166654ae gcc/testsuite/gcc.target/i386/pr21101.c ! d2ce227f0da77e75ad621d94d75b7630 gcc/testsuite/gcc.target/i386/pr21291.c e41aa30b7c11d3abfaec9393cd5ffb83 gcc/testsuite/gcc.target/i386/pr21518.c 036875bffbf4f4acfbb2f1daa06251d4 gcc/testsuite/gcc.target/i386/pr22362.c da34aa28d537d18fc2a008104a8373ff gcc/testsuite/gcc.target/i386/pr22432.c *************** eefea3f3d3ef9a6ff440c58ee4f46894 gcc/te *** 18765,18772 **** 5f4936c9d4c31140f8ee0ea81c6aa658 gcc/testsuite/gcc.target/i386/pr28946.c 0f4e92fcabda2716e94caf9bca07a76a gcc/testsuite/gcc.target/i386/pr30505.c cc7150857198a660bd08df2767715c77 gcc/testsuite/gcc.target/i386/pr30848.c ! d2eb48a8bccdeac37bcfffa37233d3eb gcc/testsuite/gcc.target/i386/pr31167.c 5f2adfec27ee687fd53e8aad0152cc9d gcc/testsuite/gcc.target/i386/pr32389.c 7fd617aaf0d7ee1e3c720b9780d5b2c9 gcc/testsuite/gcc.target/i386/pr9771-1.c 02adbe6793bd8331bb32af90439f574f gcc/testsuite/gcc.target/i386/regparm-stdcall.c 818b9820fac6e68cc6ff88e4a09ef005 gcc/testsuite/gcc.target/i386/regparm.c --- 18815,18825 ---- 5f4936c9d4c31140f8ee0ea81c6aa658 gcc/testsuite/gcc.target/i386/pr28946.c 0f4e92fcabda2716e94caf9bca07a76a gcc/testsuite/gcc.target/i386/pr30505.c cc7150857198a660bd08df2767715c77 gcc/testsuite/gcc.target/i386/pr30848.c ! 8cf310be658f288c68cc180b99640d56 gcc/testsuite/gcc.target/i386/pr31167.c 5f2adfec27ee687fd53e8aad0152cc9d gcc/testsuite/gcc.target/i386/pr32389.c + 10dc3d7f8f6698d02fa13e80847ac4a7 gcc/testsuite/gcc.target/i386/pr32961.c + e9cdc80fa02a4b7ad68dd49b31747716 gcc/testsuite/gcc.target/i386/pr33483.c + e877f9f4074c57905dcfb34dcb608584 gcc/testsuite/gcc.target/i386/pr34215.c 7fd617aaf0d7ee1e3c720b9780d5b2c9 gcc/testsuite/gcc.target/i386/pr9771-1.c 02adbe6793bd8331bb32af90439f574f gcc/testsuite/gcc.target/i386/regparm-stdcall.c 818b9820fac6e68cc6ff88e4a09ef005 gcc/testsuite/gcc.target/i386/regparm.c *************** f0c62ee7d319e56cb75bc857ffbf1485 gcc/te *** 18832,18838 **** 28237801b0fe47a878cafab680acf4d4 gcc/testsuite/gcc.target/i386/ssetype-3.c 5f393f414c97d158b6bd7f1f91da4e1c gcc/testsuite/gcc.target/i386/ssetype-4.c a425bf2ee5b842d4fe0792cf7d96d8b2 gcc/testsuite/gcc.target/i386/ssetype-5.c ! 127e416b4192187bb6e478ce1b1311e8 gcc/testsuite/gcc.target/i386/stack-prot-kernel.c 5adc41b6e41ba8b2fda9e3963579a109 gcc/testsuite/gcc.target/i386/tailcall-1.c e0e22f97d420eb10eb73db8b27d21601 gcc/testsuite/gcc.target/i386/unordcmp-1.c d7b2ab8de6a5e64237f5fc10401d91fd gcc/testsuite/gcc.target/i386/unroll-1.c --- 18885,18891 ---- 28237801b0fe47a878cafab680acf4d4 gcc/testsuite/gcc.target/i386/ssetype-3.c 5f393f414c97d158b6bd7f1f91da4e1c gcc/testsuite/gcc.target/i386/ssetype-4.c a425bf2ee5b842d4fe0792cf7d96d8b2 gcc/testsuite/gcc.target/i386/ssetype-5.c ! 457872369f618fcecff3013f3f831699 gcc/testsuite/gcc.target/i386/stack-prot-kernel.c 5adc41b6e41ba8b2fda9e3963579a109 gcc/testsuite/gcc.target/i386/tailcall-1.c e0e22f97d420eb10eb73db8b27d21601 gcc/testsuite/gcc.target/i386/unordcmp-1.c d7b2ab8de6a5e64237f5fc10401d91fd gcc/testsuite/gcc.target/i386/unroll-1.c *************** dd7c1c9a78e9bb7129d4bdcd91042339 gcc/te *** 18911,18916 **** --- 18964,18970 ---- 3e120d6dbcd56034eb944ee947d181d1 gcc/testsuite/gcc.target/mips/nmadd-3.c 87d4c469731c0ed002f9b7975eeb5680 gcc/testsuite/gcc.target/mips/pr26765.c 1fe2f18f55c14eb7206465436ced9543 gcc/testsuite/gcc.target/mips/pr33256.c + aef1802a049536a5fab5a3ed55d9c9db gcc/testsuite/gcc.target/mips/pr33755.c a4205e0d19e7a55c8731d1c45fd5f589 gcc/testsuite/gcc.target/mips/rsqrt-1.c 39feb4b4c670f17a67616a81db99cf7f gcc/testsuite/gcc.target/mips/rsqrt-2.c 782befc6970d12ac82f92f954aa2505c gcc/testsuite/gcc.target/mips/rsqrt-3.c *************** a2f7ce24b5562fcd72891f0218c48b93 gcc/te *** 20250,20255 **** --- 20304,20310 ---- 3fba4c981425f50410a2588d3dd3519d gcc/testsuite/gfortran.dg/mclock.f90 0039aa87d8c7bb33fdd7971da66f6212 gcc/testsuite/gfortran.dg/merge_char_1.f90 eeec051d497127f1ede77e4c9b0a4d06 gcc/testsuite/gfortran.dg/merge_char_const.f90 + 4380697426c380b1d867806cc513e7b7 gcc/testsuite/gfortran.dg/minmaxloc_4.f90 bfce6907d55bac00c669263625b5989e gcc/testsuite/gfortran.dg/minmaxloc_integer_kinds_1.f90 eeff4329b1c35f17ea40d66d90ca6f5c gcc/testsuite/gfortran.dg/missing_derived_type_1.f90 3bf2bb643a8d0c12dd5796ef9a72dce1 gcc/testsuite/gfortran.dg/missing_optional_dummy_1.f90 *************** b379170f00f8cd3607cfaa09f4c14273 gcc/te *** 20985,20991 **** 9a908bb507989b82eddfeb9d23c66587 gcc/testsuite/lib/scantree.exp 0c533a0c449c2759f3aa0918776e6b02 gcc/testsuite/lib/target-libpath.exp 0008c7d8da165048f49dbf74c26b12b8 gcc/testsuite/lib/target-supports-dg.exp ! ac7f38df51ad967439c06d5cff54c4f2 gcc/testsuite/lib/target-supports.exp 0a31c8334c2563934919d1a16f7c026a gcc/testsuite/lib/treelang-dg.exp daef9de50ad42f1966ea7d4aaf39830a gcc/testsuite/lib/treelang.exp 9444024f1a4c0ae317cd233a228a4684 gcc/testsuite/lib/wrapper.exp --- 21040,21046 ---- 9a908bb507989b82eddfeb9d23c66587 gcc/testsuite/lib/scantree.exp 0c533a0c449c2759f3aa0918776e6b02 gcc/testsuite/lib/target-libpath.exp 0008c7d8da165048f49dbf74c26b12b8 gcc/testsuite/lib/target-supports-dg.exp ! 038ce98d3dfa852f21dfb085c0394c51 gcc/testsuite/lib/target-supports.exp 0a31c8334c2563934919d1a16f7c026a gcc/testsuite/lib/treelang-dg.exp daef9de50ad42f1966ea7d4aaf39830a gcc/testsuite/lib/treelang.exp 9444024f1a4c0ae317cd233a228a4684 gcc/testsuite/lib/wrapper.exp *************** bc09762b3e74fc0227216052a970a32c gcc/te *** 21395,21401 **** 318a61b0250e72af17f13433cbe7c899 gcc/testsuite/objc/execute/string3.m 745164878e340e7e3913196da0f9cbab gcc/testsuite/objc/execute/string4.m a15f4a807f9ba61e7f1f938b35d010a1 gcc/testsuite/objc/execute/va_method.m ! 5f89add25098abd01afad5a18eb70231 gcc/testsuite/treelang/ChangeLog 454cfe5b1bbbcf87f68aada2d6b8e61d gcc/testsuite/treelang/Makefile.in bf22e28b9aea9db69f316d07777d7eb0 gcc/testsuite/treelang/compile/autofunc.tree 9787b9901d0eae3abfa0a7279a68ca08 gcc/testsuite/treelang/compile/badchar.tree --- 21450,21456 ---- 318a61b0250e72af17f13433cbe7c899 gcc/testsuite/objc/execute/string3.m 745164878e340e7e3913196da0f9cbab gcc/testsuite/objc/execute/string4.m a15f4a807f9ba61e7f1f938b35d010a1 gcc/testsuite/objc/execute/va_method.m ! d7d669612137671e8b597092ebe2b9f7 gcc/testsuite/treelang/ChangeLog 454cfe5b1bbbcf87f68aada2d6b8e61d gcc/testsuite/treelang/Makefile.in bf22e28b9aea9db69f316d07777d7eb0 gcc/testsuite/treelang/compile/autofunc.tree 9787b9901d0eae3abfa0a7279a68ca08 gcc/testsuite/treelang/compile/badchar.tree *************** cf30b950ee68c9dfa4530a43a7906de7 gcc/tr *** 21487,21493 **** 82618a9a7db4c5a8b96513bf1c27211c gcc/tree-ssa-loop-ch.c dbe26cd6d78721ffb5f1695bd983c39d gcc/tree-ssa-loop-im.c b2ea72ae91a610d96dc342cef2d4faad gcc/tree-ssa-loop-ivcanon.c ! 6543eeeea51f2a2b21477bfc9e1e45ad gcc/tree-ssa-loop-ivopts.c a59ed73641cc755aa16df4239df8b38e gcc/tree-ssa-loop-manip.c 0aa250e5ccae8e6b5571e8c0499f19e6 gcc/tree-ssa-loop-niter.c de433ab49f03fc8ce6c7a2d56b07d0a3 gcc/tree-ssa-loop-prefetch.c --- 21542,21548 ---- 82618a9a7db4c5a8b96513bf1c27211c gcc/tree-ssa-loop-ch.c dbe26cd6d78721ffb5f1695bd983c39d gcc/tree-ssa-loop-im.c b2ea72ae91a610d96dc342cef2d4faad gcc/tree-ssa-loop-ivcanon.c ! 9007ee180e2f536d575c363161bae778 gcc/tree-ssa-loop-ivopts.c a59ed73641cc755aa16df4239df8b38e gcc/tree-ssa-loop-manip.c 0aa250e5ccae8e6b5571e8c0499f19e6 gcc/tree-ssa-loop-niter.c de433ab49f03fc8ce6c7a2d56b07d0a3 gcc/tree-ssa-loop-prefetch.c *************** a38a578a8e4b8ebfbf0cab9511f850a6 gcc/tr *** 21519,21529 **** 4b43a0c62ad152fd20971db2b9afd403 gcc/tree-vectorizer.c b5afc270de0461d3ae0f4eb9aa135eb4 gcc/tree-vectorizer.h 7dcbc0e9d766a076dbbee83a7bb3e2b4 gcc/tree-vn.c ! 152524f161f78eec9c8b6f0f647a4bfc gcc/tree-vrp.c ! fd132b1a71fd8a3670ef332cca6ec6e8 gcc/tree.c b8747a198b2c4781ca08b4c98fbec008 gcc/tree.def 42f0e46929d15c2d07bd4aa6b0d6fcd7 gcc/tree.h ! d4ef8d045c3168dde3f19e1a5c59f5e8 gcc/treelang/ChangeLog 5e5304fc67a1501c8a304c3ade86d5b2 gcc/treelang/Make-lang.in 760e83cfd90fc02bffdf85e5e4d77bb3 gcc/treelang/README cb01b09e1c2a2a12aa66eeaa76c9fc23 gcc/treelang/config-lang.in --- 21574,21584 ---- 4b43a0c62ad152fd20971db2b9afd403 gcc/tree-vectorizer.c b5afc270de0461d3ae0f4eb9aa135eb4 gcc/tree-vectorizer.h 7dcbc0e9d766a076dbbee83a7bb3e2b4 gcc/tree-vn.c ! d7ff44671a534816d593ffbfbd125ca2 gcc/tree-vrp.c ! 36baf624f22893db4b69f0b698741354 gcc/tree.c b8747a198b2c4781ca08b4c98fbec008 gcc/tree.def 42f0e46929d15c2d07bd4aa6b0d6fcd7 gcc/tree.h ! b5d8d1b688122d4cb250082973ff0352 gcc/treelang/ChangeLog 5e5304fc67a1501c8a304c3ade86d5b2 gcc/treelang/Make-lang.in 760e83cfd90fc02bffdf85e5e4d77bb3 gcc/treelang/README cb01b09e1c2a2a12aa66eeaa76c9fc23 gcc/treelang/config-lang.in *************** f8852006bde79749efa236459685796c gcc/un *** 21557,21563 **** 82b0d712db9ec479304edce656c1bdd9 gcc/unwind.inc 36a569df61cadb62071c269f6220bf49 gcc/value-prof.c 77bb176492759705d261f3f257766bf6 gcc/value-prof.h ! 703f3de36413c6af3d47eb877aa48f27 gcc/var-tracking.c e2d400f647ffe73f69b9c52c9392e3a6 gcc/varasm.c 08b840714ee860c5d1107d3ddecd9672 gcc/varray.c d8f94e35840190c4f1dc252fb9cde4de gcc/varray.h --- 21612,21618 ---- 82b0d712db9ec479304edce656c1bdd9 gcc/unwind.inc 36a569df61cadb62071c269f6220bf49 gcc/value-prof.c 77bb176492759705d261f3f257766bf6 gcc/value-prof.h ! 0210f953ce7da549375374965dcdd412 gcc/var-tracking.c e2d400f647ffe73f69b9c52c9392e3a6 gcc/varasm.c 08b840714ee860c5d1107d3ddecd9672 gcc/varray.c d8f94e35840190c4f1dc252fb9cde4de gcc/varray.h *************** c5b71effc6b256cb73e649404147eb64 gcc/we *** 21572,21583 **** 42adadee6c316f624c86e3ccfdeee75c gcc/xcoff.h a0ca3379f7fb3ba42222ce87f9bff867 gcc/xcoffout.c 8c56db5e59eea9e7c72612f05785cce6 gcc/xcoffout.h ! 448ec9217b9850df607ebe364d595a3e gnattools/ChangeLog bf322489e2c621fc702f38efe8d8bdfe gnattools/Makefile.in 48213afdf8ef31ddcd83f58d74f8d524 gnattools/configure 8440f201742266e5f9c05547e86918f9 gnattools/configure.ac 59530bdf33659b29e73d4adb9f9f6552 include/COPYING ! dd6e645139e26dab7242d5f7962436c7 include/ChangeLog 24516b717009640ce59780ea65675d4f include/ChangeLog-9103 e1083a1fae50362cefde0b1f620e9401 include/ansidecl.h 46133b8d5031d2bfbdbfd59dec89822b include/demangle.h --- 21627,21638 ---- 42adadee6c316f624c86e3ccfdeee75c gcc/xcoff.h a0ca3379f7fb3ba42222ce87f9bff867 gcc/xcoffout.c 8c56db5e59eea9e7c72612f05785cce6 gcc/xcoffout.h ! 62541553c5ea7d75d4cea8dc796c1570 gnattools/ChangeLog bf322489e2c621fc702f38efe8d8bdfe gnattools/Makefile.in 48213afdf8ef31ddcd83f58d74f8d524 gnattools/configure 8440f201742266e5f9c05547e86918f9 gnattools/configure.ac 59530bdf33659b29e73d4adb9f9f6552 include/COPYING ! e90ed2996c954425105baa75548ab4b0 include/ChangeLog 24516b717009640ce59780ea65675d4f include/ChangeLog-9103 e1083a1fae50362cefde0b1f620e9401 include/ansidecl.h 46133b8d5031d2bfbdbfd59dec89822b include/demangle.h *************** bbf5a6a7b70efde41e703f72d9732f81 includ *** 21602,21608 **** 0294cecbb1f66d640ccba3a5d862d05b include/xregex2.h 33d7d862df35bdf707fd756625638e7f include/xtensa-config.h aded5875c5d5830de6653181e8ced19c install-sh ! 9e3065a2fbdb2c030bdd81ed79e1ffca intl/ChangeLog d2413516bb4932a3f3a3642164ac38f8 intl/Makefile.in 6ec998bb4716c744bf8185e607f69301 intl/README 76ca170a525d5b84d90f0478fe788931 intl/VERSION --- 21657,21663 ---- 0294cecbb1f66d640ccba3a5d862d05b include/xregex2.h 33d7d862df35bdf707fd756625638e7f include/xtensa-config.h aded5875c5d5830de6653181e8ced19c install-sh ! e2723197eb172491a729580e9055795a intl/ChangeLog d2413516bb4932a3f3a3642164ac38f8 intl/Makefile.in 6ec998bb4716c744bf8185e607f69301 intl/README 76ca170a525d5b84d90f0478fe788931 intl/VERSION *************** d50a8c6c5b41089930accbdce767d3c0 intl/p *** 21644,21654 **** b4758a0194e3e41362b939911472ce62 intl/relocatable.c bedade7bcfc3bc5eb09a2c6844f637f3 intl/relocatable.h 43f287d082528203fc85c1d2d81bf30d intl/textdomain.c ! 9e98cb4dbe190aca641860b9ff3df654 libada/ChangeLog dd921be69ee11ae6da2c853310750230 libada/Makefile.in 2cb2fd3fee4a620a3d3896a05e2924db libada/configure 0e6eee9ef33cbe4c3e9c2454ed64fa59 libada/configure.ac ! 152d8e2399a213de263f8ea66a800f67 libcpp/ChangeLog 2bda77fdd8cc2895a8c619fb7a6e8de4 libcpp/Makefile.in 647f30740ad5a45cc52fdcd1751083bf libcpp/aclocal.m4 eb7be65bab396bc84b16e705dd8a0710 libcpp/charset.c --- 21699,21709 ---- b4758a0194e3e41362b939911472ce62 intl/relocatable.c bedade7bcfc3bc5eb09a2c6844f637f3 intl/relocatable.h 43f287d082528203fc85c1d2d81bf30d intl/textdomain.c ! eacc47669ad95a2a81b0344f8f554729 libada/ChangeLog dd921be69ee11ae6da2c853310750230 libada/Makefile.in 2cb2fd3fee4a620a3d3896a05e2924db libada/configure 0e6eee9ef33cbe4c3e9c2454ed64fa59 libada/configure.ac ! 9ac395ee5e031b8bfe3dca68152d4de6 libcpp/ChangeLog 2bda77fdd8cc2895a8c619fb7a6e8de4 libcpp/Makefile.in 647f30740ad5a45cc52fdcd1751083bf libcpp/aclocal.m4 eb7be65bab396bc84b16e705dd8a0710 libcpp/charset.c *************** bd3ad232a81e8a65301172800949c9b8 libcpp *** 21674,21719 **** f534edcdcc5f5c162170f3c205980359 libcpp/makeucnid.c ac4b591a13a5571e94feae523a15c8ec libcpp/mkdeps.c 164388d30ab16a17dbe92c50920628a3 libcpp/pch.c ! dc3e7f89d33b8e531a9a9303117c0dd4 libcpp/po/ChangeLog ! de64aab40d63575b36741f7f0afb6836 libcpp/po/be.gmo ! 21903341bd9f993cb16f2da58242037e libcpp/po/be.po ! 3468550099db7ed261d1a6dafe02c0c0 libcpp/po/ca.gmo ! 116fcad1ee607bfa160c36a8db5b1215 libcpp/po/ca.po 9edcd6485901ca564c971a68fcc354a1 libcpp/po/cpplib.pot ! 62c2a997368bc71e23dc77b6af29ab41 libcpp/po/da.gmo ! 4f05fa34be51ddb35dc61218fa5954d2 libcpp/po/da.po ! df4d3883b5b9a07000da75b4d97e73e6 libcpp/po/de.gmo ! 5a2e2a68c397a5ce77c818d17ca8346d libcpp/po/de.po ! aaff45d8ddccc893037e74734492741b libcpp/po/el.gmo ! c489f058ce2c61e192b99d49b5c617bd libcpp/po/el.po ! 0c44dd429dc36924d99fb69324a9e91d libcpp/po/es.gmo ! 383707b9ad70703cb32825559fb61ea9 libcpp/po/es.po ! 3e8b2a03fe70ef19b79e2606eb6c2a61 libcpp/po/fr.gmo ! 89558ce3cd6e0bc8820cf2b619504a39 libcpp/po/fr.po ! 4c62eab1014bc064fcfe6c72aea2a917 libcpp/po/ja.gmo ! 253fbeddf96e32fd5115864d33fae47e libcpp/po/ja.po ! afebb0c0cfdf4f4678fe8efd8c8e8634 libcpp/po/nl.gmo ! 02b19a3bdd305e53826bc13c0fdbea5e libcpp/po/nl.po 43164bee81e71450b5e3bbf0b7548751 libcpp/po/rw.gmo 57481eade3cd0b05423387a6f0c05c5c libcpp/po/rw.po ! d083762d30c5e7d91f7db70e8b9d1db8 libcpp/po/sv.gmo ! e318237d2cb1e8115198f349c5a04fb8 libcpp/po/sv.po ! bcf70d3f84567b0e43341e67bcc700c9 libcpp/po/tr.gmo ! 5eec002e221611d314c238b9ac0d0eca libcpp/po/tr.po ! 43941e09b4899997ae318b6c7a8cf975 libcpp/po/uk.gmo ! d93cf2ac0aaeb59f4bbd9cfc4c07def8 libcpp/po/uk.po ! 5baf5aa2c91629d4cd5e58ce3987b564 libcpp/po/vi.gmo ! b9b83183b160c2d055dd049b9c5b171e libcpp/po/vi.po ! 4050b6209093f5f893ed938d650d0df2 libcpp/po/zh_CN.gmo ! c5e2141d0d581c6118c37ea662bdd93f libcpp/po/zh_CN.po ! f95fe6d4001ccc34f4ee083975d88752 libcpp/po/zh_TW.gmo ! e07e06a05815edd4b5f1453c2be5aa3c libcpp/po/zh_TW.po e748b11a8760b4a8717f37cd32b26eae libcpp/symtab.c 8a10d329d58f963bbc22146326cf8ba4 libcpp/system.h b940e25481e4fb146a808c2d2f9f44cf libcpp/traditional.c 273f6edd239910923af1435d8fef46fc libcpp/ucnid.h 62b01578743d74de9c0d15087276717c libcpp/ucnid.tab ! 91a92785f09d8d99373e30c794849472 libdecnumber/ChangeLog dacc4dd675dc516b8d824db778c8a2bb libdecnumber/Makefile.in 47adaf56dc02dd44a284b4ac78d55d75 libdecnumber/aclocal.m4 547bc9e012848a23219b22c0137d508d libdecnumber/config.in --- 21729,21774 ---- f534edcdcc5f5c162170f3c205980359 libcpp/makeucnid.c ac4b591a13a5571e94feae523a15c8ec libcpp/mkdeps.c 164388d30ab16a17dbe92c50920628a3 libcpp/pch.c ! fc5c21afb080a84c11a35fac42d0138a libcpp/po/ChangeLog ! fe191c98f1e423cca395dee328370eaa libcpp/po/be.gmo ! ca84b7e9849e7637939e90eaa9d1b92e libcpp/po/be.po ! 2813f7cb5930f17dc59c7ba7fb8b764e libcpp/po/ca.gmo ! 679e129ae84b71696a1f1e773d46f3c1 libcpp/po/ca.po 9edcd6485901ca564c971a68fcc354a1 libcpp/po/cpplib.pot ! 18480ec386767b306d5b2f6dd7ba35c8 libcpp/po/da.gmo ! d02956ac68c35386a6263309ee64df13 libcpp/po/da.po ! 711b9195f3ac99a7c26efa271786dd09 libcpp/po/de.gmo ! a12e8e2d9dfc62c43acf1cb9efff593c libcpp/po/de.po ! 486af0e348338dc7c2a1530e801d2f4c libcpp/po/el.gmo ! 132a8d2f89d4c18878986c738c816148 libcpp/po/el.po ! 2e4c159869e45dcfd7f3afe7af41e240 libcpp/po/es.gmo ! b536134cc0c0bf6c6d7e0f390a9e61bd libcpp/po/es.po ! 7c6aec21a381a9637a94bc104bdf35f8 libcpp/po/fr.gmo ! afffe78a88da236767fbe569c5653273 libcpp/po/fr.po ! fb474569ed833d4f55821b692e7e85b4 libcpp/po/ja.gmo ! 83aafb17b75e2c88d6663d0caeae0f91 libcpp/po/ja.po ! 0b5a815e9d85ae93dadcfbac739ea4c4 libcpp/po/nl.gmo ! 99c0c33acf18b3566c20d40f7dee7418 libcpp/po/nl.po 43164bee81e71450b5e3bbf0b7548751 libcpp/po/rw.gmo 57481eade3cd0b05423387a6f0c05c5c libcpp/po/rw.po ! 71cc66d6a34864b43e760968a991614e libcpp/po/sv.gmo ! 589e92bc3cb60efdbbae321722dcc8df libcpp/po/sv.po ! 03f5ec01ed9ccc2d6224e1dbb562fab1 libcpp/po/tr.gmo ! a11185d91518b487a9af46234ecb4169 libcpp/po/tr.po ! 82bb9d5a44558aaeb72f524dca15eb3c libcpp/po/uk.gmo ! cf4bf8228e63ab666ef233ef6f6589e8 libcpp/po/uk.po ! 81f43e4256c0f65256afebadcff22706 libcpp/po/vi.gmo ! 6192394e6b77a35b88a150cf7160d892 libcpp/po/vi.po ! aa18092b60bd9a79561eb39d52acd8f6 libcpp/po/zh_CN.gmo ! f805f91630ba3c822c1aed617e48754d libcpp/po/zh_CN.po ! 393f565a4bfda35d026507eb4e0b9cdb libcpp/po/zh_TW.gmo ! 98ea5d15b5601b715342c064d3b200bd libcpp/po/zh_TW.po e748b11a8760b4a8717f37cd32b26eae libcpp/symtab.c 8a10d329d58f963bbc22146326cf8ba4 libcpp/system.h b940e25481e4fb146a808c2d2f9f44cf libcpp/traditional.c 273f6edd239910923af1435d8fef46fc libcpp/ucnid.h 62b01578743d74de9c0d15087276717c libcpp/ucnid.tab ! 9309b30cef44e9162d5306e6d80bd4a9 libdecnumber/ChangeLog dacc4dd675dc516b8d824db778c8a2bb libdecnumber/Makefile.in 47adaf56dc02dd44a284b4ac78d55d75 libdecnumber/aclocal.m4 547bc9e012848a23219b22c0137d508d libdecnumber/config.in *************** e7dab10d5365fe50b7b18979900b1a1f libdec *** 21735,21741 **** 09023d69cf9eacedcbb102408d414d8d libdecnumber/decimal32.h 02d7f84386fb5d3a8cd2f4f094a76210 libdecnumber/decimal64.c b1f91891130bfe5dd564f35120a89297 libdecnumber/decimal64.h ! e347715054a03c0d3a00680e1001017d libffi/ChangeLog fbbc216bc25d759a72ea3e6d734af56b libffi/ChangeLog.libgcj d946d2b97454ad50a1dbfbf48923c5be libffi/ChangeLog.v1 085f9917800070e791f49bf4733e23fa libffi/LICENSE --- 21790,21796 ---- 09023d69cf9eacedcbb102408d414d8d libdecnumber/decimal32.h 02d7f84386fb5d3a8cd2f4f094a76210 libdecnumber/decimal64.c b1f91891130bfe5dd564f35120a89297 libdecnumber/decimal64.h ! 53930cfcfcc4810b08a44a85df9268c3 libffi/ChangeLog fbbc216bc25d759a72ea3e6d734af56b libffi/ChangeLog.libgcj d946d2b97454ad50a1dbfbf48923c5be libffi/ChangeLog.v1 085f9917800070e791f49bf4733e23fa libffi/LICENSE *************** c596ddb985689ec61b12aaa3d22affa3 libffi *** 21931,21937 **** b84890d83f011c1b342ba72165c5337b libffi/testsuite/libffi.special/ffitestcxx.h 92159904883229dd38630b1d0cee3534 libffi/testsuite/libffi.special/special.exp 4a689b7f495a16a376b392d5ea38282f libffi/testsuite/libffi.special/unwindtest.cc ! f24d3a41b7edb89a2377bcd7c980e428 libgfortran/ChangeLog 2c771a7b083f9d4ba381a572d357758a libgfortran/ChangeLog-2002 67e64c8bcbf53773807721aeb4785c9e libgfortran/ChangeLog-2003 375b728e07a8e59f37b93edc0164fc6b libgfortran/ChangeLog-2004 --- 21986,21992 ---- b84890d83f011c1b342ba72165c5337b libffi/testsuite/libffi.special/ffitestcxx.h 92159904883229dd38630b1d0cee3534 libffi/testsuite/libffi.special/special.exp 4a689b7f495a16a376b392d5ea38282f libffi/testsuite/libffi.special/unwindtest.cc ! 0cab6472747b917a61f90bb9df724742 libgfortran/ChangeLog 2c771a7b083f9d4ba381a572d357758a libgfortran/ChangeLog-2002 67e64c8bcbf53773807721aeb4785c9e libgfortran/ChangeLog-2003 375b728e07a8e59f37b93edc0164fc6b libgfortran/ChangeLog-2004 *************** a2fb7022fcf842544e40dabebea9f4ce libgfo *** 22382,22388 **** feb4a51f21dcf63e670dc45fde5fccaf libgfortran/intrinsics/args.c 3033b1ad392cdeded88b152f4f2132a0 libgfortran/intrinsics/associated.c 2515a1302ef85e6cb9810070b68cb5c9 libgfortran/intrinsics/bessel.c ! d5984f15ab7cbc8384dd8a9f8460fab1 libgfortran/intrinsics/c99_functions.c 00c33c97c4b20741dd97ef3e7c812436 libgfortran/intrinsics/chdir.c 0afe7f482a2d21ac5a7e3276a56d4b88 libgfortran/intrinsics/chmod.c 66b60d9aca69bea0f4bbb16f2c367b74 libgfortran/intrinsics/clock.c --- 22437,22443 ---- feb4a51f21dcf63e670dc45fde5fccaf libgfortran/intrinsics/args.c 3033b1ad392cdeded88b152f4f2132a0 libgfortran/intrinsics/associated.c 2515a1302ef85e6cb9810070b68cb5c9 libgfortran/intrinsics/bessel.c ! 3d4780a422f8d8627a7fffb7d55b2fdb libgfortran/intrinsics/c99_functions.c 00c33c97c4b20741dd97ef3e7c812436 libgfortran/intrinsics/chdir.c 0afe7f482a2d21ac5a7e3276a56d4b88 libgfortran/intrinsics/chmod.c 66b60d9aca69bea0f4bbb16f2c367b74 libgfortran/intrinsics/clock.c *************** b41c52478c55eb0e870aff4f6c83d1db libgfo *** 22507,22513 **** 0af1855586b82ce6abdc5bcbe4b4c8a7 libgfortran/runtime/select.c a11b58ce7b16ef6aa7b6594a0698cf8b libgfortran/runtime/stop.c 031105394d3c1f9a6286f4e4b3a3a123 libgfortran/runtime/string.c ! 70d8779146f4e4f99fed403e86b9773d libgomp/ChangeLog d44196f12a98d87c2e43173f2ec96a36 libgomp/Makefile.am 14b9e270d451fcfcb32f7c6ca4c0cc97 libgomp/Makefile.in f240afc042f089598063e6e9e3b33b8b libgomp/acinclude.m4 --- 22562,22568 ---- 0af1855586b82ce6abdc5bcbe4b4c8a7 libgfortran/runtime/select.c a11b58ce7b16ef6aa7b6594a0698cf8b libgfortran/runtime/stop.c 031105394d3c1f9a6286f4e4b3a3a123 libgfortran/runtime/string.c ! 86c210e318e4e534c52d15016629c21e libgomp/ChangeLog d44196f12a98d87c2e43173f2ec96a36 libgomp/Makefile.am 14b9e270d451fcfcb32f7c6ca4c0cc97 libgomp/Makefile.in f240afc042f089598063e6e9e3b33b8b libgomp/acinclude.m4 *************** db9319768899d2e746b7d7180cd6fe88 libgom *** 22542,22549 **** 9a4a3980e62b0601105c108a3f5d172f libgomp/config/posix/time.c 7ab7a3fdfa0b716ea93c06b5a1461e2d libgomp/config/posix95/lock.c c8b93287433a257100fec11bd6961226 libgomp/config/posix95/omp-lock.h ! ab29bcb50e9c1790bf6577cef98c0573 libgomp/configure ! 5fd6b1ccdb1ae7b2f43fff65011ede4e libgomp/configure.ac e1d5d1a2143d1658ced1f0a6b620a57b libgomp/configure.tgt 2234efc674b979ff0601f366ba6c38be libgomp/critical.c 4b927ad01e07ab426ba7ee4e890a98bf libgomp/env.c --- 22597,22604 ---- 9a4a3980e62b0601105c108a3f5d172f libgomp/config/posix/time.c 7ab7a3fdfa0b716ea93c06b5a1461e2d libgomp/config/posix95/lock.c c8b93287433a257100fec11bd6961226 libgomp/config/posix95/omp-lock.h ! 23b87dbe9294efec8b9ff4c27aaf3bd3 libgomp/configure ! 1ffa95af229152fc38f3d9c6c2fd8fb9 libgomp/configure.ac e1d5d1a2143d1658ced1f0a6b620a57b libgomp/configure.tgt 2234efc674b979ff0601f366ba6c38be libgomp/critical.c 4b927ad01e07ab426ba7ee4e890a98bf libgomp/env.c *************** e1d5d1a2143d1658ced1f0a6b620a57b libgom *** 22551,22557 **** f3855e00cf2e71145c033e8d3b0d86e1 libgomp/fortran.c 50eaad4d9eb22d4a8b7b7a1126f153a3 libgomp/iter.c 3e9f99d0d428de49a44861dda8b9c573 libgomp/libgomp.h ! 7b95b2321d2b0ca65404466efa1c18d1 libgomp/libgomp.info 89eb36d54b77f19545f66a3c7e60e9c3 libgomp/libgomp.map 591ff20dfd2b81e3c919249b5db8a967 libgomp/libgomp.spec.in 54badb2a99a769fab9d4033dda4e71cf libgomp/libgomp.texi --- 22606,22612 ---- f3855e00cf2e71145c033e8d3b0d86e1 libgomp/fortran.c 50eaad4d9eb22d4a8b7b7a1126f153a3 libgomp/iter.c 3e9f99d0d428de49a44861dda8b9c573 libgomp/libgomp.h ! f58ba64c53931c3ade1bacbe39996c1f libgomp/libgomp.info 89eb36d54b77f19545f66a3c7e60e9c3 libgomp/libgomp.map 591ff20dfd2b81e3c919249b5db8a967 libgomp/libgomp.spec.in 54badb2a99a769fab9d4033dda4e71cf libgomp/libgomp.texi *************** ee9b4e6286720c9e31c8afb5899375cf libgom *** 22779,22785 **** 10994954f2e9828dd2a982c245ff4a59 libgomp/testsuite/libgomp.fortran/workshare1.f90 a999cc9909607f39f1b668bed6f501bf libgomp/work.c a916467b91076e631dd8edb7424769c7 libiberty/COPYING.LIB ! 8572b42ea5df6b0451aa6c636512933c libiberty/ChangeLog ee0771d4c43eb53588ddb2c07b83f5ae libiberty/Makefile.in 294191545dc71f5ad13229b0a5bfd7b1 libiberty/README 8797cb1a6faa84f3c7fe3d12164a4b13 libiberty/_doprnt.c --- 22834,22840 ---- 10994954f2e9828dd2a982c245ff4a59 libgomp/testsuite/libgomp.fortran/workshare1.f90 a999cc9909607f39f1b668bed6f501bf libgomp/work.c a916467b91076e631dd8edb7424769c7 libiberty/COPYING.LIB ! 72aed34936f16d0b33e693dce80c9541 libiberty/ChangeLog ee0771d4c43eb53588ddb2c07b83f5ae libiberty/Makefile.in 294191545dc71f5ad13229b0a5bfd7b1 libiberty/README 8797cb1a6faa84f3c7fe3d12164a4b13 libiberty/_doprnt.c *************** cdc140ce93944c5bb2ac62cd3dfd86d6 libibe *** 22916,22922 **** 6f774a92661ca4a067f1691a7925524b libiberty/xstrerror.c c6e7ef53b4ff115a136d917511222656 libiberty/xstrndup.c 94d55d512a9ba36caa9b7df079bae19f libjava/COPYING ! 9c6820adcaca32bc3cd50be238fb4a1e libjava/ChangeLog 03e1f38b916604fdf1470238201325f3 libjava/ChangeLog-1998 691acb61fbd6a2235826ff55db5578be libjava/ChangeLog-1999 b58c6701706771a02bf00a77666941ef libjava/ChangeLog-2000 --- 22971,22977 ---- 6f774a92661ca4a067f1691a7925524b libiberty/xstrerror.c c6e7ef53b4ff115a136d917511222656 libiberty/xstrndup.c 94d55d512a9ba36caa9b7df079bae19f libjava/COPYING ! bb887bba3ec10d11415049d8c70739a4 libjava/ChangeLog 03e1f38b916604fdf1470238201325f3 libjava/ChangeLog-1998 691acb61fbd6a2235826ff55db5578be libjava/ChangeLog-1999 b58c6701706771a02bf00a77666941ef libjava/ChangeLog-2000 *************** efc33151e6f0752ce2b40ae21ab49671 libjav *** 22937,22943 **** ca8e9bd5d9f1286aa2a015ad029497c0 libjava/classpath/AUTHORS efd97e0bb913655e0c8b16fa78bdded4 libjava/classpath/BUGS af0004801732bc4b20d90f351cf80510 libjava/classpath/COPYING ! 5a053e60a9b3717269a30dc7e510ae9f libjava/classpath/ChangeLog 539139753b2aae955026b6567ec391ea libjava/classpath/ChangeLog-2003 a5b24de904ca628e02ef4e7aaee0378e libjava/classpath/ChangeLog-2004 8f19ed69c8956b521da218526390b21e libjava/classpath/ChangeLog-2005 --- 22992,22998 ---- ca8e9bd5d9f1286aa2a015ad029497c0 libjava/classpath/AUTHORS efd97e0bb913655e0c8b16fa78bdded4 libjava/classpath/BUGS af0004801732bc4b20d90f351cf80510 libjava/classpath/COPYING ! 1ebb66e9090fa7d83ab4986c0a03b5ec libjava/classpath/ChangeLog 539139753b2aae955026b6567ec391ea libjava/classpath/ChangeLog-2003 a5b24de904ca628e02ef4e7aaee0378e libjava/classpath/ChangeLog-2004 8f19ed69c8956b521da218526390b21e libjava/classpath/ChangeLog-2005 *************** f2364b7e150108abd0377346f5ec5ce7 libjav *** 29664,29670 **** 625fa2c816d6e6d17fb1082cde55bca1 libjava/java/lang/natFloat.cc 38f692d64cb2de9c49202f41d4392825 libjava/java/lang/natMath.cc cd3a737f2db795fb827d767120fffa58 libjava/java/lang/natObject.cc ! e7f3e507c6744bfd18cc86dbb389b6b3 libjava/java/lang/natPosixProcess.cc cea4d6e62960e0b6657de01207793c3a libjava/java/lang/natRuntime.cc 695d04605b79aec0f19e32e0dbf1bb2b libjava/java/lang/natString.cc 7c87f5acddd8589e59cea5b11b3e5db6 libjava/java/lang/natStringBuffer.cc --- 29719,29725 ---- 625fa2c816d6e6d17fb1082cde55bca1 libjava/java/lang/natFloat.cc 38f692d64cb2de9c49202f41d4392825 libjava/java/lang/natMath.cc cd3a737f2db795fb827d767120fffa58 libjava/java/lang/natObject.cc ! 6bedf44fc26ca44b64392f821dba0a32 libjava/java/lang/natPosixProcess.cc cea4d6e62960e0b6657de01207793c3a libjava/java/lang/natRuntime.cc 695d04605b79aec0f19e32e0dbf1bb2b libjava/java/lang/natString.cc 7c87f5acddd8589e59cea5b11b3e5db6 libjava/java/lang/natStringBuffer.cc *************** d04590c4dc6a61734d09958671cba4da libjav *** 29744,29750 **** c47d9d2a3aff39dca071c5554ad5930a libjava/libgcj.spec.in 7c54aae5201fce512e10bc9274650060 libjava/libgcj_bc.c e3eda01d9815f8d24aae2dbd89b68b06 libjava/libltdl/COPYING.LIB ! 3474a2493b7d42c3590a10e406bf5818 libjava/libltdl/ChangeLog 687405b58bc7fffede3a92c2d9d39bcf libjava/libltdl/Makefile.am 129915ab2faa96ebc5d04ca1524bbf5e libjava/libltdl/Makefile.in 36da24f9facf00b349ea10dba3789d92 libjava/libltdl/README --- 29799,29805 ---- c47d9d2a3aff39dca071c5554ad5930a libjava/libgcj.spec.in 7c54aae5201fce512e10bc9274650060 libjava/libgcj_bc.c e3eda01d9815f8d24aae2dbd89b68b06 libjava/libltdl/COPYING.LIB ! c7ed811544fb136c2fd0ba7be7a88458 libjava/libltdl/ChangeLog 687405b58bc7fffede3a92c2d9d39bcf libjava/libltdl/Makefile.am 129915ab2faa96ebc5d04ca1524bbf5e libjava/libltdl/Makefile.in 36da24f9facf00b349ea10dba3789d92 libjava/libltdl/README *************** d41d8cd98f00b204e9800998ecf8427e libjav *** 30513,30519 **** 434ac04eb066f5075299583492846410 libjava/verify.cc b49b4f4aeefe0015a25485073b3bdc13 libjava/win32-threads.cc 434d5e5e91727dec004f0d1d1fab47ec libjava/win32.cc ! 7dc0139a69648a1c51cfe07cc8aeab6b libmudflap/ChangeLog c8acea5852055d21346ff119d153785e libmudflap/Makefile.am ebb289fe36e15f34242703b027e9b293 libmudflap/Makefile.in 9883ed42b491d8aea83fdde90561cf2a libmudflap/acinclude.m4 --- 30568,30574 ---- 434ac04eb066f5075299583492846410 libjava/verify.cc b49b4f4aeefe0015a25485073b3bdc13 libjava/win32-threads.cc 434d5e5e91727dec004f0d1d1fab47ec libjava/win32.cc ! 649ff277031da4182b4f6148362ab7ec libmudflap/ChangeLog c8acea5852055d21346ff119d153785e libmudflap/Makefile.am ebb289fe36e15f34242703b027e9b293 libmudflap/Makefile.in 9883ed42b491d8aea83fdde90561cf2a libmudflap/acinclude.m4 *************** c5335252518805ab1392c05df57648dd libmud *** 30648,30654 **** 67c76fce7dd9dbb0f532d7e9f5c09f7a libmudflap/testsuite/libmudflap.cth/pass39-frag.c 9c6e0ee7556df21372ba89fcb2612d17 libmudflap/testsuite/libmudflap.cth/pass40-frag.c 60168171460c9277504005955b1ea1b8 libmudflap/testsuite/mfconfig.exp.in ! 6000b585b059213ec4e623648aee8620 libobjc/ChangeLog 267c1662111ddddd03719f4b53ddd1a8 libobjc/Makefile.in b72b505ce44f731e074f50699c5692e8 libobjc/NXConstStr.m 601602b8688b4064b961b0c12d68360d libobjc/Object.m --- 30703,30709 ---- 67c76fce7dd9dbb0f532d7e9f5c09f7a libmudflap/testsuite/libmudflap.cth/pass39-frag.c 9c6e0ee7556df21372ba89fcb2612d17 libmudflap/testsuite/libmudflap.cth/pass40-frag.c 60168171460c9277504005955b1ea1b8 libmudflap/testsuite/mfconfig.exp.in ! 994468a6ee4515ba6e65cba781f3a733 libobjc/ChangeLog 267c1662111ddddd03719f4b53ddd1a8 libobjc/Makefile.in b72b505ce44f731e074f50699c5692e8 libobjc/NXConstStr.m 601602b8688b4064b961b0c12d68360d libobjc/Object.m *************** dc40c43e3b37ec7b0fc4a64a75a54c87 libobj *** 30706,30712 **** dc40c43e3b37ec7b0fc4a64a75a54c87 libobjc/thr-vxworks.c 1e0b955d26e11a355d21cad4f2007898 libobjc/thr-win32.c 5314fd1def4a84ee5c5c93c8a9a1a8ba libobjc/thr.c ! 069e047e7816fff229f2088dfb5c5e50 libssp/ChangeLog fd468600fde6719e8182b011df02f23c libssp/Makefile.am 6b84a8440a4ee9b4ad42485bea53eea0 libssp/Makefile.in 5749a9aef434ef582f5d49d98a854836 libssp/aclocal.m4 --- 30761,30767 ---- dc40c43e3b37ec7b0fc4a64a75a54c87 libobjc/thr-vxworks.c 1e0b955d26e11a355d21cad4f2007898 libobjc/thr-win32.c 5314fd1def4a84ee5c5c93c8a9a1a8ba libobjc/thr.c ! a5bcf38c6b157e264f791406f7b5cda3 libssp/ChangeLog fd468600fde6719e8182b011df02f23c libssp/Makefile.am 6b84a8440a4ee9b4ad42485bea53eea0 libssp/Makefile.in 5749a9aef434ef582f5d49d98a854836 libssp/aclocal.m4 *************** eedcb30bb5e1189173c5a377cae8e014 libssp *** 30735,30741 **** 062bfaca10505a776cb397b9ad6418b5 libssp/strncpy-chk.c 5b568b3f83a33ce26abd2184b4f49f87 libssp/vsnprintf-chk.c 7dbcd73efdcd7e29635d58af69cbd48d libssp/vsprintf-chk.c ! dd645436e3f6394fe8eca6fe1317a5a4 libstdc++-v3/ChangeLog 0cda0576312959181333fb6113d11fca libstdc++-v3/ChangeLog-1998 c1b0e4b61db61eeb710dcf9bb925f9eb libstdc++-v3/ChangeLog-1999 7b42e2258fc86c55d4a1196c3073f514 libstdc++-v3/ChangeLog-2000 --- 30790,30796 ---- 062bfaca10505a776cb397b9ad6418b5 libssp/strncpy-chk.c 5b568b3f83a33ce26abd2184b4f49f87 libssp/vsnprintf-chk.c 7dbcd73efdcd7e29635d58af69cbd48d libssp/vsprintf-chk.c ! 262c30f8e8e8f8bc31c5b8a9854ab7ff libstdc++-v3/ChangeLog 0cda0576312959181333fb6113d11fca libstdc++-v3/ChangeLog-1998 c1b0e4b61db61eeb710dcf9bb925f9eb libstdc++-v3/ChangeLog-1999 7b42e2258fc86c55d4a1196c3073f514 libstdc++-v3/ChangeLog-2000 *************** fd85b193ffcf648176beb46e31decec6 libstd *** 30969,30975 **** 04634d92698ab47d0ef884fbbc9123a6 libstdc++-v3/docs/html/27_io/binary_iostreams_kanze.txt 8df1a969d47ddd463121be67c1317f5e libstdc++-v3/docs/html/27_io/binary_iostreams_kuehl.txt 8c3569748e82f1a54066535763c790c0 libstdc++-v3/docs/html/27_io/howto.html ! 487fd00ae9958022896748bad45fc7d2 libstdc++-v3/docs/html/Makefile 74c0763dd9d3851fb49dd21f761307fb libstdc++-v3/docs/html/abi.html a689fb7206ad363d04221ec50c4caf77 libstdc++-v3/docs/html/configopts.html c0a2c24cff4cff7482c5cbee0ff8618c libstdc++-v3/docs/html/debug.html --- 31024,31030 ---- 04634d92698ab47d0ef884fbbc9123a6 libstdc++-v3/docs/html/27_io/binary_iostreams_kanze.txt 8df1a969d47ddd463121be67c1317f5e libstdc++-v3/docs/html/27_io/binary_iostreams_kuehl.txt 8c3569748e82f1a54066535763c790c0 libstdc++-v3/docs/html/27_io/howto.html ! e7379bf66aaa994f9e1b91851d01006d libstdc++-v3/docs/html/Makefile 74c0763dd9d3851fb49dd21f761307fb libstdc++-v3/docs/html/abi.html a689fb7206ad363d04221ec50c4caf77 libstdc++-v3/docs/html/configopts.html c0a2c24cff4cff7482c5cbee0ff8618c libstdc++-v3/docs/html/debug.html *************** ae641d88710596fd04900d3d23c07644 libstd *** 31326,31335 **** a67436b966aecd4ebcf5f6c8b3d6b4b7 libstdc++-v3/include/backward/tempbuf.h 006329f14b527b0a963f5ed42d8a71e5 libstdc++-v3/include/backward/tree.h 0940863d773162ed810610ffacdf4cfd libstdc++-v3/include/backward/vector.h ! 22174c0a88fa4d5f845cc533d380bcb1 libstdc++-v3/include/bits/allocator.h a64089c0fc0888ff8175a85f2448b21d libstdc++-v3/include/bits/basic_ios.h 1d62c50318f5c98d7ee04f2d27e8b630 libstdc++-v3/include/bits/basic_ios.tcc ! 195724c05c76d0ba2d64595f7d9dc9e2 libstdc++-v3/include/bits/basic_string.h 514d828778435ada7e14d67daa2fc671 libstdc++-v3/include/bits/basic_string.tcc a252fee6a420dc886cf5b68074847377 libstdc++-v3/include/bits/boost_concept_check.h 0e2f690e8ee156c802aee8dc1f14837d libstdc++-v3/include/bits/c++config --- 31381,31390 ---- a67436b966aecd4ebcf5f6c8b3d6b4b7 libstdc++-v3/include/backward/tempbuf.h 006329f14b527b0a963f5ed42d8a71e5 libstdc++-v3/include/backward/tree.h 0940863d773162ed810610ffacdf4cfd libstdc++-v3/include/backward/vector.h ! 5c929c8985b279b642b6e35993c8bec2 libstdc++-v3/include/bits/allocator.h a64089c0fc0888ff8175a85f2448b21d libstdc++-v3/include/bits/basic_ios.h 1d62c50318f5c98d7ee04f2d27e8b630 libstdc++-v3/include/bits/basic_ios.tcc ! 0789f03cfa3bc21f0c0fdc6bd03c1217 libstdc++-v3/include/bits/basic_string.h 514d828778435ada7e14d67daa2fc671 libstdc++-v3/include/bits/basic_string.tcc a252fee6a420dc886cf5b68074847377 libstdc++-v3/include/bits/boost_concept_check.h 0e2f690e8ee156c802aee8dc1f14837d libstdc++-v3/include/bits/c++config *************** c8de27d52bb3405681b64dc12806ad66 libstd *** 31338,31344 **** 951facae6cd748f54b167fb78865f89a libstdc++-v3/include/bits/concept_check.h c45eed79e4f577e077681dd28da4afd7 libstdc++-v3/include/bits/cpp_type_traits.h 89ee8aa57e1e6220b6db34186496a441 libstdc++-v3/include/bits/deque.tcc ! c85e1e2e63dc7de664f8abfbfc1f1381 libstdc++-v3/include/bits/fstream.tcc f4428717d77d5034dccd089b6f387637 libstdc++-v3/include/bits/functexcept.h e51f2e421cdb9453453ec88f2f7c0d58 libstdc++-v3/include/bits/gslice.h af5d8e2673db44760fa6df1dabd5c7b4 libstdc++-v3/include/bits/gslice_array.h --- 31393,31399 ---- 951facae6cd748f54b167fb78865f89a libstdc++-v3/include/bits/concept_check.h c45eed79e4f577e077681dd28da4afd7 libstdc++-v3/include/bits/cpp_type_traits.h 89ee8aa57e1e6220b6db34186496a441 libstdc++-v3/include/bits/deque.tcc ! 66137911039cd50b3c49280192802388 libstdc++-v3/include/bits/fstream.tcc f4428717d77d5034dccd089b6f387637 libstdc++-v3/include/bits/functexcept.h e51f2e421cdb9453453ec88f2f7c0d58 libstdc++-v3/include/bits/gslice.h af5d8e2673db44760fa6df1dabd5c7b4 libstdc++-v3/include/bits/gslice_array.h *************** eb10e92e691d8dd6faab60e9cfe40f49 libstd *** 31348,31354 **** 0bd6472c069c36f9c5e7f2593084371a libstdc++-v3/include/bits/list.tcc dab8eda6edfcceda9b0b00a8093bcaff libstdc++-v3/include/bits/locale_classes.h 28a678fe0b8b6a609d3302064e0488ac libstdc++-v3/include/bits/locale_facets.h ! d3062598e6158e1143ecbf84403f1ab6 libstdc++-v3/include/bits/locale_facets.tcc c3dde6eaa95d011f099e737c20532436 libstdc++-v3/include/bits/localefwd.h 016d5fba102e3c5ceb5d56ed2a7fd008 libstdc++-v3/include/bits/mask_array.h 8aae4106b43f807e7f4c678c3c24e5eb libstdc++-v3/include/bits/ostream.tcc --- 31403,31409 ---- 0bd6472c069c36f9c5e7f2593084371a libstdc++-v3/include/bits/list.tcc dab8eda6edfcceda9b0b00a8093bcaff libstdc++-v3/include/bits/locale_classes.h 28a678fe0b8b6a609d3302064e0488ac libstdc++-v3/include/bits/locale_facets.h ! 979b4e8fbce74cbf02ca08deee6f2179 libstdc++-v3/include/bits/locale_facets.tcc c3dde6eaa95d011f099e737c20532436 libstdc++-v3/include/bits/localefwd.h 016d5fba102e3c5ceb5d56ed2a7fd008 libstdc++-v3/include/bits/mask_array.h 8aae4106b43f807e7f4c678c3c24e5eb libstdc++-v3/include/bits/ostream.tcc *************** fe096aec737a6aba4944ee9e3c304a0c libstd *** 31472,31481 **** ba1331226f8bb4982353cd1570bb6b86 libstdc++-v3/include/debug/vector f5a40fd6066aab521b406e86cc3b8939 libstdc++-v3/include/ext/algorithm 1b40de72e53f49b15f707625e1d56341 libstdc++-v3/include/ext/array_allocator.h ! 4ef0d34b80752bf2399c1b40c46cd183 libstdc++-v3/include/ext/atomicity.h 084f2b2748dad30fe49d0c34634633bc libstdc++-v3/include/ext/bitmap_allocator.h ! 5fe6bc1972d6fd4e100d858c4a07b144 libstdc++-v3/include/ext/codecvt_specializations.h ! 0387aa979a04965db24742c139bb60d8 libstdc++-v3/include/ext/concurrence.h be0f8721ee4acfcbee42ff176251774e libstdc++-v3/include/ext/debug_allocator.h bf64df301291a3c00897bc2c482efc85 libstdc++-v3/include/ext/functional 0ccaee33e11d0540ce7e687938672a23 libstdc++-v3/include/ext/hash_fun.h --- 31527,31536 ---- ba1331226f8bb4982353cd1570bb6b86 libstdc++-v3/include/debug/vector f5a40fd6066aab521b406e86cc3b8939 libstdc++-v3/include/ext/algorithm 1b40de72e53f49b15f707625e1d56341 libstdc++-v3/include/ext/array_allocator.h ! b0aa67049f28df38fbc32452c15cb104 libstdc++-v3/include/ext/atomicity.h 084f2b2748dad30fe49d0c34634633bc libstdc++-v3/include/ext/bitmap_allocator.h ! 4e313f051b6580d5ec1950c2d19d24bf libstdc++-v3/include/ext/codecvt_specializations.h ! 37ecdabffbff3463a846123b89023941 libstdc++-v3/include/ext/concurrence.h be0f8721ee4acfcbee42ff176251774e libstdc++-v3/include/ext/debug_allocator.h bf64df301291a3c00897bc2c482efc85 libstdc++-v3/include/ext/functional 0ccaee33e11d0540ce7e687938672a23 libstdc++-v3/include/ext/hash_fun.h *************** b195c6d04821b1f114997db0a9a6ff7e libstd *** 31767,31773 **** 2e1737c926a4636c05c33e5a563a6e87 libstdc++-v3/include/ext/throw_allocator.h a93b9cd6296862195ee1b64b5c69a2d6 libstdc++-v3/include/ext/type_traits.h 969729bb88882ded198828d3b7619f18 libstdc++-v3/include/ext/typelist.h ! 5225c168b6b7baf7ad3f5d1f9031ff1e libstdc++-v3/include/ext/vstring.h f5c47b8fa2362a93e6ee6a5d86bfbce3 libstdc++-v3/include/ext/vstring.tcc 29865105db6b64af4c5f109dd595ee05 libstdc++-v3/include/ext/vstring_fwd.h a18bc2406aa233e97a13e269e1082351 libstdc++-v3/include/ext/vstring_util.h --- 31822,31828 ---- 2e1737c926a4636c05c33e5a563a6e87 libstdc++-v3/include/ext/throw_allocator.h a93b9cd6296862195ee1b64b5c69a2d6 libstdc++-v3/include/ext/type_traits.h 969729bb88882ded198828d3b7619f18 libstdc++-v3/include/ext/typelist.h ! 9cdb9f0690c658ce9206480019f8b88c libstdc++-v3/include/ext/vstring.h f5c47b8fa2362a93e6ee6a5d86bfbce3 libstdc++-v3/include/ext/vstring.tcc 29865105db6b64af4c5f109dd595ee05 libstdc++-v3/include/ext/vstring_fwd.h a18bc2406aa233e97a13e269e1082351 libstdc++-v3/include/ext/vstring_util.h *************** cf33e24abadf202e754a08b6a0fd25b8 libstd *** 31806,31812 **** 4642d5ebd4b7ef87878f50162db12672 libstdc++-v3/include/tr1/array 8e2d5377808aebf8ab16ad54bd44baae libstdc++-v3/include/tr1/bind_iterate.h ae9aa5a02b1d120b5d830ff9488d1708 libstdc++-v3/include/tr1/bind_repeat.h ! 18eaca36288ddd564565eed4f3a572a7 libstdc++-v3/include/tr1/boost_shared_ptr.h 0c94eea686338d91c72495f105894e55 libstdc++-v3/include/tr1/cctype 518ef842d8d019328390e4626f0691b6 libstdc++-v3/include/tr1/cfenv b4c75de0175e38a0d9b913d77de04cdd libstdc++-v3/include/tr1/cfloat --- 31861,31867 ---- 4642d5ebd4b7ef87878f50162db12672 libstdc++-v3/include/tr1/array 8e2d5377808aebf8ab16ad54bd44baae libstdc++-v3/include/tr1/bind_iterate.h ae9aa5a02b1d120b5d830ff9488d1708 libstdc++-v3/include/tr1/bind_repeat.h ! e720e5eea127760441c808d7623aa009 libstdc++-v3/include/tr1/boost_shared_ptr.h 0c94eea686338d91c72495f105894e55 libstdc++-v3/include/tr1/cctype 518ef842d8d019328390e4626f0691b6 libstdc++-v3/include/tr1/cfenv b4c75de0175e38a0d9b913d77de04cdd libstdc++-v3/include/tr1/cfloat *************** a448298856979a495f60cec96c56bd4f libstd *** 31837,31843 **** 80d2162d046fc7a0b895edf0ee7e6bf1 libstdc++-v3/include/tr1/math.h 61a8ce9ff4e1ae0bd9c3f1964b35f839 libstdc++-v3/include/tr1/memory cbbd75d8249aebe117dcb82ba68b7c9c libstdc++-v3/include/tr1/mu_iterate.h ! 537a8fa10ce05e37c40374e191532c67 libstdc++-v3/include/tr1/random ae4f702de37420961cb64b413f0f3831 libstdc++-v3/include/tr1/random.tcc faea7e74dc7e9b5619fd0296c3948ba7 libstdc++-v3/include/tr1/ref_fwd.h 385fc689a5b0721e7edffc9c9af9ee90 libstdc++-v3/include/tr1/ref_wrap_iterate.h --- 31892,31898 ---- 80d2162d046fc7a0b895edf0ee7e6bf1 libstdc++-v3/include/tr1/math.h 61a8ce9ff4e1ae0bd9c3f1964b35f839 libstdc++-v3/include/tr1/memory cbbd75d8249aebe117dcb82ba68b7c9c libstdc++-v3/include/tr1/mu_iterate.h ! a169286e9bb9075c2e55d41297d975db libstdc++-v3/include/tr1/random ae4f702de37420961cb64b413f0f3831 libstdc++-v3/include/tr1/random.tcc faea7e74dc7e9b5619fd0296c3948ba7 libstdc++-v3/include/tr1/ref_fwd.h 385fc689a5b0721e7edffc9c9af9ee90 libstdc++-v3/include/tr1/ref_wrap_iterate.h *************** c71138d8b85ca9a614c0a411a3b60f52 libstd *** 31880,31886 **** 768ddc950454a0a55910796d7db0e048 libstdc++-v3/libsupc++/eh_catch.cc cd0411f8f6eaa7f1ba8995b9da6efdbf libstdc++-v3/libsupc++/eh_exception.cc 15f658f1d9522501a30a1afbf925cb0a libstdc++-v3/libsupc++/eh_globals.cc ! 5ef640e3ae95fcc672c82db5ec89e276 libstdc++-v3/libsupc++/eh_personality.cc a02eb3f1fa9a26a456af808ac4fa146e libstdc++-v3/libsupc++/eh_term_handler.cc 89d2e91f7c1a9b2f872b68f3a2c0dd99 libstdc++-v3/libsupc++/eh_terminate.cc b93658be999ade574078d078a2cbd3f9 libstdc++-v3/libsupc++/eh_throw.cc --- 31935,31941 ---- 768ddc950454a0a55910796d7db0e048 libstdc++-v3/libsupc++/eh_catch.cc cd0411f8f6eaa7f1ba8995b9da6efdbf libstdc++-v3/libsupc++/eh_exception.cc 15f658f1d9522501a30a1afbf925cb0a libstdc++-v3/libsupc++/eh_globals.cc ! a147f379a3196ae34d12ff81168543a8 libstdc++-v3/libsupc++/eh_personality.cc a02eb3f1fa9a26a456af808ac4fa146e libstdc++-v3/libsupc++/eh_term_handler.cc 89d2e91f7c1a9b2f872b68f3a2c0dd99 libstdc++-v3/libsupc++/eh_terminate.cc b93658be999ade574078d078a2cbd3f9 libstdc++-v3/libsupc++/eh_throw.cc *************** d2b4f3f336928504607d3db4b515f6dc libstd *** 31964,31970 **** b0d835963b4ad1f520e98da48cf1f6ed libstdc++-v3/src/string-inst.cc afba8cc4ddc6c833054ee8d3605d3a72 libstdc++-v3/src/strstream.cc 0feb7112ae18ea39a764d7692227faba libstdc++-v3/src/tree.cc ! 625e39373fb3dfab6fb737624e0fd624 libstdc++-v3/src/valarray-inst.cc 480de974075d1b3608006a7aa0cba0f7 libstdc++-v3/src/wlocale-inst.cc ff697dedd3dbeb0ab5a0366d4e754cd7 libstdc++-v3/src/wstring-inst.cc eeda817b9853e0d93d89594b32dce51c libstdc++-v3/testsuite/17_intro/header_cassert.cc --- 32019,32025 ---- b0d835963b4ad1f520e98da48cf1f6ed libstdc++-v3/src/string-inst.cc afba8cc4ddc6c833054ee8d3605d3a72 libstdc++-v3/src/strstream.cc 0feb7112ae18ea39a764d7692227faba libstdc++-v3/src/tree.cc ! 9a6d9b285923f0b539d376d0e17adf94 libstdc++-v3/src/valarray-inst.cc 480de974075d1b3608006a7aa0cba0f7 libstdc++-v3/src/wlocale-inst.cc ff697dedd3dbeb0ab5a0366d4e754cd7 libstdc++-v3/src/wstring-inst.cc eeda817b9853e0d93d89594b32dce51c libstdc++-v3/testsuite/17_intro/header_cassert.cc *************** c9a831dbdb4ff7f072471721f3c05a40 libstd *** 32014,32019 **** --- 32069,32075 ---- ac220e485364d8e9dd401eada9d54a72 libstdc++-v3/testsuite/20_util/memory/allocator/1.cc fbb90398c26091d24a9623d29d1bf9e0 libstdc++-v3/testsuite/20_util/memory/allocator/10378.cc bd376959c10b698e3235efbdc8c9e384 libstdc++-v3/testsuite/20_util/memory/allocator/14176.cc + 459c17eebda7ae4dc02649eccc387a0c libstdc++-v3/testsuite/20_util/memory/allocator/33807.cc d78e0e3db59798d8ebfc50bab33ffef0 libstdc++-v3/testsuite/20_util/memory/allocator/8230.cc dafb82b1e6b7cebc3404af023e7b7bda libstdc++-v3/testsuite/20_util/memory/auto_ptr/1.cc 1cb2ba5ab1012a4f20ecd5261bdad2bd libstdc++-v3/testsuite/20_util/memory/auto_ptr/2.cc *************** eade0e7ec6a3f0511280dea684b75fb4 libstd *** 32481,32486 **** --- 32537,32543 ---- 8de17a7e7e1888ab73385bb4f6194229 libstdc++-v3/testsuite/22_locale/num_put/put/char/1.cc 79318185c0cc3915b846d3fa46530f60 libstdc++-v3/testsuite/22_locale/num_put/put/char/10.cc 2e27b8a0f4753bf933d22e502783ab99 libstdc++-v3/testsuite/22_locale/num_put/put/char/11.cc + 654137b91c1b0b5a95f3e3ffcc87860a libstdc++-v3/testsuite/22_locale/num_put/put/char/12.cc d57aa5d6236ecb33e46d39db6fa52eed libstdc++-v3/testsuite/22_locale/num_put/put/char/14220.cc 59b810d8a5120fae02474dd67b5dfa2c libstdc++-v3/testsuite/22_locale/num_put/put/char/15565.cc 14d4874406a183fc33f85df784e85e00 libstdc++-v3/testsuite/22_locale/num_put/put/char/2.cc *************** fcb7c4e5df7cfd918d009fa3b7931581 libstd *** 32500,32505 **** --- 32557,32563 ---- 9228935e0603ac3ec8f5573ab35f6b58 libstdc++-v3/testsuite/22_locale/num_put/put/wchar_t/1.cc e2daaa158030330f4ad70437eaea2b23 libstdc++-v3/testsuite/22_locale/num_put/put/wchar_t/10.cc b6c31176f3766445c293f9f92b2acc3d libstdc++-v3/testsuite/22_locale/num_put/put/wchar_t/11.cc + 40924449dabec6543608b1d8d780e21c libstdc++-v3/testsuite/22_locale/num_put/put/wchar_t/12.cc c13417686afce9d967430f7d4ce00bd3 libstdc++-v3/testsuite/22_locale/num_put/put/wchar_t/14220.cc c97eea87f43b448c61108950645ad275 libstdc++-v3/testsuite/22_locale/num_put/put/wchar_t/15565.cc aa554a01086cea35d880d036e944602e libstdc++-v3/testsuite/22_locale/num_put/put/wchar_t/2.cc *************** bd5d4660062280f7e415378b63c8e2cc libstd *** 34213,34218 **** --- 34271,34277 ---- 88cccd2973c333f86055710f853b9cc9 libstdc++-v3/testsuite/tr1/2_general_utilities/memory/shared_ptr/cons/weak_ptr_expired.cc 5730e36994a96ac7f2ca9e2b45172beb libstdc++-v3/testsuite/tr1/2_general_utilities/memory/shared_ptr/dest/dest.cc 84250683e984d364d538b427e8a3d235 libstdc++-v3/testsuite/tr1/2_general_utilities/memory/shared_ptr/explicit_instantiation/1.cc + 172f0c78477f770e801875d2d71a9c22 libstdc++-v3/testsuite/tr1/2_general_utilities/memory/shared_ptr/explicit_instantiation/2.cc fb18ced7dce36bde738243716a1af4f1 libstdc++-v3/testsuite/tr1/2_general_utilities/memory/shared_ptr/misc/24595.cc 874b1b4b734b0e8e2c8220cef77824b8 libstdc++-v3/testsuite/tr1/2_general_utilities/memory/shared_ptr/misc/io.cc 623ad17ebf1fe3ceecd3441598bf1d23 libstdc++-v3/testsuite/tr1/2_general_utilities/memory/shared_ptr/misc/swap.cc *************** d8a4988963a6982be43a4ca911cabf3b libstd *** 34228,34233 **** --- 34287,34293 ---- dfd7382a5b5596b24a394a099df46fc5 libstdc++-v3/testsuite/tr1/2_general_utilities/memory/shared_ptr/thread/default_weaktoshared.cc 88e0547e7f38355c39f77b845d86f1e4 libstdc++-v3/testsuite/tr1/2_general_utilities/memory/shared_ptr/thread/mutex_weaktoshared.cc ce691b282bdef2a823376fb9c4e5388d libstdc++-v3/testsuite/tr1/2_general_utilities/memory/weak_ptr/explicit_instantiation/1.cc + b9e2fb546faabeb74a216a45f0767cbb libstdc++-v3/testsuite/tr1/2_general_utilities/memory/weak_ptr/explicit_instantiation/2.cc 60f282da0313d3eea4ae5ec8d877e22e libstdc++-v3/testsuite/tr1/2_general_utilities/memory/weak_ptr/lock/1.cc 743b0510a0927f73174c46bc5be9a464 libstdc++-v3/testsuite/tr1/3_function_objects/bind/all_bound.cc f004403aa0b4ba3fd11c7b84caa6be7f libstdc++-v3/testsuite/tr1/3_function_objects/bind/nested.cc *************** a2d47602fcd7324c616dc9afe83fc435 ltcf-c *** 34654,34663 **** fffe423a2194a2fcc3890bba0d9ac23f ltcf-gcj.sh 88874ccfc7298fda733754724dd93312 ltconfig 8328ccc025749f369b42fcee97659940 ltmain.sh ! b9e5824f00646116988ce22b8b5c3b16 maintainer-scripts/ChangeLog 9bf52719995189b7572953a25ad202ed maintainer-scripts/README dea291db15d8324298005761d3a728b4 maintainer-scripts/crontab ! 0d83c098ee7c54faa474bbb418871efb maintainer-scripts/gcc_release 5a590c51b17d10747f3ce2694caf0ff2 maintainer-scripts/maintainer-addresses 67147b0d6cd79b577afefa2d239c1996 maintainer-scripts/update_version e3613edadabd2dba9de5f08e56c8d800 maintainer-scripts/update_version_svn --- 34714,34723 ---- fffe423a2194a2fcc3890bba0d9ac23f ltcf-gcj.sh 88874ccfc7298fda733754724dd93312 ltconfig 8328ccc025749f369b42fcee97659940 ltmain.sh ! ee98ed58bc84f33c9ae650af8fc0165e maintainer-scripts/ChangeLog 9bf52719995189b7572953a25ad202ed maintainer-scripts/README dea291db15d8324298005761d3a728b4 maintainer-scripts/crontab ! a6119bf6efe70986b9fa01ccaedff9b6 maintainer-scripts/gcc_release 5a590c51b17d10747f3ce2694caf0ff2 maintainer-scripts/maintainer-addresses 67147b0d6cd79b577afefa2d239c1996 maintainer-scripts/update_version e3613edadabd2dba9de5f08e56c8d800 maintainer-scripts/update_version_svn *************** fbe2467afef81c41c166173adeb0ee20 mkdep *** 34669,34675 **** a20215c156b06261d944ae7f30a3b75c move-if-change cf2baa0854f564a7785307e79f155efc symlink-tree e0a5f7e59d19edfd4b4d26479a141f02 ylwrap ! f49f95b0925c905457f1761d5fdd008a zlib/ChangeLog 9602f98cc212f59622bb55fec22fdc24 zlib/ChangeLog.gcj 2f46720fda5ab68a1e495009895d874c zlib/FAQ 8851ace55681b1664d97c045d71e339b zlib/INDEX --- 34729,34735 ---- a20215c156b06261d944ae7f30a3b75c move-if-change cf2baa0854f564a7785307e79f155efc symlink-tree e0a5f7e59d19edfd4b4d26479a141f02 ylwrap ! 4f7a5239fe5441e76ce2c15e70be7a50 zlib/ChangeLog 9602f98cc212f59622bb55fec22fdc24 zlib/ChangeLog.gcj 2f46720fda5ab68a1e495009895d874c zlib/FAQ 8851ace55681b1664d97c045d71e339b zlib/INDEX diff -Nrcpad gcc-4.2.2/NEWS gcc-4.2.3/NEWS *** gcc-4.2.2/NEWS Sun Oct 7 21:23:22 2007 --- gcc-4.2.3/NEWS Fri Feb 1 17:07:05 2008 *************** see ONEWS. *** 6,72 **** ====================================================================== http://gcc.gnu.org/gcc-4.2/index.html - GCC 4.2 Release Series ! October 7, 2007 ! The [1]GNU project and the GCC developers are pleased to announce the ! release of GCC 4.2.2. ! This release is a bug-fix release, containing fixes for regressions in GCC ! 4.2.1 relative to previous releases of GCC. Release History GCC 4.2.2 ! October 7, 2007 ([2]changes) GCC 4.2.1 ! July 18, 2007 ([3]changes) GCC 4.2.0 ! May 13, 2007 ([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, one of the [10]GNU 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 2007-10-07 [20]Valid XHTML 1.0 References --- 6,74 ---- ====================================================================== http://gcc.gnu.org/gcc-4.2/index.html GCC 4.2 Release Series ! February 1, 2008 ! The [1]GNU project and the GCC developers are pleased to announce the ! release of GCC 4.2.3. ! This release is a bug-fix release, containing fixes for regressions in ! GCC 4.2.2 relative to previous releases of GCC. Release History + GCC 4.2.3 + February 1, 2008 ([2]changes) + GCC 4.2.2 ! October 7, 2007 ([3]changes) GCC 4.2.1 ! July 18, 2007 ([4]changes) GCC 4.2.0 ! May 13, 2007 ([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, one of the [11]GNU ! 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-02-01 [21]Valid XHTML 1.0 References *************** References *** 74,179 **** 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/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://www.gnu.org/order/ftp.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.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 ! [3]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