aboutsummaryrefslogtreecommitdiffstats
path: root/gcc-4.9
diff options
context:
space:
mode:
Diffstat (limited to 'gcc-4.9')
-rw-r--r--gcc-4.9/.dir-locals.el24
-rw-r--r--gcc-4.9/.gitignore42
-rw-r--r--gcc-4.9/INSTALL/binaries.html168
-rw-r--r--gcc-4.9/INSTALL/build.html458
-rw-r--r--gcc-4.9/INSTALL/configure.html1837
-rw-r--r--gcc-4.9/INSTALL/download.html132
-rw-r--r--gcc-4.9/INSTALL/finalinstall.html227
-rw-r--r--gcc-4.9/INSTALL/gfdl.html571
-rw-r--r--gcc-4.9/INSTALL/index.html165
-rw-r--r--gcc-4.9/INSTALL/old.html253
-rw-r--r--gcc-4.9/INSTALL/prerequisites.html431
-rw-r--r--gcc-4.9/INSTALL/specific.html1454
-rw-r--r--gcc-4.9/INSTALL/test.html315
-rw-r--r--gcc-4.9/LAST_UPDATED1
-rw-r--r--gcc-4.9/MD5SUMS84493
-rw-r--r--gcc-4.9/Makefile.def7
-rw-r--r--gcc-4.9/Makefile.in1011
-rw-r--r--gcc-4.9/Makefile.tpl6
-rw-r--r--gcc-4.9/NEWS14589
-rwxr-xr-xgcc-4.9/boehm-gc/configure21
-rwxr-xr-xgcc-4.9/configure10
-rw-r--r--gcc-4.9/configure.ac10
-rw-r--r--gcc-4.9/contrib/ChangeLog4
-rwxr-xr-xgcc-4.9/contrib/gennews2
-rw-r--r--gcc-4.9/contrib/testsuite-management/aarch64-grtev4-linux-gnu.xfail152
-rw-r--r--gcc-4.9/contrib/testsuite-management/powerpc64le-grtev4-linux-gnu.xfail259
-rwxr-xr-xgcc-4.9/contrib/testsuite-management/validate_failures.py2
-rw-r--r--gcc-4.9/contrib/testsuite-management/x86_64-grtev4-linux-gnu.xfail47
-rw-r--r--gcc-4.9/contrib/testsuite-management/x86_64-unknown-linux-gnu.xfail109
-rw-r--r--gcc-4.9/function_reordering_plugin/ChangeLog.google-4_714
-rw-r--r--gcc-4.9/function_reordering_plugin/Makefile.am38
-rw-r--r--gcc-4.9/function_reordering_plugin/Makefile.in548
-rw-r--r--gcc-4.9/function_reordering_plugin/aclocal.m49008
-rw-r--r--gcc-4.9/function_reordering_plugin/callgraph.c1188
-rw-r--r--gcc-4.9/function_reordering_plugin/callgraph.h318
-rw-r--r--gcc-4.9/function_reordering_plugin/config.h.in68
-rwxr-xr-xgcc-4.9/function_reordering_plugin/configure13086
-rw-r--r--gcc-4.9/function_reordering_plugin/configure.ac14
-rw-r--r--gcc-4.9/function_reordering_plugin/function_reordering_plugin.c501
-rw-r--r--gcc-4.9/gcc/BASE-VER2
-rw-r--r--gcc-4.9/gcc/ChangeLog1075
-rw-r--r--gcc-4.9/gcc/DATESTAMP2
-rw-r--r--gcc-4.9/gcc/Makefile.in77
-rw-r--r--gcc-4.9/gcc/ada/ChangeLog56
-rw-r--r--gcc-4.9/gcc/ada/comperr.adb14
-rw-r--r--gcc-4.9/gcc/ada/comperr.ads13
-rw-r--r--gcc-4.9/gcc/ada/exp_cg.adb6
-rw-r--r--gcc-4.9/gcc/ada/exp_dbug.adb77
-rw-r--r--gcc-4.9/gcc/ada/exp_dbug.ads26
-rw-r--r--gcc-4.9/gcc/ada/exp_disp.adb7
-rw-r--r--gcc-4.9/gcc/ada/fe.h23
-rw-r--r--gcc-4.9/gcc/ada/gcc-interface/Makefile.in38
-rw-r--r--gcc-4.9/gcc/ada/gcc-interface/decl.c26
-rw-r--r--gcc-4.9/gcc/ada/gcc-interface/misc.c22
-rw-r--r--gcc-4.9/gcc/ada/gcc-interface/trans.c16
-rw-r--r--gcc-4.9/gcc/ada/gcc-interface/utils.c3
-rw-r--r--gcc-4.9/gcc/ada/init.c13
-rw-r--r--gcc-4.9/gcc/ada/types.h18
-rw-r--r--gcc-4.9/gcc/alias.c66
-rw-r--r--gcc-4.9/gcc/attribs.c1
-rw-r--r--gcc-4.9/gcc/auto-profile.c1865
-rw-r--r--gcc-4.9/gcc/auto-profile.h36
-rw-r--r--gcc-4.9/gcc/basic-block.h6
-rw-r--r--gcc-4.9/gcc/builtin-types.def4
-rw-r--r--gcc-4.9/gcc/builtins.c8
-rw-r--r--gcc-4.9/gcc/c-family/ChangeLog26
-rw-r--r--gcc-4.9/gcc/c-family/c-common.c117
-rw-r--r--gcc-4.9/gcc/c-family/c-common.h3
-rw-r--r--gcc-4.9/gcc/c-family/c-cppbuiltin.c29
-rw-r--r--gcc-4.9/gcc/c-family/c-gimplify.c4
-rw-r--r--gcc-4.9/gcc/c-family/c-omp.c9
-rw-r--r--gcc-4.9/gcc/c-family/c-opts.c126
-rw-r--r--gcc-4.9/gcc/c-family/c-pragma.c2
-rw-r--r--gcc-4.9/gcc/c-family/c.opt4
-rw-r--r--gcc-4.9/gcc/c/ChangeLog51
-rw-r--r--gcc-4.9/gcc/c/c-array-notation.c18
-rw-r--r--gcc-4.9/gcc/c/c-decl.c374
-rw-r--r--gcc-4.9/gcc/c/c-lang.c21
-rw-r--r--gcc-4.9/gcc/c/c-parser.c36
-rw-r--r--gcc-4.9/gcc/c/c-tree.h15
-rw-r--r--gcc-4.9/gcc/c/c-typeck.c3
-rw-r--r--gcc-4.9/gcc/cfg-flags.def9
-rw-r--r--gcc-4.9/gcc/cfg.c20
-rw-r--r--gcc-4.9/gcc/cfgexpand.c5
-rw-r--r--gcc-4.9/gcc/cfghooks.c17
-rw-r--r--gcc-4.9/gcc/cfgloop.c94
-rw-r--r--gcc-4.9/gcc/cfgloop.h17
-rw-r--r--gcc-4.9/gcc/cfgrtl.c4
-rw-r--r--gcc-4.9/gcc/cgraph.c67
-rw-r--r--gcc-4.9/gcc/cgraph.h79
-rw-r--r--gcc-4.9/gcc/cgraphbuild.c391
-rw-r--r--gcc-4.9/gcc/cgraphclones.c87
-rw-r--r--gcc-4.9/gcc/cgraphunit.c191
-rw-r--r--gcc-4.9/gcc/cif-code.def8
-rw-r--r--gcc-4.9/gcc/combine.c2
-rw-r--r--gcc-4.9/gcc/common.opt203
-rw-r--r--gcc-4.9/gcc/common/config/msp430/msp430-common.c91
-rw-r--r--gcc-4.9/gcc/common/config/nds32/nds32-common.c2
-rw-r--r--gcc-4.9/gcc/config.gcc50
-rw-r--r--gcc-4.9/gcc/config.host1
-rw-r--r--gcc-4.9/gcc/config.in24
-rw-r--r--gcc-4.9/gcc/config/aarch64/aarch64-linux-android.h59
-rw-r--r--gcc-4.9/gcc/config/aarch64/aarch64-linux.h35
-rw-r--r--gcc-4.9/gcc/config/aarch64/aarch64-modes.def1
-rw-r--r--gcc-4.9/gcc/config/aarch64/aarch64-simd.md461
-rw-r--r--gcc-4.9/gcc/config/aarch64/aarch64.c20
-rw-r--r--gcc-4.9/gcc/config/aarch64/aarch64.md28
-rw-r--r--gcc-4.9/gcc/config/aarch64/arm_neon.h50
-rw-r--r--gcc-4.9/gcc/config/aarch64/iterators.md16
-rw-r--r--gcc-4.9/gcc/config/alpha/alpha.c6
-rw-r--r--gcc-4.9/gcc/config/arm/aout.h9
-rw-r--r--gcc-4.9/gcc/config/arm/arm-cores.def9
-rw-r--r--gcc-4.9/gcc/config/arm/arm-opts.h9
-rw-r--r--gcc-4.9/gcc/config/arm/arm.c13
-rw-r--r--gcc-4.9/gcc/config/arm/arm.h9
-rw-r--r--gcc-4.9/gcc/config/arm/arm.md13
-rw-r--r--gcc-4.9/gcc/config/arm/arm_neon.h608
-rw-r--r--gcc-4.9/gcc/config/arm/bpabi.h9
-rw-r--r--gcc-4.9/gcc/config/arm/elf.h9
-rw-r--r--gcc-4.9/gcc/config/arm/linux-eabi.h5
-rw-r--r--gcc-4.9/gcc/config/arm/linux-elf.h11
-rw-r--r--gcc-4.9/gcc/config/arm/linux-gas.h9
-rw-r--r--gcc-4.9/gcc/config/arm/linux-grte.h27
-rw-r--r--gcc-4.9/gcc/config/arm/neon-docgen.ml424
-rw-r--r--gcc-4.9/gcc/config/arm/neon-gen.ml520
-rw-r--r--gcc-4.9/gcc/config/arm/netbsd-elf.h9
-rw-r--r--gcc-4.9/gcc/config/arm/uclinux-eabi.h9
-rw-r--r--gcc-4.9/gcc/config/arm/uclinux-elf.h9
-rw-r--r--gcc-4.9/gcc/config/arm/unspecs.md9
-rw-r--r--gcc-4.9/gcc/config/arm/vxworks.h9
-rw-r--r--gcc-4.9/gcc/config/avr/avr-fixed.md4
-rw-r--r--gcc-4.9/gcc/config/avr/avr.h14
-rw-r--r--gcc-4.9/gcc/config/avr/avr.md9
-rw-r--r--gcc-4.9/gcc/config/dbx.h9
-rw-r--r--gcc-4.9/gcc/config/i386/driver-i386.c5
-rw-r--r--gcc-4.9/gcc/config/i386/gnu-user.h6
-rw-r--r--gcc-4.9/gcc/config/i386/i386-protos.h11
-rw-r--r--gcc-4.9/gcc/config/i386/i386.c362
-rw-r--r--gcc-4.9/gcc/config/i386/i386.md97
-rw-r--r--gcc-4.9/gcc/config/i386/i386.opt20
-rw-r--r--gcc-4.9/gcc/config/i386/linux.h20
-rw-r--r--gcc-4.9/gcc/config/i386/linux64.h19
-rw-r--r--gcc-4.9/gcc/config/i386/sse.md64
-rw-r--r--gcc-4.9/gcc/config/initfini-array.h9
-rw-r--r--gcc-4.9/gcc/config/linux-grte.h41
-rw-r--r--gcc-4.9/gcc/config/linux.c4
-rw-r--r--gcc-4.9/gcc/config/linux.h17
-rw-r--r--gcc-4.9/gcc/config/msp430/msp430-opts.h32
-rw-r--r--gcc-4.9/gcc/config/msp430/msp430.c117
-rw-r--r--gcc-4.9/gcc/config/msp430/msp430.h4
-rw-r--r--gcc-4.9/gcc/config/msp430/msp430.md32
-rw-r--r--gcc-4.9/gcc/config/msp430/predicates.md4
-rw-r--r--gcc-4.9/gcc/config/newlib-stdint.h9
-rw-r--r--gcc-4.9/gcc/config/rs6000/htm.md2
-rw-r--r--gcc-4.9/gcc/config/rs6000/htmxlintrin.h9
-rw-r--r--gcc-4.9/gcc/config/rs6000/linux-grte.h41
-rw-r--r--gcc-4.9/gcc/config/rs6000/linux64.h6
-rw-r--r--gcc-4.9/gcc/config/rs6000/rs6000-builtin.def21
-rw-r--r--gcc-4.9/gcc/config/rs6000/rs6000-protos.h2
-rw-r--r--gcc-4.9/gcc/config/rs6000/rs6000.c71
-rw-r--r--gcc-4.9/gcc/config/rs6000/rs6000.h17
-rw-r--r--gcc-4.9/gcc/config/rs6000/rs6000.md24
-rw-r--r--gcc-4.9/gcc/config/rs6000/sysv4.h11
-rw-r--r--gcc-4.9/gcc/config/rs6000/vsx.md43
-rw-r--r--gcc-4.9/gcc/config/rtems.h9
-rw-r--r--gcc-4.9/gcc/config/sol2-clearcap.map2
-rw-r--r--gcc-4.9/gcc/config/sol2-clearcapv2.map7
-rw-r--r--gcc-4.9/gcc/config/sol2.h11
-rw-r--r--gcc-4.9/gcc/config/sol2.opt4
-rw-r--r--gcc-4.9/gcc/config/t-sol27
-rw-r--r--gcc-4.9/gcc/config/v850/rtems.h9
-rw-r--r--gcc-4.9/gcc/config/v850/v850-opts.h9
-rw-r--r--gcc-4.9/gcc/config/v850/v850.h9
-rwxr-xr-xgcc-4.9/gcc/configure190
-rw-r--r--gcc-4.9/gcc/configure.ac95
-rw-r--r--gcc-4.9/gcc/coverage.c1899
-rw-r--r--gcc-4.9/gcc/coverage.h37
-rw-r--r--gcc-4.9/gcc/cp/ChangeLog165
-rw-r--r--gcc-4.9/gcc/cp/call.c78
-rw-r--r--gcc-4.9/gcc/cp/class.c13
-rw-r--r--gcc-4.9/gcc/cp/cp-array-notation.c7
-rw-r--r--gcc-4.9/gcc/cp/cp-gimplify.c23
-rw-r--r--gcc-4.9/gcc/cp/cp-lang.c43
-rw-r--r--gcc-4.9/gcc/cp/cp-objcp-common.c465
-rw-r--r--gcc-4.9/gcc/cp/cp-tree.h49
-rw-r--r--gcc-4.9/gcc/cp/decl.c47
-rw-r--r--gcc-4.9/gcc/cp/decl2.c176
-rw-r--r--gcc-4.9/gcc/cp/error.c5
-rw-r--r--gcc-4.9/gcc/cp/friend.c10
-rw-r--r--gcc-4.9/gcc/cp/init.c85
-rw-r--r--gcc-4.9/gcc/cp/mangle.c33
-rw-r--r--gcc-4.9/gcc/cp/method.c6
-rw-r--r--gcc-4.9/gcc/cp/name-lookup.c54
-rw-r--r--gcc-4.9/gcc/cp/name-lookup.h1
-rw-r--r--gcc-4.9/gcc/cp/parser.c148
-rw-r--r--gcc-4.9/gcc/cp/parser.h9
-rw-r--r--gcc-4.9/gcc/cp/pt.c55
-rw-r--r--gcc-4.9/gcc/cp/rtti.c10
-rw-r--r--gcc-4.9/gcc/cp/semantics.c54
-rw-r--r--gcc-4.9/gcc/cp/tree.c11
-rw-r--r--gcc-4.9/gcc/cp/typeck.c6
-rw-r--r--gcc-4.9/gcc/cp/typeck2.c16
-rw-r--r--gcc-4.9/gcc/dbgcnt.def2
-rw-r--r--gcc-4.9/gcc/dce.c3
-rw-r--r--gcc-4.9/gcc/debug.h1
-rw-r--r--gcc-4.9/gcc/df-problems.c26
-rw-r--r--gcc-4.9/gcc/df.h2
-rw-r--r--gcc-4.9/gcc/diagnostic.c12
-rw-r--r--gcc-4.9/gcc/diagnostic.h3
-rw-r--r--gcc-4.9/gcc/doc/aot-compile.1209
-rw-r--r--gcc-4.9/gcc/doc/arm-acle-intrinsics.texi10
-rw-r--r--gcc-4.9/gcc/doc/arm-neon-intrinsics.texi2
-rw-r--r--gcc-4.9/gcc/doc/cpp.11046
-rw-r--r--gcc-4.9/gcc/doc/cpp.info5602
-rw-r--r--gcc-4.9/gcc/doc/cppinternals.info1029
-rw-r--r--gcc-4.9/gcc/doc/extend.texi13
-rw-r--r--gcc-4.9/gcc/doc/fsf-funding.7193
-rw-r--r--gcc-4.9/gcc/doc/g++.121501
-rw-r--r--gcc-4.9/gcc/doc/gc-analyze.1231
-rw-r--r--gcc-4.9/gcc/doc/gcc.121501
-rw-r--r--gcc-4.9/gcc/doc/gcc.info56908
-rw-r--r--gcc-4.9/gcc/doc/gcc.texi3
-rw-r--r--gcc-4.9/gcc/doc/gccinstall.info4679
-rw-r--r--gcc-4.9/gcc/doc/gccint.info50307
-rw-r--r--gcc-4.9/gcc/doc/gcj-dbtool.1247
-rw-r--r--gcc-4.9/gcc/doc/gcj.1593
-rw-r--r--gcc-4.9/gcc/doc/gcj.info3653
-rw-r--r--gcc-4.9/gcc/doc/gcov-tool.texi189
-rw-r--r--gcc-4.9/gcc/doc/gcov.1733
-rw-r--r--gcc-4.9/gcc/doc/generic.texi10
-rw-r--r--gcc-4.9/gcc/doc/gfdl.71
-rw-r--r--gcc-4.9/gcc/doc/gfortran.11411
-rw-r--r--gcc-4.9/gcc/doc/gij.1295
-rw-r--r--gcc-4.9/gcc/doc/gpl.7850
-rw-r--r--gcc-4.9/gcc/doc/grmic.1222
-rw-r--r--gcc-4.9/gcc/doc/install.texi38
-rw-r--r--gcc-4.9/gcc/doc/invoke.texi352
-rw-r--r--gcc-4.9/gcc/doc/jcf-dump.1217
-rw-r--r--gcc-4.9/gcc/doc/jv-convert.1210
-rw-r--r--gcc-4.9/gcc/doc/md.texi10
-rw-r--r--gcc-4.9/gcc/doc/options.texi4
-rw-r--r--gcc-4.9/gcc/doc/rebuild-gcj-db.1181
-rw-r--r--gcc-4.9/gcc/doc/sourcebuild.texi3
-rw-r--r--gcc-4.9/gcc/doc/tm.texi7
-rw-r--r--gcc-4.9/gcc/doc/tm.texi.in7
-rw-r--r--gcc-4.9/gcc/double-int.c2
-rw-r--r--gcc-4.9/gcc/dumpfile.c6
-rw-r--r--gcc-4.9/gcc/dwarf2out.c207
-rw-r--r--gcc-4.9/gcc/dwarf2out.h4
-rw-r--r--gcc-4.9/gcc/except.c12
-rw-r--r--gcc-4.9/gcc/expmed.c19
-rw-r--r--gcc-4.9/gcc/expr.c14
-rw-r--r--gcc-4.9/gcc/final.c121
-rw-r--r--gcc-4.9/gcc/fold-const.c220
-rw-r--r--gcc-4.9/gcc/fortran/ChangeLog604
-rw-r--r--gcc-4.9/gcc/fortran/cpp.c2
-rw-r--r--gcc-4.9/gcc/fortran/decl.c7
-rw-r--r--gcc-4.9/gcc/fortran/dump-parse-tree.c205
-rw-r--r--gcc-4.9/gcc/fortran/f95-lang.c39
-rw-r--r--gcc-4.9/gcc/fortran/frontend-passes.c73
-rw-r--r--gcc-4.9/gcc/fortran/gfortran.h231
-rw-r--r--gcc-4.9/gcc/fortran/gfortran.info18449
-rw-r--r--gcc-4.9/gcc/fortran/gfortran.texi6
-rw-r--r--gcc-4.9/gcc/fortran/gfortranspec.c38
-rw-r--r--gcc-4.9/gcc/fortran/intrinsic.texi9
-rw-r--r--gcc-4.9/gcc/fortran/match.c29
-rw-r--r--gcc-4.9/gcc/fortran/match.h26
-rw-r--r--gcc-4.9/gcc/fortran/module.c502
-rw-r--r--gcc-4.9/gcc/fortran/openmp.c2341
-rw-r--r--gcc-4.9/gcc/fortran/parse.c520
-rw-r--r--gcc-4.9/gcc/fortran/resolve.c117
-rw-r--r--gcc-4.9/gcc/fortran/scanner.c7
-rw-r--r--gcc-4.9/gcc/fortran/st.c25
-rw-r--r--gcc-4.9/gcc/fortran/symbol.c61
-rw-r--r--gcc-4.9/gcc/fortran/trans-array.c51
-rw-r--r--gcc-4.9/gcc/fortran/trans-array.h4
-rw-r--r--gcc-4.9/gcc/fortran/trans-common.c6
-rw-r--r--gcc-4.9/gcc/fortran/trans-decl.c51
-rw-r--r--gcc-4.9/gcc/fortran/trans-expr.c16
-rw-r--r--gcc-4.9/gcc/fortran/trans-openmp.c2696
-rw-r--r--gcc-4.9/gcc/fortran/trans-stmt.c7
-rw-r--r--gcc-4.9/gcc/fortran/trans-stmt.h1
-rw-r--r--gcc-4.9/gcc/fortran/trans-types.c7
-rw-r--r--gcc-4.9/gcc/fortran/trans.c23
-rw-r--r--gcc-4.9/gcc/fortran/trans.h18
-rw-r--r--gcc-4.9/gcc/function.c35
-rw-r--r--gcc-4.9/gcc/function.h46
-rw-r--r--gcc-4.9/gcc/gcc.c87
-rw-r--r--gcc-4.9/gcc/gcov-counter.def60
-rw-r--r--gcc-4.9/gcc/gcov-dump.c104
-rw-r--r--gcc-4.9/gcc/gcov-io.c90
-rw-r--r--gcc-4.9/gcc/gcov-io.h136
-rw-r--r--gcc-4.9/gcc/gcov-tool.c832
-rw-r--r--gcc-4.9/gcc/gcov.c2
-rw-r--r--gcc-4.9/gcc/gengtype-lex.c2897
-rw-r--r--gcc-4.9/gcc/ggc-page.c15
-rw-r--r--gcc-4.9/gcc/ggc.h3
-rw-r--r--gcc-4.9/gcc/gimple-expr.c5
-rw-r--r--gcc-4.9/gcc/gimple-fold.c4
-rw-r--r--gcc-4.9/gcc/gimple-low.c2
-rw-r--r--gcc-4.9/gcc/gimple-pretty-print.c21
-rw-r--r--gcc-4.9/gcc/gimple.c2
-rw-r--r--gcc-4.9/gcc/gimplify.c205
-rw-r--r--gcc-4.9/gcc/gimplify.h1
-rw-r--r--gcc-4.9/gcc/go/gofrontend/lex.cc2
-rw-r--r--gcc-4.9/gcc/graphite-scop-detection.c6
-rw-r--r--gcc-4.9/gcc/incpath.c24
-rw-r--r--gcc-4.9/gcc/incpath.h3
-rw-r--r--gcc-4.9/gcc/input.c93
-rw-r--r--gcc-4.9/gcc/input.h8
-rw-r--r--gcc-4.9/gcc/ipa-cp.c31
-rw-r--r--gcc-4.9/gcc/ipa-devirt.c6
-rw-r--r--gcc-4.9/gcc/ipa-inline-analysis.c27
-rw-r--r--gcc-4.9/gcc/ipa-inline-transform.c177
-rw-r--r--gcc-4.9/gcc/ipa-inline.c252
-rw-r--r--gcc-4.9/gcc/ipa-inline.h7
-rw-r--r--gcc-4.9/gcc/ipa-prop.c78
-rw-r--r--gcc-4.9/gcc/ipa-prop.h1
-rw-r--r--gcc-4.9/gcc/ipa-pure-const.c6
-rw-r--r--gcc-4.9/gcc/ipa-utils.c4
-rw-r--r--gcc-4.9/gcc/ipa-utils.h6
-rw-r--r--gcc-4.9/gcc/ipa.c75
-rw-r--r--gcc-4.9/gcc/ira-costs.c192
-rw-r--r--gcc-4.9/gcc/ira-int.h5
-rw-r--r--gcc-4.9/gcc/java/Make-lang.in2
-rw-r--r--gcc-4.9/gcc/l-ipo.c2394
-rw-r--r--gcc-4.9/gcc/l-ipo.h68
-rw-r--r--gcc-4.9/gcc/langhooks-def.h48
-rw-r--r--gcc-4.9/gcc/langhooks.c55
-rw-r--r--gcc-4.9/gcc/langhooks.h66
-rw-r--r--gcc-4.9/gcc/loop-iv.c8
-rw-r--r--gcc-4.9/gcc/loop-unroll.c290
-rw-r--r--gcc-4.9/gcc/lra-constraints.c56
-rw-r--r--gcc-4.9/gcc/lra-eliminations.c10
-rw-r--r--gcc-4.9/gcc/lto/ChangeLog5
-rw-r--r--gcc-4.9/gcc/lto/lto-symtab.c7
-rw-r--r--gcc-4.9/gcc/mcf.c163
-rw-r--r--gcc-4.9/gcc/mversn-dispatch.c1769
-rw-r--r--gcc-4.9/gcc/omp-low.c215
-rw-r--r--gcc-4.9/gcc/optabs.c3
-rw-r--r--gcc-4.9/gcc/optabs.def2
-rw-r--r--gcc-4.9/gcc/opts-global.c45
-rw-r--r--gcc-4.9/gcc/opts.c132
-rw-r--r--gcc-4.9/gcc/opts.h16
-rw-r--r--gcc-4.9/gcc/params.c2
-rw-r--r--gcc-4.9/gcc/params.def262
-rw-r--r--gcc-4.9/gcc/passes.c15
-rw-r--r--gcc-4.9/gcc/passes.def2
-rw-r--r--gcc-4.9/gcc/po/ChangeLog4
-rw-r--r--gcc-4.9/gcc/po/be.gmobin10532 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/po/da.gmobin137513 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/po/de.gmobin1197941 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/po/el.gmobin11733 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/po/es.gmobin1129927 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/po/fi.gmobin253499 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/po/fr.gmobin198110 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/po/hr.gmobin16065 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/po/id.gmobin666820 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/po/ja.gmobin493928 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/po/nl.gmobin95067 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/po/ru.gmobin505514 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/po/sr.gmobin652078 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/po/sv.gmobin1298864 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/po/tr.gmobin465450 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/po/vi.gmobin461464 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/po/zh_CN.gmobin791208 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/po/zh_CN.po1532
-rw-r--r--gcc-4.9/gcc/po/zh_TW.gmobin387769 -> 0 bytes
-rw-r--r--gcc-4.9/gcc/predict.c23
-rw-r--r--gcc-4.9/gcc/print-rtl.c9
-rw-r--r--gcc-4.9/gcc/profile.c45
-rw-r--r--gcc-4.9/gcc/profile.h8
-rw-r--r--gcc-4.9/gcc/ree.c53
-rw-r--r--gcc-4.9/gcc/regs.h4
-rw-r--r--gcc-4.9/gcc/rtl.h1
-rw-r--r--gcc-4.9/gcc/sel-sched-ir.c56
-rw-r--r--gcc-4.9/gcc/stmt.c4
-rw-r--r--gcc-4.9/gcc/symtab.c40
-rw-r--r--gcc-4.9/gcc/testsuite/ChangeLog582
-rw-r--r--gcc-4.9/gcc/testsuite/ChangeLog-20133197
-rw-r--r--gcc-4.9/gcc/testsuite/ada/.gitignore2
-rw-r--r--gcc-4.9/gcc/testsuite/c-c++-common/cilk-plus/AN/pr57541-2.c15
-rwxr-xr-xgcc-4.9/gcc/testsuite/c-c++-common/cilk-plus/AN/pr57541.c13
-rw-r--r--gcc-4.9/gcc/testsuite/c-c++-common/cilk-plus/AN/pr58942.c8
-rw-r--r--gcc-4.9/gcc/testsuite/c-c++-common/cilk-plus/AN/pr61191.c10
-rw-r--r--gcc-4.9/gcc/testsuite/c-c++-common/cilk-plus/CK/invalid_sync.cc9
-rw-r--r--gcc-4.9/gcc/testsuite/c-c++-common/gomp/pr59073.c12
-rw-r--r--gcc-4.9/gcc/testsuite/c-c++-common/gomp/pr60823-1.c19
-rw-r--r--gcc-4.9/gcc/testsuite/c-c++-common/gomp/pr60823-2.c44
-rw-r--r--gcc-4.9/gcc/testsuite/c-c++-common/gomp/pr60823-3.c32
-rw-r--r--gcc-4.9/gcc/testsuite/c-c++-common/gomp/pr61486-1.c13
-rw-r--r--gcc-4.9/gcc/testsuite/c-c++-common/gomp/pr61486-2.c458
-rw-r--r--gcc-4.9/gcc/testsuite/c-c++-common/torture/pr60971.c34
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/constexpr-aggr1.C17
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/constexpr-ptrmem2.C13
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/constexpr-template7.C32
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/defaulted49.C15
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/initlist84.C17
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/initlist86.C18
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/lambda/lambda-const3.C38
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/lambda/lambda-template13.C20
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/lambda/lambda-this18.C30
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/nsdmi-template10.C14
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/nsdmi-template11.C15
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/nsdmi-template12.C17
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/nsdmi-template13.C11
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/nsdmi-template9.C16
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/pr58155.C13
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/pr58781.C18
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/pr60249.C6
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/ref-qual15.C13
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/sfinae50.C41
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/variadic158.C24
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/variadic159.C14
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp0x/variadic160.C49
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/cpp1y/pr59867.C52
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/debug/dwarf2/cdtor-1.C2
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/debug/dwarf2/dwarf4-nested.C55
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/debug/dwarf2/dwarf4-typedef.C2
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/debug/dwarf2/imported-decl-2.C32
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/debug/dwarf2/pr61433.C23
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/eh/spec3-static.C25
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/ext/complit14.C11
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/gcov/gcov-7.C28
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/guality/guality.exp3
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/init/copy7.C9
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/ipa/devirt-11.C4
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/ipa/devirt-25.C2
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/ipa/devirt-31.C23
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/ipa/devirt-9.C2
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/ipa/pr60600.C4
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/ipa/pr61085.C33
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/ipa/pr61160-1.C31
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/ipa/pr61160-2.C43
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/ipa/pr61160-3.C37
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/ipa/pr61540.C38
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/opt/pr60849.C13
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/opt/pr60912.C18
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/opt/pr61456.C26
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/opt/pr61654.C27
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/opt/typeinfo1.C27
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/other/no-strict-enum-precision-1.C35
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/other/no-strict-enum-precision-2.C37
-rwxr-xr-xgcc-4.9/gcc/testsuite/g++.dg/other/no-strict-enum-precision-3.C21
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/other/sized-delete-1.C14
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/plugin/selfassign.c4
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/pr60969.C32
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/pr61094.C31
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/pr61289-2.c62
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/pr61289.C63
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/rtti/repo1.C1
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/template/conv14.C30
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/template/local-fn1.C8
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/template/pr61537.C23
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/template/ptrmem27.C22
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/template/ptrmem28.C10
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/thunk_section_name.C30
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tls/thread_local9.C23
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/torture/pr60854.C13
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/torture/pr60895.C32
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/func_reorder_gold_plugin_1.C45
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/func_reorder_gold_plugin_2.C25
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/func_reorder_gold_plugin_3.C25
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/func_reorder_gold_plugin_4.C41
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/func_reorder_gold_plugin_5.C41
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/func_reorder_gold_plugin_6.C53
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/func_reorder_gold_plugin_7.C55
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/func_reorder_gold_plugin_8.C19
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/func_reorder_gold_plugin_split_functions_1.C63
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/lipo/indir-call-prof-2_0.C35
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/lipo/indir-call-prof_0.C39
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/lipo/inline_mismatch_args_0.C36
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/lipo/lipo.exp60
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/lipo/partition1_0.C54
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/lipo/partition2_0.C16
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/lipo/partition3_0.C18
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/lipo/vcall1_0.C41
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/lipo/vcall1_1.C23
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/lipo/vcall1_2.C31
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/morefunc.C55
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/reorder.C48
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/reorder_class1.h11
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/reorder_class2.h12
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-prof/tree-prof.exp4
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-ssa/forwprop-switch.C24
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/tree-ssa/pr61009.C53
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/vect/pr60836.cc39
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/warn/Weff1.C5
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/warn/Wnull-conversion-1.C2
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/warn/Wnull-conversion-2.C58
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/warn/Wself-assign-1.C54
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/warn/Wself-assign-3.C35
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/warn/Wself-assign-4.C48
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/warn/Wself-assign-5.C38
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/warn/Wself-assign-non-pod-1.C54
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/warn/Wself-assign-non-pod-3.C35
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/warn/Wself-assign-non-pod-4.C48
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/warn/Wself-assign-non-pod-5.C38
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/warn/Wshadow-compatible-local-1.C63
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/warn/Wshadow-local-1.C35
-rw-r--r--gcc-4.9/gcc/testsuite/g++.dg/warn/Wshadow-local-2.C63
-rw-r--r--gcc-4.9/gcc/testsuite/g++.old-deja/g++.benjamin/15309-1.C21
-rw-r--r--gcc-4.9/gcc/testsuite/g++.old-deja/g++.benjamin/15309-2.C10
-rw-r--r--gcc-4.9/gcc/testsuite/g++.old-deja/g++.ext/memconst.C2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.c-torture/compile/pr61684.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.c-torture/execute/20140425-1.c23
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.c-torture/execute/pr60960.c38
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.c-torture/execute/pr61306-1.c39
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.c-torture/execute/pr61306-2.c40
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.c-torture/execute/pr61306-3.c13
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.c-torture/execute/pr61673.c50
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.c-torture/execute/pr61725.c14
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/Wshadow-compatible-local-1.c36
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/Wshadow-local-1.c23
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/Wshadow-local-2.c49
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/Wshadow-local-3.c9
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/autopar/outer-1.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/autopar/outer-3.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/autopar/outer-4.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/autopar/outer-5.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/autopar/parallelization-1.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/autopar/reduc-1.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/autopar/reduc-1char.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/autopar/reduc-1short.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/autopar/reduc-2.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/autopar/reduc-2char.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/autopar/reduc-2short.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/autopar/reduc-3.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/autopar/reduc-6.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/autopar/reduc-7.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/autopar/reduc-8.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/autopar/reduc-9.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/debug/dwarf2/mlt1.c32
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/debug/dwarf2/mlt2.c31
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/fstack-protector-strong.c5
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/graphite/pr55022.c27
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/graphite/pr59817-1.c16
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/graphite/pr59817-2.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/graphite/pr60979.c37
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/guality/guality.exp3
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/lto/pr60720_0.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/lto/pr60720_1.c1
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/lto/pr60911_0.c21
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/lto/pr61526_0.c6
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/lto/pr61526_1.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/plugin/selfassign.c4
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/pr47793.c1
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/pr53265.c4
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/pr57233.c171
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/pr60844.c16
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/pr60866.c18
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/pr61045.c12
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/pr61053.c75
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/pr61060.c19
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/pr61158.c12
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/pr61583.c18
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/record-compilation-info-in-elf-1.c16
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/torture/pr56965-1.c32
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/torture/pr56965-2.c34
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/torture/pr57864.c37
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/torture/pr60891.c23
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/torture/pr60903.c22
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/torture/pr60930.c22
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/torture/pr61010.c8
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/torture/pr61383-1.c35
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/torture/pr61452.c31
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/torture/pr61681.c37
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/crossmodule-indircall-1a.c1
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/inliner-1.c4
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/bb-reorg_0.c39
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/ic-misattribution-1_0.c19
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/ic-misattribution-1_1.c18
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/indir-call-prof-single_0.c43
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/indir-call-prof_0.c23
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/indir-call-prof_1.c23
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/inliner-1_0.c42
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/lipo.exp60
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/lipo_inline1_0.c29
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/lipo_inline1_1.c22
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/lipo_inline1_2.c6
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/pr34999_0.c45
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/pr45354_0.c43
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/pr47187_0.c23
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/stringop-1_0.c22
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/stringop-2_0.c20
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/tracer-1_0.c18
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/update-cunroll-2_0.c21
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/update-loopch_0.c20
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/update-tailcall_0.c20
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/val-prof-1_0.c22
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/val-prof-2_0.c32
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/val-prof-3_0.c32
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/val-prof-4_0.c32
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/val-prof-5_0.c17
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/val-prof-6_0.c20
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/val-prof-7_0.c26
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/lipo/wcoverage-mismatch_0.c20
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-prof/merge_block.c21
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-ssa/ivopt_1.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-ssa/ivopt_2.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-ssa/ivopt_4.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-ssa/ivopts-lt.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-ssa/loop-16.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-ssa/predcom-1.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-ssa/predcom-4.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-ssa/predcom-5.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-ssa/prefetch-7.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-ssa/prefetch-8.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-ssa/prefetch-9.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/tree-ssa/vrp93.c36
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/typeof-2.c28
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/unused-8b.c4
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/var-expand1.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/vect/pr60841.c183
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/vect/pr61680.c51
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/vect/vect-reduc-sad.c54
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/vect/vect-singleton_1.c38
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/vect/vect.exp25
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/wself-assign-1.c27
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.dg/wself-assign-2.c24
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.misc-tests/help.exp2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/aapcs64/type-def.h7
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/aapcs64/va_arg-13.c59
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/aapcs64/va_arg-14.c35
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/aapcs64/va_arg-15.c39
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/pr61325.c19
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/scalar_intrinsics.c26
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vector_intrinsics.c14
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlal_high_lane_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlal_high_lane_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlal_high_laneq_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlal_high_laneq_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlal_lane_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlal_lane_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlal_laneq_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlal_laneq_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlalh_lane_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlals_lane_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlsl_high_lane_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlsl_high_lane_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlsl_high_laneq_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlsl_high_laneq_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlsl_lane_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlsl_lane_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlsl_laneq_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlslh_lane_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmlsls_lane_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmulh_laneq_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmulh_laneq_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmulhh_lane_s16.c36
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmulhq_laneq_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmulhq_laneq_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmulhs_lane_s32.c34
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmull_high_lane_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmull_high_lane_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmull_high_laneq_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmull_high_laneq_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmull_lane_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmull_lane_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmull_laneq_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmull_laneq_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmullh_lane_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqdmulls_lane_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqrdmulh_laneq_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqrdmulh_laneq_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqrdmulhh_lane_s16.c35
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqrdmulhq_laneq_s16.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqrdmulhq_laneq_s32.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/aarch64/vqrdmulhs_lane_s32.c35
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/alpha/pr61586.c10
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/arm/pr48252.c13
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/avr/pr60991.c21
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/avr/torture/pr61055.c88
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/avr/torture/pr61443.c134
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/avx-pr57233.c16
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/avx2-pr57233.c16
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/avx2-vpaddb-3.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/avx2-vpaddw-3.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/avx2-vpmullw-3.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/avx2-vpsraw-3.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/avx2-vpsrlw-3.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/avx2-vpsubb-3.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/avx2-vpsubw-3.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/avx512f-pr57233.c16
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi-andn-1a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi-andn-2a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi-bextr-1a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi-bextr-2a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi-blsi-1a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi-blsi-2a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi-blsmsk-1a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi-blsmsk-2a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi-blsr-1a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi-blsr-2a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi-tzcnt-1a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi-tzcnt-2a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi2-bzhi32-1a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi2-bzhi64-1a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi2-pdep32-1a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi2-pdep64-1a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi2-pext32-1a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/bmi2-pext64-1a.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/cadd.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/clearcap.map3
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/clearcapv2.map7
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/i386.exp36
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/patch-functions-1.c23
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/patch-functions-2.c21
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/patch-functions-3.c21
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/patch-functions-4.c22
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/patch-functions-5.c22
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/patch-functions-6.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/patch-functions-7.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/patch-functions-8.c29
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/patch-functions-force-no-patching.c27
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/patch-functions-force-patching.c20
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/patch-functions-sibling-call.c26
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/pie-copyrelocs-1.c13
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/pie-copyrelocs-2.c13
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/pr50038.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/pr57233.c15
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/pr60868.c10
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/pr60901.c17
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/pr60902.c32
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/pr60909-1.c11
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/pr60909-2.c11
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/pr61423.c38
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/pr61446.c14
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/pr61599-1.c13
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/pr61599-2.c13
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/recip-vec-sqrtf-avx.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/sse2-pr57233.c16
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/sse2-unaligned-mov.c20
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/sse4_1-roundss-1.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/sse4_1-roundss-2.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/sse4_1-roundss-3.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/vec-may_alias.c25
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/wmul-1.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/i386/xop-pr57233.c16
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/powerpc/bcd-1.c27
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/powerpc/bcd-2.c44
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/powerpc/bcd-3.c103
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/powerpc/dfp-builtin-1.c88
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/powerpc/dfp-builtin-2.c88
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/powerpc/extend-divide-1.c34
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/powerpc/extend-divide-2.c34
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/powerpc/htm-ttest.c14
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/powerpc/pack01.c91
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/powerpc/pack02.c96
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/powerpc/pack03.c88
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/powerpc/pr60735.c11
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/powerpc/tfmode_off.c1
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/powerpc/ti_math1.c20
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/powerpc/ti_math2.c73
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/s390/htm-nofloat-2.c55
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/x86_64/abi/avx/abi-avx.exp16
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/x86_64/abi/avx512f/abi-avx512f.exp16
-rw-r--r--gcc-4.9/gcc/testsuite/gcc.target/x86_64/abi/callabi/leaf-2.c2
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/allocatable_function_8.f9059
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/arrayio_14.f9018
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/arrayio_15.f9011
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/arrayio_16.f9013
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/associate_16.f9023
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/associate_17.f9012
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/class_array_15.f033
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/cray_pointers_10.f9018
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/default_format_denormal_2.f904
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/finalize_25.f9055
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/affinity-1.f9019
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/allocatable_components_1.f9010
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/appendix-a/a.31.3.f902
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/associate1.f9083
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/declare-simd-1.f909
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/depend-1.f9013
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/intentin1.f9016
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/omp_do_concurrent.f9013
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/openmp-simd-1.f90137
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/openmp-simd-2.f9028
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/openmp-simd-3.f9028
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/proc_ptr_2.f9014
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/reduction1.f9068
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/reduction3.f908
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/target1.f90520
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/target2.f9074
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/target3.f9012
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/udr1.f9041
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/udr2.f9053
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/udr3.f9075
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/udr4.f9074
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/udr5.f9059
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/udr6.f90205
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/udr7.f9090
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/gomp/udr8.f90351
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/graphite/pr59817.f14
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/guality/guality.exp3
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/list_read_13.f13
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/nint_2.f903
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/oldstyle_5.f8
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/openmp-define-3.f902
-rw-r--r--gcc-4.9/gcc/testsuite/gfortran.dg/round_4.f901
-rw-r--r--gcc-4.9/gcc/testsuite/gnat.dg/aliasing1.adb2
-rw-r--r--gcc-4.9/gcc/testsuite/gnat.dg/enum3.adb23
-rw-r--r--gcc-4.9/gcc/testsuite/gnat.dg/opt38.adb9
-rw-r--r--gcc-4.9/gcc/testsuite/gnat.dg/opt38_pkg.adb33
-rw-r--r--gcc-4.9/gcc/testsuite/gnat.dg/opt38_pkg.ads5
-rw-r--r--gcc-4.9/gcc/testsuite/gnat.dg/opt39.adb31
-rw-r--r--gcc-4.9/gcc/testsuite/gnat.dg/overflow_fixed.adb19
-rw-r--r--gcc-4.9/gcc/testsuite/lib/asan-dg.exp6
-rw-r--r--gcc-4.9/gcc/testsuite/lib/clearcap.exp58
-rw-r--r--gcc-4.9/gcc/testsuite/lib/gcov.exp2
-rw-r--r--gcc-4.9/gcc/testsuite/lib/profopt.exp76
-rw-r--r--gcc-4.9/gcc/testsuite/lib/target-supports-dg.exp19
-rw-r--r--gcc-4.9/gcc/testsuite/lib/target-supports.exp53
-rw-r--r--gcc-4.9/gcc/testsuite/lib/target-supports.exp.orig5791
-rw-r--r--gcc-4.9/gcc/testsuite/lib/ubsan-dg.exp6
-rw-r--r--gcc-4.9/gcc/timevar.def1
-rw-r--r--gcc-4.9/gcc/toplev.c28
-rw-r--r--gcc-4.9/gcc/tree-cfg.c127
-rw-r--r--gcc-4.9/gcc/tree-core.h22
-rw-r--r--gcc-4.9/gcc/tree-diagnostic.c2
-rw-r--r--gcc-4.9/gcc/tree-inline.c65
-rw-r--r--gcc-4.9/gcc/tree-nested.c238
-rw-r--r--gcc-4.9/gcc/tree-pass.h2
-rw-r--r--gcc-4.9/gcc/tree-pretty-print.c21
-rw-r--r--gcc-4.9/gcc/tree-profile.c868
-rw-r--r--gcc-4.9/gcc/tree-sra.c13
-rw-r--r--gcc-4.9/gcc/tree-ssa-alias.c147
-rw-r--r--gcc-4.9/gcc/tree-ssa-forwprop.c55
-rw-r--r--gcc-4.9/gcc/tree-ssa-ifcombine.c7
-rw-r--r--gcc-4.9/gcc/tree-ssa-live.c2
-rw-r--r--gcc-4.9/gcc/tree-ssa-loop-ivcanon.c2
-rw-r--r--gcc-4.9/gcc/tree-ssa-math-opts.c73
-rw-r--r--gcc-4.9/gcc/tree-ssa-operands.c1
-rw-r--r--gcc-4.9/gcc/tree-ssa-sccvn.c89
-rw-r--r--gcc-4.9/gcc/tree-ssa-structalias.c4
-rw-r--r--gcc-4.9/gcc/tree-ssa-tail-merge.c21
-rw-r--r--gcc-4.9/gcc/tree-ssa-threadedge.c113
-rw-r--r--gcc-4.9/gcc/tree-ssa-uninit.c1
-rw-r--r--gcc-4.9/gcc/tree-ssa.c1
-rw-r--r--gcc-4.9/gcc/tree-streamer-in.c3
-rw-r--r--gcc-4.9/gcc/tree-vect-data-refs.c13
-rw-r--r--gcc-4.9/gcc/tree-vect-generic.c161
-rw-r--r--gcc-4.9/gcc/tree-vect-loop.c1
-rw-r--r--gcc-4.9/gcc/tree-vect-patterns.c244
-rw-r--r--gcc-4.9/gcc/tree-vectorizer.h2
-rw-r--r--gcc-4.9/gcc/tree-vrp.c12
-rw-r--r--gcc-4.9/gcc/tree.c12
-rw-r--r--gcc-4.9/gcc/tree.def16
-rw-r--r--gcc-4.9/gcc/tree.h12
-rw-r--r--gcc-4.9/gcc/value-prof.c454
-rw-r--r--gcc-4.9/gcc/value-prof.h8
-rw-r--r--gcc-4.9/gcc/varasm.c28
-rw-r--r--gcc-4.9/gcc/varpool.c25
-rw-r--r--gcc-4.9/include/ChangeLog6
-rw-r--r--gcc-4.9/libatomic/.gitignore2
-rwxr-xr-xgcc-4.9/libatomic/configure36
-rw-r--r--gcc-4.9/libatomic/configure.ac1
-rw-r--r--gcc-4.9/libatomic/testsuite/atomicconfig.exp.in2
-rw-r--r--gcc-4.9/libatomic/testsuite/config/default.exp1
-rw-r--r--gcc-4.9/libatomic/testsuite/lib/libatomic.exp2
-rw-r--r--gcc-4.9/libcpp/ChangeLog7
-rw-r--r--gcc-4.9/libcpp/lex.c4
-rw-r--r--gcc-4.9/libcpp/po/be.gmobin1003 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/ca.gmobin17214 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/da.gmobin13534 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/de.gmobin21755 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/el.gmobin703 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/eo.gmobin20961 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/es.gmobin21317 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/fi.gmobin22216 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/fr.gmobin20027 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/id.gmobin20470 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/ja.gmobin23362 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/nl.gmobin21687 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/pt_BR.gmobin21909 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/ru.gmobin28665 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/sr.gmobin27039 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/sv.gmobin21236 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/tr.gmobin20851 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/uk.gmobin28056 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/vi.gmobin25186 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/zh_CN.gmobin19082 -> 0 bytes
-rw-r--r--gcc-4.9/libcpp/po/zh_TW.gmobin19496 -> 0 bytes
-rw-r--r--gcc-4.9/libdecnumber/.gitignore1
-rwxr-xr-xgcc-4.9/libffi/configure21
-rw-r--r--gcc-4.9/libffi/doc/libffi.info618
-rw-r--r--gcc-4.9/libgcc/ChangeLog88
-rw-r--r--gcc-4.9/libgcc/Makefile.in71
-rw-r--r--gcc-4.9/libgcc/config.host11
-rw-r--r--gcc-4.9/libgcc/config/arm/bpabi-lib.h4
-rw-r--r--gcc-4.9/libgcc/config/arm/lib1funcs.S4
-rw-r--r--gcc-4.9/libgcc/config/arm/sfp-machine.h8
-rw-r--r--gcc-4.9/libgcc/config/mips/linux-unwind.h2
-rw-r--r--gcc-4.9/libgcc/config/msp430/t-msp4302
-rw-r--r--gcc-4.9/libgcc/config/t-slibgcc-sld4
-rw-r--r--gcc-4.9/libgcc/config/t-static-no-vis-hide2
-rw-r--r--gcc-4.9/libgcc/configure634
-rw-r--r--gcc-4.9/libgcc/configure.ac8
-rw-r--r--gcc-4.9/libgcc/dyn-ipa.c2540
-rw-r--r--gcc-4.9/libgcc/libgcov-driver-system.c91
-rw-r--r--gcc-4.9/libgcc/libgcov-driver.c276
-rw-r--r--gcc-4.9/libgcc/libgcov-interface.c53
-rw-r--r--gcc-4.9/libgcc/libgcov-merge.c145
-rw-r--r--gcc-4.9/libgcc/libgcov-profiler.c219
-rw-r--r--gcc-4.9/libgcc/libgcov-util.c1162
-rw-r--r--gcc-4.9/libgcc/libgcov.h205
-rw-r--r--gcc-4.9/libgcc/pmu-profile.c1552
-rw-r--r--gcc-4.9/libgfortran/ChangeLog42
-rwxr-xr-xgcc-4.9/libgfortran/configure21
-rw-r--r--gcc-4.9/libgfortran/intrinsics/ctime.c70
-rw-r--r--gcc-4.9/libgfortran/io/list_read.c47
-rw-r--r--gcc-4.9/libgfortran/io/unix.c18
-rw-r--r--gcc-4.9/libgo/runtime/proc.c3
-rw-r--r--gcc-4.9/libgomp/ChangeLog131
-rw-r--r--gcc-4.9/libgomp/config/linux/proc.c7
-rwxr-xr-xgcc-4.9/libgomp/configure24
-rw-r--r--gcc-4.9/libgomp/configure.ac1
-rw-r--r--gcc-4.9/libgomp/configure.tgt3
-rw-r--r--gcc-4.9/libgomp/libgomp.info3232
-rw-r--r--gcc-4.9/libgomp/libgomp.texi84
-rw-r--r--gcc-4.9/libgomp/omp_lib.f90.in2
-rw-r--r--gcc-4.9/libgomp/omp_lib.h.in2
-rw-r--r--gcc-4.9/libgomp/testsuite/config/default.exp1
-rw-r--r--gcc-4.9/libgomp/testsuite/gompconfig.exp.in2
-rw-r--r--gcc-4.9/libgomp/testsuite/lib/libgomp.exp5
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c++/for-10.C3
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c++/simd-9.C52
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c++/simd10.C6
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c++/simd11.C6
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c++/simd12.C6
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c++/simd13.C6
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c/for-2.c3
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c/for-2.h21
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c/loop-16.c27
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c/simd-10.c26
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c/simd-11.c27
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c/simd-12.c19
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c/simd-13.c18
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c/simd-14.c123
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c/simd-15.c129
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c/simd-16.c67
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c/simd-17.c73
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c/simd-7.c96
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c/simd-8.c44
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c/simd-9.c70
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.c/target-8.c26
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/aligned1.f03133
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/alloc-comp-1.f90328
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/alloc-comp-2.f90367
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/alloc-comp-3.f90372
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/allocatable10.f90112
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/allocatable11.f9072
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/allocatable12.f9074
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/allocatable9.f90156
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/associate1.f9023
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/associate2.f9046
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/cancel-do-1.f9014
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/cancel-do-2.f9090
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/cancel-parallel-1.f9010
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/cancel-parallel-3.f9038
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/cancel-sections-1.f9023
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/cancel-taskgroup-2.f9028
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/declare-simd-1.f9095
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/declare-simd-2.f9025
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/declare-simd-3.f9022
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/depend-1.f90203
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/depend-2.f9034
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/depend-3.f9042
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/nestedfn5.f9096
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/omp_atomic5.f9059
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/openmp_version-1.f2
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/openmp_version-2.f902
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/procptr1.f9042
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/simd1.f9035
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/simd2.f90101
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/simd3.f90109
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/simd4.f90103
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/simd5.f90124
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/simd6.f90135
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/simd7.f90172
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/target1.f9058
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/target2.f9096
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/target3.f9029
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/target4.f9048
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/target5.f9021
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/target6.f9050
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/target7.f9038
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/target8.f9033
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/taskgroup1.f9080
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/udr1.f9051
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/udr10.f9032
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/udr11.f9095
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/udr12.f9076
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/udr13.f90106
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/udr14.f9050
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/udr15.f9064
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/udr2.f9051
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/udr3.f9038
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/udr4.f9050
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/udr5.f9057
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/udr6.f9069
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/udr7.f9046
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/udr8.f9046
-rw-r--r--gcc-4.9/libgomp/testsuite/libgomp.fortran/udr9.f9065
-rw-r--r--gcc-4.9/libiberty/.gitignore2
-rw-r--r--gcc-4.9/libitm/ChangeLog7
-rw-r--r--gcc-4.9/libitm/acinclude.m410
-rw-r--r--gcc-4.9/libitm/clearcap.map14
-rw-r--r--gcc-4.9/libitm/configure8
-rw-r--r--gcc-4.9/libitm/libitm.info1293
-rw-r--r--gcc-4.9/libjava/classpath/.cvsignore18
-rwxr-xr-xgcc-4.9/libjava/classpath/configure29
-rw-r--r--gcc-4.9/libjava/classpath/doc/.cvsignore13
-rw-r--r--gcc-4.9/libjava/classpath/doc/api/.cvsignore2
-rw-r--r--gcc-4.9/libjava/classpath/doc/cp-tools.info3146
-rw-r--r--gcc-4.9/libjava/classpath/doc/gappletviewer.1249
-rw-r--r--gcc-4.9/libjava/classpath/doc/gjar.1216
-rw-r--r--gcc-4.9/libjava/classpath/doc/gjarsigner.1221
-rw-r--r--gcc-4.9/libjava/classpath/doc/gjavah.1212
-rw-r--r--gcc-4.9/libjava/classpath/doc/gjdoc.1915
-rw-r--r--gcc-4.9/libjava/classpath/doc/gkeytool.1697
-rw-r--r--gcc-4.9/libjava/classpath/doc/gnative2ascii.1174
-rw-r--r--gcc-4.9/libjava/classpath/doc/gorbd.1181
-rw-r--r--gcc-4.9/libjava/classpath/doc/grmid.1193
-rw-r--r--gcc-4.9/libjava/classpath/doc/grmiregistry.1190
-rw-r--r--gcc-4.9/libjava/classpath/doc/gserialver.1171
-rw-r--r--gcc-4.9/libjava/classpath/doc/gtnameserv.1174
-rw-r--r--gcc-4.9/libjava/classpath/examples/.cvsignore6
-rw-r--r--gcc-4.9/libjava/classpath/external/.cvsignore2
-rw-r--r--gcc-4.9/libjava/classpath/external/jsr166/.cvsignore1
-rw-r--r--gcc-4.9/libjava/classpath/external/relaxngDatatype/.cvsignore2
-rw-r--r--gcc-4.9/libjava/classpath/external/sax/.cvsignore2
-rw-r--r--gcc-4.9/libjava/classpath/external/w3c_dom/.cvsignore2
-rw-r--r--gcc-4.9/libjava/classpath/gnu/classpath/.cvsignore1
-rw-r--r--gcc-4.9/libjava/classpath/gnu/java/locale/.cvsignore1
-rw-r--r--gcc-4.9/libjava/classpath/gnu/java/security/.cvsignore1
-rw-r--r--gcc-4.9/libjava/classpath/gnu/test/.cvsignore1
-rw-r--r--gcc-4.9/libjava/classpath/include/.cvsignore9
-rw-r--r--gcc-4.9/libjava/classpath/java/util/.cvsignore1
-rw-r--r--gcc-4.9/libjava/classpath/lib/.cvsignore38
-rw-r--r--gcc-4.9/libjava/classpath/native/.cvsignore8
-rw-r--r--gcc-4.9/libjava/classpath/native/fdlibm/.cvsignore8
-rw-r--r--gcc-4.9/libjava/classpath/native/jawt/.cvsignore8
-rw-r--r--gcc-4.9/libjava/classpath/native/jni/.cvsignore8
-rw-r--r--gcc-4.9/libjava/classpath/native/jni/classpath/.cvsignore8
-rw-r--r--gcc-4.9/libjava/classpath/native/jni/gconf-peer/.cvsignore6
-rw-r--r--gcc-4.9/libjava/classpath/native/jni/gtk-peer/.cvsignore8
-rw-r--r--gcc-4.9/libjava/classpath/native/jni/java-io/.cvsignore8
-rw-r--r--gcc-4.9/libjava/classpath/native/jni/java-lang/.cvsignore8
-rw-r--r--gcc-4.9/libjava/classpath/native/jni/java-net/.cvsignore8
-rw-r--r--gcc-4.9/libjava/classpath/native/jni/java-nio/.cvsignore8
-rw-r--r--gcc-4.9/libjava/classpath/native/jni/java-util/.cvsignore8
-rw-r--r--gcc-4.9/libjava/classpath/native/jni/midi-alsa/.cvsignore9
-rw-r--r--gcc-4.9/libjava/classpath/native/jni/midi-dssi/.cvsignore9
-rw-r--r--gcc-4.9/libjava/classpath/native/jni/native-lib/.cvsignore8
-rw-r--r--gcc-4.9/libjava/classpath/native/jni/qt-peer/.cvsignore9
-rw-r--r--gcc-4.9/libjava/classpath/native/jni/xmlj/.cvsignore8
-rw-r--r--gcc-4.9/libjava/classpath/native/plugin/.cvsignore6
-rw-r--r--gcc-4.9/libjava/classpath/resource/.cvsignore2
-rw-r--r--gcc-4.9/libjava/classpath/resource/META-INF/services/.cvsignore1
-rw-r--r--gcc-4.9/libjava/classpath/scripts/.cvsignore3
-rw-r--r--gcc-4.9/libjava/classpath/tools/.cvsignore19
-rw-r--r--gcc-4.9/libjava/classpath/vm/.cvsignore2
-rw-r--r--gcc-4.9/libjava/classpath/vm/reference/.cvsignore2
-rwxr-xr-xgcc-4.9/libjava/configure17
-rwxr-xr-xgcc-4.9/libobjc/configure23
-rwxr-xr-xgcc-4.9/libquadmath/configure21
-rw-r--r--gcc-4.9/libquadmath/libquadmath.info808
-rwxr-xr-xgcc-4.9/libssp/configure24
-rw-r--r--gcc-4.9/libssp/configure.ac3
-rw-r--r--gcc-4.9/libstdc++-v3/ChangeLog111
-rw-r--r--gcc-4.9/libstdc++-v3/acinclude.m420
-rw-r--r--gcc-4.9/libstdc++-v3/config.h.in10
-rw-r--r--gcc-4.9/libstdc++-v3/config/abi/post/x86_64-linux-gnu/32/baseline_symbols.txt3
-rw-r--r--gcc-4.9/libstdc++-v3/config/abi/post/x86_64-linux-gnu/baseline_symbols.txt1
-rw-r--r--gcc-4.9/libstdc++-v3/config/abi/pre/gnu.ver3
-rw-r--r--gcc-4.9/libstdc++-v3/config/locale/generic/c_locale.cc12
-rw-r--r--gcc-4.9/libstdc++-v3/config/locale/generic/c_locale.h19
-rw-r--r--gcc-4.9/libstdc++-v3/config/locale/generic/time_members.cc8
-rw-r--r--gcc-4.9/libstdc++-v3/config/os/bionic/ctype_base.h2
-rwxr-xr-xgcc-4.9/libstdc++-v3/configure52
-rw-r--r--gcc-4.9/libstdc++-v3/configure.ac6
-rw-r--r--gcc-4.9/libstdc++-v3/include/Makefile.am1
-rw-r--r--gcc-4.9/libstdc++-v3/include/Makefile.in1
-rw-r--r--gcc-4.9/libstdc++-v3/include/backward/hashtable.h3
-rw-r--r--gcc-4.9/libstdc++-v3/include/bits/deque.tcc16
-rw-r--r--gcc-4.9/libstdc++-v3/include/bits/hashtable.h146
-rw-r--r--gcc-4.9/libstdc++-v3/include/bits/regex_automaton.tcc18
-rw-r--r--gcc-4.9/libstdc++-v3/include/bits/regex_compiler.h11
-rw-r--r--gcc-4.9/libstdc++-v3/include/bits/regex_compiler.tcc17
-rw-r--r--gcc-4.9/libstdc++-v3/include/bits/regex_executor.tcc6
-rw-r--r--gcc-4.9/libstdc++-v3/include/bits/stl_algo.h80
-rw-r--r--gcc-4.9/libstdc++-v3/include/bits/stl_bvector.h245
-rw-r--r--gcc-4.9/libstdc++-v3/include/bits/stl_deque.h56
-rw-r--r--gcc-4.9/libstdc++-v3/include/bits/stl_tree.h44
-rw-r--r--gcc-4.9/libstdc++-v3/include/bits/stl_vector.h262
-rw-r--r--gcc-4.9/libstdc++-v3/include/bits/vector.tcc52
-rw-r--r--gcc-4.9/libstdc++-v3/include/ext/new_allocator.h7
-rw-r--r--gcc-4.9/libstdc++-v3/include/ext/sso_string_base.h44
-rw-r--r--gcc-4.9/libstdc++-v3/include/ext/vstring.h39
-rw-r--r--gcc-4.9/libstdc++-v3/include/std/future29
-rw-r--r--gcc-4.9/libstdc++-v3/include/std/iomanip38
-rw-r--r--gcc-4.9/libstdc++-v3/include/std/tuple26
-rw-r--r--gcc-4.9/libstdc++-v3/include/std/type_traits39
-rw-r--r--gcc-4.9/libstdc++-v3/include/tr2/bool_set2
-rw-r--r--gcc-4.9/libstdc++-v3/libsupc++/Makefile.am10
-rw-r--r--gcc-4.9/libstdc++-v3/libsupc++/Makefile.in11
-rw-r--r--gcc-4.9/libstdc++-v3/libsupc++/del_opsz.cc50
-rw-r--r--gcc-4.9/libstdc++-v3/libsupc++/eh_arm.cc4
-rw-r--r--gcc-4.9/libstdc++-v3/libsupc++/guard.cc22
-rw-r--r--gcc-4.9/libstdc++-v3/libsupc++/new2
-rw-r--r--gcc-4.9/libstdc++-v3/scripts/run_doxygen11
-rw-r--r--gcc-4.9/libstdc++-v3/src/Makefile.am5
-rw-r--r--gcc-4.9/libstdc++-v3/src/Makefile.in6
-rw-r--r--gcc-4.9/libstdc++-v3/src/c++11/Makefile.am9
-rw-r--r--gcc-4.9/libstdc++-v3/src/c++11/Makefile.in9
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/alignment_of/requirements/explicit_instantiation.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/alignment_of/requirements/typedefs.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/alignment_of/value.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/declval/requirements/1_neg.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/function/60594.cc36
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/has_virtual_destructor/requirements/explicit_instantiation.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/has_virtual_destructor/requirements/typedefs.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/has_virtual_destructor/value.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/is_array/requirements/explicit_instantiation.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/is_array/requirements/typedefs.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/is_array/value.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/is_enum/requirements/explicit_instantiation.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/is_enum/requirements/typedefs.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/is_enum/value.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/is_union/requirements/explicit_instantiation.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/is_union/requirements/typedefs.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/is_union/value.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/make_signed/requirements/typedefs-1.cc5
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/make_signed/requirements/typedefs-2.cc6
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/make_signed/requirements/typedefs-3.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/make_signed/requirements/typedefs-4.cc33
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/make_signed/requirements/typedefs_neg.cc4
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/make_unsigned/requirements/typedefs-1.cc5
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/make_unsigned/requirements/typedefs-2.cc6
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/make_unsigned/requirements/typedefs_neg.cc4
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/shared_ptr/cons/61036.cc28
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/tuple/60497.cc37
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/tuple/element_access/get_by_type.cc4
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/20_util/tuple/tuple_element_t.cc36
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/23_containers/deque/requirements/dr438/assign_neg.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/23_containers/deque/requirements/dr438/constructor_1_neg.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/23_containers/deque/requirements/dr438/constructor_2_neg.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/23_containers/deque/requirements/dr438/insert_neg.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/23_containers/set/cons/61023.cc56
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/23_containers/unordered_set/61143.cc38
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/23_containers/unordered_set/modifiers/swap.cc65
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/23_containers/vector/requirements/dr438/assign_neg.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/23_containers/vector/requirements/dr438/constructor_1_neg.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/23_containers/vector/requirements/dr438/constructor_2_neg.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/23_containers/vector/requirements/dr438/insert_neg.cc2
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/27_io/manipulators/standard/char/dr2344.cc50
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/27_io/manipulators/standard/wchar_t/dr2344.cc50
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/28_regex/algorithms/regex_match/ecma/char/quoted_char.cc10
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/28_regex/basic_regex/multiple_quantifiers.cc4
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/30_threads/promise/60966.cc67
-rw-r--r--gcc-4.9/libstdc++-v3/testsuite/libstdc++-prettyprinters/simple11.cc92
-rw-r--r--gcc-4.9/ltmain.sh44
-rw-r--r--gcc-4.9/lto-plugin/ChangeLog6
-rwxr-xr-xgcc-4.9/lto-plugin/configure47
-rw-r--r--gcc-4.9/lto-plugin/configure.ac14
-rw-r--r--gcc-4.9/ltoptions.m417
-rwxr-xr-xgcc-4.9/zlib/configure21
1168 files changed, 85986 insertions, 323684 deletions
diff --git a/gcc-4.9/.dir-locals.el b/gcc-4.9/.dir-locals.el
new file mode 100644
index 0000000..b748c8d
--- /dev/null
+++ b/gcc-4.9/.dir-locals.el
@@ -0,0 +1,24 @@
+;; Emacs settings.
+;; Copyright (C) 2012-2013 Free Software Foundation, Inc.
+
+;; This program is free software; you can redistribute it and/or modify
+;; it under the terms of the GNU General Public License as published by
+;; the Free Software Foundation; either version 3 of the License, or
+;; (at your option) any later version.
+
+;; This program is distributed in the hope that it will be useful,
+;; but WITHOUT ANY WARRANTY; without even the implied warranty of
+;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+;; GNU General Public License for more details.
+
+;; You should have received a copy of the GNU General Public License
+;; along with this program. If not, see <http://www.gnu.org/licenses/>.
+
+(
+ (tcl-mode . ((tcl-indent-level . 4)
+ (tcl-continued-indent-level . 4)
+ (indent-tabs-mode . t)))
+ (nil . ((bug-reference-url-format . "http://gcc.gnu.org/PR%s")))
+ (c-mode . ((c-file-style . "GNU")
+ (indent-tabs-mode . t)))
+)
diff --git a/gcc-4.9/.gitignore b/gcc-4.9/.gitignore
new file mode 100644
index 0000000..bda55a3
--- /dev/null
+++ b/gcc-4.9/.gitignore
@@ -0,0 +1,42 @@
+*.diff
+*.patch
+*.orig
+*.rej
+
+*~
+.#*
+*#
+
+*.flt
+*.gmo
+*.info
+*.la
+*.lo
+*.o
+*.pyc
+*.tmp
+
+.deps
+.libs
+
+autom4te.cache
+config.cache
+config.h
+config.intl
+config.log
+config.status
+libtool
+POTFILES
+*-POTFILES
+
+TAGS
+TAGS.sub
+
+.gdbinit
+.gdb_history
+
+# ignore core files, but not java/net/protocol/core/
+core
+!core/
+
+lost+found
diff --git a/gcc-4.9/INSTALL/binaries.html b/gcc-4.9/INSTALL/binaries.html
deleted file mode 100644
index b02bdf8..0000000
--- a/gcc-4.9/INSTALL/binaries.html
+++ /dev/null
@@ -1,168 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<!-- Copyright (C) 1988-2014 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.3 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. -->
-<!-- Created by GNU Texinfo 5.1, http://www.gnu.org/software/texinfo/ -->
-<head>
-<title>Installing GCC</title>
-
-<meta name="description" content="Installing GCC">
-<meta name="keywords" content="Installing GCC">
-<meta name="resource-type" content="document">
-<meta name="distribution" content="global">
-<meta name="Generator" content="makeinfo">
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<style type="text/css">
-<!--
-a.summary-letter {text-decoration: none}
-blockquote.smallquotation {font-size: smaller}
-div.display {margin-left: 3.2em}
-div.example {margin-left: 3.2em}
-div.indentedblock {margin-left: 3.2em}
-div.lisp {margin-left: 3.2em}
-div.smalldisplay {margin-left: 3.2em}
-div.smallexample {margin-left: 3.2em}
-div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
-div.smalllisp {margin-left: 3.2em}
-kbd {font-style:oblique}
-pre.display {font-family: inherit}
-pre.format {font-family: inherit}
-pre.menu-comment {font-family: serif}
-pre.menu-preformatted {font-family: serif}
-pre.smalldisplay {font-family: inherit; font-size: smaller}
-pre.smallexample {font-size: smaller}
-pre.smallformat {font-family: inherit; font-size: smaller}
-pre.smalllisp {font-size: smaller}
-span.nocodebreak {white-space:nowrap}
-span.nolinebreak {white-space:nowrap}
-span.roman {font-family:serif; font-weight:normal}
-span.sansserif {font-family:sans-serif; font-weight:normal}
-ul.no-bullet {list-style: none}
--->
-</style>
-
-
-</head>
-
-<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
-<h1 class="settitle" align="center">Installing GCC</h1>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<a name="index-Binaries"></a>
-<a name="index-Installing-GCC_003a-Binaries"></a>
-
-<p>We are often asked about pre-compiled versions of GCC. While we cannot
-provide these for all platforms, below you&rsquo;ll find links to binaries for
-various platforms where creating them by yourself is not easy due to various
-reasons.
-</p>
-<p>Please note that we did not create these binaries, nor do we
-support them. If you have any problems installing them, please
-contact their makers.
-</p>
-<ul>
-<li> AIX:
-<ul>
-<li> <a href="http://www.bullfreeware.com">Bull&rsquo;s Freeware and Shareware Archive for AIX</a>;
-
-</li><li> <a href="http://pware.hvcc.edu">Hudson Valley Community College Open Source Software for IBM System p</a>;
-
-</li><li> <a href="http://www.perzl.org/aix/">AIX 5L and 6 Open Source Packages</a>.
-</li></ul>
-
-</li><li> DOS&mdash;<a href="http://www.delorie.com/djgpp/">DJGPP</a>.
-
-</li><li> Renesas H8/300[HS]&mdash;<a href="http://h8300-hms.sourceforge.net/">GNU
-Development Tools for the Renesas H8/300[HS] Series</a>.
-
-</li><li> HP-UX:
-<ul>
-<li> <a href="http://hpux.connect.org.uk/">HP-UX Porting Center</a>;
-
-</li><li> <a href="ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/">Binaries for HP-UX 11.00 at Aachen University of Technology</a>.
-</li></ul>
-
-</li><li> <a href="http://www.sco.com/skunkware/devtools/index.html#gcc">SCO
-OpenServer/Unixware</a>.
-
-</li><li> Solaris 2 (SPARC, Intel):
-<ul>
-<li> <a href="http://www.sunfreeware.com/">Sunfreeware</a>
-
-</li><li> <a href="http://www.blastwave.org/">Blastwave</a>
-
-</li><li> <a href="http://www.opencsw.org/">OpenCSW</a>
-
-</li><li> <a href="http://jupiterrise.com/tgcware/">TGCware</a>
-</li></ul>
-
-</li><li> Microsoft Windows:
-<ul>
-<li> The <a href="http://sourceware.org/cygwin/">Cygwin</a> project;
-</li><li> The <a href="http://www.mingw.org/">MinGW</a> project.
-</li></ul>
-
-</li><li> <a href="ftp://ftp.thewrittenword.com/packages/by-name/">The
-Written Word</a> offers binaries for
-AIX 4.3.3, 5.1 and 5.2,
-GNU/Linux (i386),
-HP-UX 10.20, 11.00, and 11.11, and
-Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10.
-
-</li><li> <a href="http://www.openpkg.org/">OpenPKG</a> offers binaries for quite a
-number of platforms.
-
-</li><li> The <a href="http://gcc.gnu.org/wiki/GFortranBinaries">GFortran Wiki</a> has
-links to GNU Fortran binaries for several platforms.
-</li></ul>
-
-<hr />
-<p><p><a href="./index.html">Return to the GCC Installation page</a>
-</p>
-
-
-
-
-
-
-
-</body>
-</html>
diff --git a/gcc-4.9/INSTALL/build.html b/gcc-4.9/INSTALL/build.html
deleted file mode 100644
index a4fdbda..0000000
--- a/gcc-4.9/INSTALL/build.html
+++ /dev/null
@@ -1,458 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<!-- Copyright (C) 1988-2014 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.3 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. -->
-<!-- Created by GNU Texinfo 5.1, http://www.gnu.org/software/texinfo/ -->
-<head>
-<title>Installing GCC</title>
-
-<meta name="description" content="Installing GCC">
-<meta name="keywords" content="Installing GCC">
-<meta name="resource-type" content="document">
-<meta name="distribution" content="global">
-<meta name="Generator" content="makeinfo">
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<style type="text/css">
-<!--
-a.summary-letter {text-decoration: none}
-blockquote.smallquotation {font-size: smaller}
-div.display {margin-left: 3.2em}
-div.example {margin-left: 3.2em}
-div.indentedblock {margin-left: 3.2em}
-div.lisp {margin-left: 3.2em}
-div.smalldisplay {margin-left: 3.2em}
-div.smallexample {margin-left: 3.2em}
-div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
-div.smalllisp {margin-left: 3.2em}
-kbd {font-style:oblique}
-pre.display {font-family: inherit}
-pre.format {font-family: inherit}
-pre.menu-comment {font-family: serif}
-pre.menu-preformatted {font-family: serif}
-pre.smalldisplay {font-family: inherit; font-size: smaller}
-pre.smallexample {font-size: smaller}
-pre.smallformat {font-family: inherit; font-size: smaller}
-pre.smalllisp {font-size: smaller}
-span.nocodebreak {white-space:nowrap}
-span.nolinebreak {white-space:nowrap}
-span.roman {font-family:serif; font-weight:normal}
-span.sansserif {font-family:sans-serif; font-weight:normal}
-ul.no-bullet {list-style: none}
--->
-</style>
-
-
-</head>
-
-<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
-<h1 class="settitle" align="center">Installing GCC</h1>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<a name="index-Installing-GCC_003a-Building"></a>
-
-<p>Now that GCC is configured, you are ready to build the compiler and
-runtime libraries.
-</p>
-<p>Some commands executed when making the compiler may fail (return a
-nonzero status) and be ignored by <code>make</code>. These failures, which
-are often due to files that were not found, are expected, and can safely
-be ignored.
-</p>
-<p>It is normal to have compiler warnings when compiling certain files.
-Unless you are a GCC developer, you can generally ignore these warnings
-unless they cause compilation to fail. Developers should attempt to fix
-any warnings encountered, however they can temporarily continue past
-warnings-as-errors by specifying the configure flag
-<samp>--disable-werror</samp>.
-</p>
-<p>On certain old systems, defining certain environment variables such as
-<code>CC</code> can interfere with the functioning of <code>make</code>.
-</p>
-<p>If you encounter seemingly strange errors when trying to build the
-compiler in a directory other than the source directory, it could be
-because you have previously configured the compiler in the source
-directory. Make sure you have done all the necessary preparations.
-</p>
-<p>If you build GCC on a BSD system using a directory stored in an old System
-V file system, problems may occur in running <code>fixincludes</code> if the
-System V file system doesn&rsquo;t support symbolic links. These problems
-result in a failure to fix the declaration of <code>size_t</code> in
-<samp>sys/types.h</samp>. If you find that <code>size_t</code> is a signed type and
-that type mismatches occur, this could be the cause.
-</p>
-<p>The solution is not to use such a directory for building GCC.
-</p>
-<p>Similarly, when building from SVN or snapshots, or if you modify
-<samp>*.l</samp> files, you need the Flex lexical analyzer generator
-installed. If you do not modify <samp>*.l</samp> files, releases contain
-the Flex-generated files and you do not need Flex installed to build
-them. There is still one Flex-based lexical analyzer (part of the
-build machinery, not of GCC itself) that is used even if you only
-build the C front end.
-</p>
-<p>When building from SVN or snapshots, or if you modify Texinfo
-documentation, you need version 4.7 or later of Texinfo installed if you
-want Info documentation to be regenerated. Releases contain Info
-documentation pre-built for the unmodified documentation in the release.
-</p>
-<a name="Building-a-native-compiler"></a>
-<h3 class="section">Building a native compiler</h3>
-
-<p>For a native build, the default configuration is to perform
-a 3-stage bootstrap of the compiler when &lsquo;<samp>make</samp>&rsquo; is invoked.
-This will build the entire GCC system and ensure that it compiles
-itself correctly. It can be disabled with the <samp>--disable-bootstrap</samp>
-parameter to &lsquo;<samp>configure</samp>&rsquo;, but bootstrapping is suggested because
-the compiler will be tested more completely and could also have
-better performance.
-</p>
-<p>The bootstrapping process will complete the following steps:
-</p>
-<ul>
-<li> Build tools necessary to build the compiler.
-
-</li><li> Perform a 3-stage bootstrap of the compiler. This includes building
-three times the target tools for use by the compiler such as binutils
-(bfd, binutils, gas, gprof, ld, and opcodes) if they have been
-individually linked or moved into the top level GCC source tree before
-configuring.
-
-</li><li> Perform a comparison test of the stage2 and stage3 compilers.
-
-</li><li> Build runtime libraries using the stage3 compiler from the previous step.
-
-</li></ul>
-
-<p>If you are short on disk space you might consider &lsquo;<samp>make
-bootstrap-lean</samp>&rsquo; instead. The sequence of compilation is the
-same described above, but object files from the stage1 and
-stage2 of the 3-stage bootstrap of the compiler are deleted as
-soon as they are no longer needed.
-</p>
-<p>If you wish to use non-default GCC flags when compiling the stage2
-and stage3 compilers, set <code>BOOT_CFLAGS</code> on the command line when
-doing &lsquo;<samp>make</samp>&rsquo;. For example, if you want to save additional space
-during the bootstrap and in the final installation as well, you can
-build the compiler binaries without debugging information as in the
-following example. This will save roughly 40% of disk space both for
-the bootstrap and the final installation. (Libraries will still contain
-debugging information.)
-</p>
-<div class="smallexample">
-<pre class="smallexample">make BOOT_CFLAGS='-O' bootstrap
-</pre></div>
-
-<p>You can place non-default optimization flags into <code>BOOT_CFLAGS</code>; they
-are less well tested here than the default of &lsquo;<samp>-g -O2</samp>&rsquo;, but should
-still work. In a few cases, you may find that you need to specify special
-flags such as <samp>-msoft-float</samp> here to complete the bootstrap; or,
-if the native compiler miscompiles the stage1 compiler, you may need
-to work around this, by choosing <code>BOOT_CFLAGS</code> to avoid the parts
-of the stage1 compiler that were miscompiled, or by using &lsquo;<samp>make
-bootstrap4</samp>&rsquo; to increase the number of stages of bootstrap.
-</p>
-<p><code>BOOT_CFLAGS</code> does not apply to bootstrapped target libraries.
-Since these are always compiled with the compiler currently being
-bootstrapped, you can use <code>CFLAGS_FOR_TARGET</code> to modify their
-compilation flags, as for non-bootstrapped target libraries.
-Again, if the native compiler miscompiles the stage1 compiler, you may
-need to work around this by avoiding non-working parts of the stage1
-compiler. Use <code>STAGE1_TFLAGS</code> to this end.
-</p>
-<p>If you used the flag <samp>--enable-languages=&hellip;</samp> to restrict
-the compilers to be built, only those you&rsquo;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 <code>LANGUAGES</code> when calling &lsquo;<samp>make</samp>&rsquo;
-<strong>does not</strong> work anymore!
-</p>
-<p>If the comparison of stage2 and stage3 fails, this normally indicates
-that the stage2 compiler has compiled GCC incorrectly, and is therefore
-a potentially serious bug which you should investigate and report. (On
-a few systems, meaningful comparison of object files is impossible; they
-always appear &ldquo;different&rdquo;. If you encounter this problem, you will
-need to disable comparison in the <samp>Makefile</samp>.)
-</p>
-<p>If you do not want to bootstrap your compiler, you can configure with
-<samp>--disable-bootstrap</samp>. In particular cases, you may want to
-bootstrap your compiler even if the target system is not the same as
-the one you are building on: for example, you could build a
-<code>powerpc-unknown-linux-gnu</code> toolchain on a
-<code>powerpc64-unknown-linux-gnu</code> host. In this case, pass
-<samp>--enable-bootstrap</samp> to the configure script.
-</p>
-<p><code>BUILD_CONFIG</code> can be used to bring in additional customization
-to the build. It can be set to a whitespace-separated list of names.
-For each such <code>NAME</code>, top-level <samp>config/<code>NAME</code>.mk</samp> will
-be included by the top-level <samp>Makefile</samp>, bringing in any settings
-it contains. The default <code>BUILD_CONFIG</code> can be set using the
-configure option <samp>--with-build-config=<code>NAME</code>...</samp>. Some
-examples of supported build configurations are:
-</p>
-<dl compact="compact">
-<dt>&lsquo;<samp>bootstrap-O1</samp>&rsquo;</dt>
-<dd><p>Removes any <samp>-O</samp>-started option from <code>BOOT_CFLAGS</code>, and adds
-<samp>-O1</samp> to it. &lsquo;<samp>BUILD_CONFIG=bootstrap-O1</samp>&rsquo; is equivalent to
-&lsquo;<samp>BOOT_CFLAGS='-g -O1'</samp>&rsquo;.
-</p>
-</dd>
-<dt>&lsquo;<samp>bootstrap-O3</samp>&rsquo;</dt>
-<dd><p>Analogous to <code>bootstrap-O1</code>.
-</p>
-</dd>
-<dt>&lsquo;<samp>bootstrap-lto</samp>&rsquo;</dt>
-<dd><p>Enables Link-Time Optimization for host tools during bootstrapping.
-&lsquo;<samp>BUILD_CONFIG=bootstrap-lto</samp>&rsquo; is equivalent to adding
-<samp>-flto</samp> to &lsquo;<samp>BOOT_CFLAGS</samp>&rsquo;.
-</p>
-</dd>
-<dt>&lsquo;<samp>bootstrap-debug</samp>&rsquo;</dt>
-<dd><p>Verifies that the compiler generates the same executable code, whether
-or not it is asked to emit debug information. To this end, this
-option builds stage2 host programs without debug information, and uses
-<samp>contrib/compare-debug</samp> to compare them with the stripped stage3
-object files. If <code>BOOT_CFLAGS</code> is overridden so as to not enable
-debug information, stage2 will have it, and stage3 won&rsquo;t. This option
-is enabled by default when GCC bootstrapping is enabled, if
-<code>strip</code> can turn object files compiled with and without debug
-info into identical object files. In addition to better test
-coverage, this option makes default bootstraps faster and leaner.
-</p>
-</dd>
-<dt>&lsquo;<samp>bootstrap-debug-big</samp>&rsquo;</dt>
-<dd><p>Rather than comparing stripped object files, as in
-<code>bootstrap-debug</code>, this option saves internal compiler dumps
-during stage2 and stage3 and compares them as well, which helps catch
-additional potential problems, but at a great cost in terms of disk
-space. It can be specified in addition to &lsquo;<samp>bootstrap-debug</samp>&rsquo;.
-</p>
-</dd>
-<dt>&lsquo;<samp>bootstrap-debug-lean</samp>&rsquo;</dt>
-<dd><p>This option saves disk space compared with <code>bootstrap-debug-big</code>,
-but at the expense of some recompilation. Instead of saving the dumps
-of stage2 and stage3 until the final compare, it uses
-<samp>-fcompare-debug</samp> to generate, compare and remove the dumps
-during stage3, repeating the compilation that already took place in
-stage2, whose dumps were not saved.
-</p>
-</dd>
-<dt>&lsquo;<samp>bootstrap-debug-lib</samp>&rsquo;</dt>
-<dd><p>This option tests executable code invariance over debug information
-generation on target libraries, just like <code>bootstrap-debug-lean</code>
-tests it on host programs. It builds stage3 libraries with
-<samp>-fcompare-debug</samp>, and it can be used along with any of the
-<code>bootstrap-debug</code> options above.
-</p>
-<p>There aren&rsquo;t <code>-lean</code> or <code>-big</code> counterparts to this option
-because most libraries are only build in stage3, so bootstrap compares
-would not get significant coverage. Moreover, the few libraries built
-in stage2 are used in stage3 host programs, so we wouldn&rsquo;t want to
-compile stage2 libraries with different options for comparison purposes.
-</p>
-</dd>
-<dt>&lsquo;<samp>bootstrap-debug-ckovw</samp>&rsquo;</dt>
-<dd><p>Arranges for error messages to be issued if the compiler built on any
-stage is run without the option <samp>-fcompare-debug</samp>. This is
-useful to verify the full <samp>-fcompare-debug</samp> testing coverage. It
-must be used along with <code>bootstrap-debug-lean</code> and
-<code>bootstrap-debug-lib</code>.
-</p>
-</dd>
-<dt>&lsquo;<samp>bootstrap-time</samp>&rsquo;</dt>
-<dd><p>Arranges for the run time of each program started by the GCC driver,
-built in any stage, to be logged to <samp>time.log</samp>, in the top level of
-the build tree.
-</p>
-</dd>
-</dl>
-
-<a name="Building-a-cross-compiler"></a>
-<h3 class="section">Building a cross compiler</h3>
-
-<p>When building a cross compiler, it is not generally possible to do a
-3-stage bootstrap of the compiler. This makes for an interesting problem
-as parts of GCC can only be built with GCC.
-</p>
-<p>To build a cross compiler, we recommend first building and installing a
-native compiler. You can then use the native GCC compiler to build the
-cross compiler. The installed native compiler needs to be GCC version
-2.95 or later.
-</p>
-<p>If the cross compiler is to be built with support for the Java
-programming language and the ability to compile .java source files is
-desired, the installed native compiler used to build the cross
-compiler needs to be the same GCC version as the cross compiler. In
-addition the cross compiler needs to be configured with
-<samp>--with-ecj-jar=&hellip;</samp>.
-</p>
-<p>Assuming you have already installed a native copy of GCC and configured
-your cross compiler, issue the command <code>make</code>, which performs the
-following steps:
-</p>
-<ul>
-<li> Build host tools necessary to build the compiler.
-
-</li><li> Build target tools for use by the compiler such as binutils (bfd,
-binutils, gas, gprof, ld, and opcodes)
-if they have been individually linked or moved into the top level GCC source
-tree before configuring.
-
-</li><li> Build the compiler (single stage only).
-
-</li><li> Build runtime libraries using the compiler from the previous step.
-</li></ul>
-
-<p>Note that if an error occurs in any step the make process will exit.
-</p>
-<p>If you are not building GNU binutils in the same source tree as GCC,
-you will need a cross-assembler and cross-linker installed before
-configuring GCC. Put them in the directory
-<samp><var>prefix</var>/<var>target</var>/bin</samp>. Here is a table of the tools
-you should put in this directory:
-</p>
-<dl compact="compact">
-<dt><samp>as</samp></dt>
-<dd><p>This should be the cross-assembler.
-</p>
-</dd>
-<dt><samp>ld</samp></dt>
-<dd><p>This should be the cross-linker.
-</p>
-</dd>
-<dt><samp>ar</samp></dt>
-<dd><p>This should be the cross-archiver: a program which can manipulate
-archive files (linker libraries) in the target machine&rsquo;s format.
-</p>
-</dd>
-<dt><samp>ranlib</samp></dt>
-<dd><p>This should be a program to construct a symbol table in an archive file.
-</p></dd>
-</dl>
-
-<p>The installation of GCC will find these programs in that directory,
-and copy or link them to the proper place to for the cross-compiler to
-find them when run later.
-</p>
-<p>The easiest way to provide these files is to build the Binutils package.
-Configure it with the same <samp>--host</samp> and <samp>--target</samp>
-options that you use for configuring GCC, then build and install
-them. They install their executables automatically into the proper
-directory. Alas, they do not support all the targets that GCC
-supports.
-</p>
-<p>If you are not building a C library in the same source tree as GCC,
-you should also provide the target libraries and headers before
-configuring GCC, specifying the directories with
-<samp>--with-sysroot</samp> or <samp>--with-headers</samp> and
-<samp>--with-libs</samp>. Many targets also require &ldquo;start files&rdquo; such
-as <samp>crt0.o</samp> and
-<samp>crtn.o</samp> which are linked into each executable. There may be several
-alternatives for <samp>crt0.o</samp>, for use with profiling or other
-compilation options. Check your target&rsquo;s definition of
-<code>STARTFILE_SPEC</code> to find out what start files it uses.
-</p>
-<a name="Building-in-parallel"></a>
-<h3 class="section">Building in parallel</h3>
-
-<p>GNU Make 3.80 and above, which is necessary to build GCC, support
-building in parallel. To activate this, you can use &lsquo;<samp>make -j 2</samp>&rsquo;
-instead of &lsquo;<samp>make</samp>&rsquo;. You can also specify a bigger number, and
-in most cases using a value greater than the number of processors in
-your machine will result in fewer and shorter I/O latency hits, thus
-improving overall throughput; this is especially true for slow drives
-and network filesystems.
-</p>
-<a name="Building-the-Ada-compiler"></a>
-<h3 class="section">Building the Ada compiler</h3>
-
-<p>In order to build GNAT, the Ada compiler, you need a working GNAT
-compiler (GCC version 4.0 or later).
-This includes GNAT tools such as <code>gnatmake</code> and
-<code>gnatlink</code>, since the Ada front end is written in Ada and
-uses some GNAT-specific extensions.
-</p>
-<p>In order to build a cross compiler, it is suggested to install
-the new compiler as native first, and then use it to build the cross
-compiler.
-</p>
-<p><code>configure</code> does not test whether the GNAT installation works
-and has a sufficiently recent version; if too old a GNAT version is
-installed, the build will fail unless <samp>--enable-languages</samp> is
-used to disable building the Ada front end.
-</p>
-<p><code>ADA_INCLUDE_PATH</code> and <code>ADA_OBJECT_PATH</code> environment variables
-must not be set when building the Ada compiler, the Ada tools, or the
-Ada runtime libraries. You can check that your build environment is clean
-by verifying that &lsquo;<samp>gnatls -v</samp>&rsquo; lists only one explicit path in each
-section.
-</p>
-<a name="Building-with-profile-feedback"></a>
-<h3 class="section">Building with profile feedback</h3>
-
-<p>It is possible to use profile feedback to optimize the compiler itself. This
-should result in a faster compiler binary. Experiments done on x86 using gcc
-3.3 showed approximately 7 percent speedup on compiling C programs. To
-bootstrap the compiler with profile feedback, use <code>make profiledbootstrap</code>.
-</p>
-<p>When &lsquo;<samp>make profiledbootstrap</samp>&rsquo; is run, it will first build a <code>stage1</code>
-compiler. This compiler is used to build a <code>stageprofile</code> compiler
-instrumented to collect execution counts of instruction and branch
-probabilities. Then runtime libraries are compiled with profile collected.
-Finally a <code>stagefeedback</code> compiler is built using the information collected.
-</p>
-<p>Unlike standard bootstrap, several additional restrictions apply. The
-compiler used to build <code>stage1</code> needs to support a 64-bit integral type.
-It is recommended to only use GCC for this. Also parallel make is currently
-not supported since collisions in profile collecting may occur.
-</p>
-<hr />
-<p><p><a href="./index.html">Return to the GCC Installation page</a>
-</p>
-
-
-
-
-
-
-
-<hr>
-
-
-
-</body>
-</html>
diff --git a/gcc-4.9/INSTALL/configure.html b/gcc-4.9/INSTALL/configure.html
deleted file mode 100644
index 83db7e8..0000000
--- a/gcc-4.9/INSTALL/configure.html
+++ /dev/null
@@ -1,1837 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<!-- Copyright (C) 1988-2014 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.3 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. -->
-<!-- Created by GNU Texinfo 5.1, http://www.gnu.org/software/texinfo/ -->
-<head>
-<title>Installing GCC</title>
-
-<meta name="description" content="Installing GCC">
-<meta name="keywords" content="Installing GCC">
-<meta name="resource-type" content="document">
-<meta name="distribution" content="global">
-<meta name="Generator" content="makeinfo">
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<style type="text/css">
-<!--
-a.summary-letter {text-decoration: none}
-blockquote.smallquotation {font-size: smaller}
-div.display {margin-left: 3.2em}
-div.example {margin-left: 3.2em}
-div.indentedblock {margin-left: 3.2em}
-div.lisp {margin-left: 3.2em}
-div.smalldisplay {margin-left: 3.2em}
-div.smallexample {margin-left: 3.2em}
-div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
-div.smalllisp {margin-left: 3.2em}
-kbd {font-style:oblique}
-pre.display {font-family: inherit}
-pre.format {font-family: inherit}
-pre.menu-comment {font-family: serif}
-pre.menu-preformatted {font-family: serif}
-pre.smalldisplay {font-family: inherit; font-size: smaller}
-pre.smallexample {font-size: smaller}
-pre.smallformat {font-family: inherit; font-size: smaller}
-pre.smalllisp {font-size: smaller}
-span.nocodebreak {white-space:nowrap}
-span.nolinebreak {white-space:nowrap}
-span.roman {font-family:serif; font-weight:normal}
-span.sansserif {font-family:sans-serif; font-weight:normal}
-ul.no-bullet {list-style: none}
--->
-</style>
-
-
-</head>
-
-<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
-<h1 class="settitle" align="center">Installing GCC</h1>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<a name="index-Configuration"></a>
-<a name="index-Installing-GCC_003a-Configuration"></a>
-
-<p>Like most GNU software, GCC must be configured before it can be built.
-This document describes the recommended configuration procedure
-for both native and cross targets.
-</p>
-<p>We use <var>srcdir</var> to refer to the toplevel source directory for
-GCC; we use <var>objdir</var> to refer to the toplevel build/object directory.
-</p>
-<p>If you obtained the sources via SVN, <var>srcdir</var> must refer to the top
-<samp>gcc</samp> directory, the one where the <samp>MAINTAINERS</samp> file can be
-found, and not its <samp>gcc</samp> subdirectory, otherwise the build will fail.
-</p>
-<p>If either <var>srcdir</var> or <var>objdir</var> is located on an automounted NFS
-file system, the shell&rsquo;s built-in <code>pwd</code> command will return
-temporary pathnames. Using these can lead to various sorts of build
-problems. To avoid this issue, set the <code>PWDCMD</code> environment
-variable to an automounter-aware <code>pwd</code> command, e.g.,
-<code>pawd</code> or &lsquo;<samp>amq -w</samp>&rsquo;, during the configuration and build
-phases.
-</p>
-<p>First, we <strong>highly</strong> recommend that GCC be built into a
-separate directory from the sources which does <strong>not</strong> reside
-within the source tree. This is how we generally build GCC; building
-where <var>srcdir</var> == <var>objdir</var> should still work, but doesn&rsquo;t
-get extensive testing; building where <var>objdir</var> is a subdirectory
-of <var>srcdir</var> is unsupported.
-</p>
-<p>If you have previously built GCC in the same directory for a
-different target machine, do &lsquo;<samp>make distclean</samp>&rsquo; to delete all files
-that might be invalid. One of the files this deletes is <samp>Makefile</samp>;
-if &lsquo;<samp>make distclean</samp>&rsquo; complains that <samp>Makefile</samp> does not exist
-or issues a message like &ldquo;don&rsquo;t know how to make distclean&rdquo; it probably
-means that the directory is already suitably clean. However, with the
-recommended method of building in a separate <var>objdir</var>, you should
-simply use a different <var>objdir</var> for each target.
-</p>
-<p>Second, when configuring a native system, either <code>cc</code> or
-<code>gcc</code> must be in your path or you must set <code>CC</code> in
-your environment before running configure. Otherwise the configuration
-scripts may fail.
-</p>
-
-<p>To configure GCC:
-</p>
-<div class="smallexample">
-<pre class="smallexample">% mkdir <var>objdir</var>
-% cd <var>objdir</var>
-% <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
-</pre></div>
-
-<a name="Distributor-options"></a>
-<h3 class="heading">Distributor options</h3>
-
-<p>If you will be distributing binary versions of GCC, with modifications
-to the source code, you should use the options described in this
-section to make clear that your version contains modifications.
-</p>
-<dl compact="compact">
-<dt><code>--with-pkgversion=<var>version</var></code></dt>
-<dd><p>Specify a string that identifies your package. You may wish
-to include a build number or build date. This version string will be
-included in the output of <code>gcc --version</code>. This suffix does
-not replace the default version string, only the &lsquo;<samp>GCC</samp>&rsquo; part.
-</p>
-<p>The default value is &lsquo;<samp>GCC</samp>&rsquo;.
-</p>
-</dd>
-<dt><code>--with-bugurl=<var>url</var></code></dt>
-<dd><p>Specify the URL that users should visit if they wish to report a bug.
-You are of course welcome to forward bugs reported to you to the FSF,
-if you determine that they are not bugs in your modifications.
-</p>
-<p>The default value refers to the FSF&rsquo;s GCC bug tracker.
-</p>
-</dd>
-</dl>
-
-<a name="Target-specification"></a>
-<h3 class="heading">Target specification</h3>
-<ul>
-<li> GCC has code to correctly determine the correct value for <var>target</var>
-for nearly all native systems. Therefore, we highly recommend you do
-not provide a configure target when configuring a native compiler.
-
-</li><li> <var>target</var> must be specified as <samp>--target=<var>target</var></samp>
-when configuring a cross compiler; examples of valid targets would be
-m68k-elf, sh-elf, etc.
-
-</li><li> Specifying just <var>target</var> instead of <samp>--target=<var>target</var></samp>
-implies that the host defaults to <var>target</var>.
-</li></ul>
-
-
-<a name="Options-specification"></a>
-<h3 class="heading">Options specification</h3>
-
-<p>Use <var>options</var> to override several configure time options for
-GCC. A list of supported <var>options</var> follows; &lsquo;<samp>configure
---help</samp>&rsquo; may list other options, but those not listed below may not
-work and should not normally be used.
-</p>
-<p>Note that each <samp>--enable</samp> option has a corresponding
-<samp>--disable</samp> option and that each <samp>--with</samp> option has a
-corresponding <samp>--without</samp> option.
-</p>
-<dl compact="compact">
-<dt><code>--prefix=<var>dirname</var></code></dt>
-<dd><p>Specify the toplevel installation
-directory. This is the recommended way to install the tools into a directory
-other than the default. The toplevel installation directory defaults to
-<samp>/usr/local</samp>.
-</p>
-<p>We <strong>highly</strong> recommend against <var>dirname</var> being the same or a
-subdirectory of <var>objdir</var> or vice versa. If specifying a directory
-beneath a user&rsquo;s home directory tree, some shells will not expand
-<var>dirname</var> correctly if it contains the &lsquo;<samp>~</samp>&rsquo; metacharacter; use
-<code>$HOME</code> instead.
-</p>
-<p>The following standard <code>autoconf</code> options are supported. Normally you
-should not need to use these options.
-</p><dl compact="compact">
-<dt><code>--exec-prefix=<var>dirname</var></code></dt>
-<dd><p>Specify the toplevel installation directory for architecture-dependent
-files. The default is <samp><var>prefix</var></samp>.
-</p>
-</dd>
-<dt><code>--bindir=<var>dirname</var></code></dt>
-<dd><p>Specify the installation directory for the executables called by users
-(such as <code>gcc</code> and <code>g++</code>). The default is
-<samp><var>exec-prefix</var>/bin</samp>.
-</p>
-</dd>
-<dt><code>--libdir=<var>dirname</var></code></dt>
-<dd><p>Specify the installation directory for object code libraries and
-internal data files of GCC. The default is <samp><var>exec-prefix</var>/lib</samp>.
-</p>
-</dd>
-<dt><code>--libexecdir=<var>dirname</var></code></dt>
-<dd><p>Specify the installation directory for internal executables of GCC.
-The default is <samp><var>exec-prefix</var>/libexec</samp>.
-</p>
-</dd>
-<dt><code>--with-slibdir=<var>dirname</var></code></dt>
-<dd><p>Specify the installation directory for the shared libgcc library. The
-default is <samp><var>libdir</var></samp>.
-</p>
-</dd>
-<dt><code>--datarootdir=<var>dirname</var></code></dt>
-<dd><p>Specify the root of the directory tree for read-only architecture-independent
-data files referenced by GCC. The default is <samp><var>prefix</var>/share</samp>.
-</p>
-</dd>
-<dt><code>--infodir=<var>dirname</var></code></dt>
-<dd><p>Specify the installation directory for documentation in info format.
-The default is <samp><var>datarootdir</var>/info</samp>.
-</p>
-</dd>
-<dt><code>--datadir=<var>dirname</var></code></dt>
-<dd><p>Specify the installation directory for some architecture-independent
-data files referenced by GCC. The default is <samp><var>datarootdir</var></samp>.
-</p>
-</dd>
-<dt><code>--docdir=<var>dirname</var></code></dt>
-<dd><p>Specify the installation directory for documentation files (other
-than Info) for GCC. The default is <samp><var>datarootdir</var>/doc</samp>.
-</p>
-</dd>
-<dt><code>--htmldir=<var>dirname</var></code></dt>
-<dd><p>Specify the installation directory for HTML documentation files.
-The default is <samp><var>docdir</var></samp>.
-</p>
-</dd>
-<dt><code>--pdfdir=<var>dirname</var></code></dt>
-<dd><p>Specify the installation directory for PDF documentation files.
-The default is <samp><var>docdir</var></samp>.
-</p>
-</dd>
-<dt><code>--mandir=<var>dirname</var></code></dt>
-<dd><p>Specify the installation directory for manual pages. The default is
-<samp><var>datarootdir</var>/man</samp>. (Note that the manual pages are only extracts
-from the full GCC manuals, which are provided in Texinfo format. The manpages
-are derived by an automatic conversion process from parts of the full
-manual.)
-</p>
-</dd>
-<dt><code>--with-gxx-include-dir=<var>dirname</var></code></dt>
-<dd><p>Specify
-the installation directory for G++ header files. The default depends
-on other configuration options, and differs between cross and native
-configurations.
-</p>
-</dd>
-<dt><code>--with-specs=<var>specs</var></code></dt>
-<dd><p>Specify additional command line driver SPECS.
-This can be useful if you need to turn on a non-standard feature by
-default without modifying the compiler&rsquo;s source code, for instance
-<samp>--with-specs=%{!fcommon:%{!fno-common:-fno-common}}</samp>.
-See &ldquo;Spec Files&rdquo; in the main manual
-</p>
-</dd>
-</dl>
-
-</dd>
-<dt><code>--program-prefix=<var>prefix</var></code></dt>
-<dd><p>GCC supports some transformations of the names of its programs when
-installing them. This option prepends <var>prefix</var> to the names of
-programs to install in <var>bindir</var> (see above). For example, specifying
-<samp>--program-prefix=foo-</samp> would result in &lsquo;<samp>gcc</samp>&rsquo;
-being installed as <samp>/usr/local/bin/foo-gcc</samp>.
-</p>
-</dd>
-<dt><code>--program-suffix=<var>suffix</var></code></dt>
-<dd><p>Appends <var>suffix</var> to the names of programs to install in <var>bindir</var>
-(see above). For example, specifying <samp>--program-suffix=-3.1</samp>
-would result in &lsquo;<samp>gcc</samp>&rsquo; being installed as
-<samp>/usr/local/bin/gcc-3.1</samp>.
-</p>
-</dd>
-<dt><code>--program-transform-name=<var>pattern</var></code></dt>
-<dd><p>Applies the &lsquo;<samp>sed</samp>&rsquo; script <var>pattern</var> to be applied to the names
-of programs to install in <var>bindir</var> (see above). <var>pattern</var> has to
-consist of one or more basic &lsquo;<samp>sed</samp>&rsquo; editing commands, separated by
-semicolons. For example, if you want the &lsquo;<samp>gcc</samp>&rsquo; program name to be
-transformed to the installed program <samp>/usr/local/bin/myowngcc</samp> and
-the &lsquo;<samp>g++</samp>&rsquo; program name to be transformed to
-<samp>/usr/local/bin/gspecial++</samp> without changing other program names,
-you could use the pattern
-<samp>--program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/'</samp>
-to achieve this effect.
-</p>
-<p>All three options can be combined and used together, resulting in more
-complex conversion patterns. As a basic rule, <var>prefix</var> (and
-<var>suffix</var>) are prepended (appended) before further transformations
-can happen with a special transformation script <var>pattern</var>.
-</p>
-<p>As currently implemented, this option only takes effect for native
-builds; cross compiler binaries&rsquo; names are not transformed even when a
-transformation is explicitly asked for by one of these options.
-</p>
-<p>For native builds, some of the installed programs are also installed
-with the target alias in front of their name, as in
-&lsquo;<samp>i686-pc-linux-gnu-gcc</samp>&rsquo;. All of the above transformations happen
-before the target alias is prepended to the name&mdash;so, specifying
-<samp>--program-prefix=foo-</samp> and <samp>program-suffix=-3.1</samp>, the
-resulting binary would be installed as
-<samp>/usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1</samp>.
-</p>
-<p>As a last shortcoming, none of the installed Ada programs are
-transformed yet, which will be fixed in some time.
-</p>
-</dd>
-<dt><code>--with-local-prefix=<var>dirname</var></code></dt>
-<dd><p>Specify the
-installation directory for local include files. The default is
-<samp>/usr/local</samp>. Specify this option if you want the compiler to
-search directory <samp><var>dirname</var>/include</samp> for locally installed
-header files <em>instead</em> of <samp>/usr/local/include</samp>.
-</p>
-<p>You should specify <samp>--with-local-prefix</samp> <strong>only</strong> if your
-site has a different convention (not <samp>/usr/local</samp>) for where to put
-site-specific files.
-</p>
-<p>The default value for <samp>--with-local-prefix</samp> is <samp>/usr/local</samp>
-regardless of the value of <samp>--prefix</samp>. Specifying
-<samp>--prefix</samp> has no effect on which directory GCC searches for
-local header files. This may seem counterintuitive, but actually it is
-logical.
-</p>
-<p>The purpose of <samp>--prefix</samp> is to specify where to <em>install
-GCC</em>. The local header files in <samp>/usr/local/include</samp>&mdash;if you put
-any in that directory&mdash;are not part of GCC. They are part of other
-programs&mdash;perhaps many others. (GCC installs its own header files in
-another directory which is based on the <samp>--prefix</samp> value.)
-</p>
-<p>Both the local-prefix include directory and the GCC-prefix include
-directory are part of GCC&rsquo;s &ldquo;system include&rdquo; directories. Although these
-two directories are not fixed, they need to be searched in the proper
-order for the correct processing of the include_next directive. The
-local-prefix include directory is searched before the GCC-prefix
-include directory. Another characteristic of system include directories
-is that pedantic warnings are turned off for headers in these directories.
-</p>
-<p>Some autoconf macros add <samp>-I <var>directory</var></samp> options to the
-compiler command line, to ensure that directories containing installed
-packages&rsquo; headers are searched. When <var>directory</var> is one of GCC&rsquo;s
-system include directories, GCC will ignore the option so that system
-directories continue to be processed in the correct order. This
-may result in a search order different from what was specified but the
-directory will still be searched.
-</p>
-<p>GCC automatically searches for ordinary libraries using
-<code>GCC_EXEC_PREFIX</code>. Thus, when the same installation prefix is
-used for both GCC and packages, GCC will automatically search for
-both headers and libraries. This provides a configuration that is
-easy to use. GCC behaves in a manner similar to that when it is
-installed as a system compiler in <samp>/usr</samp>.
-</p>
-<p>Sites that need to install multiple versions of GCC may not want to
-use the above simple configuration. It is possible to use the
-<samp>--program-prefix</samp>, <samp>--program-suffix</samp> and
-<samp>--program-transform-name</samp> options to install multiple versions
-into a single directory, but it may be simpler to use different prefixes
-and the <samp>--with-local-prefix</samp> option to specify the location of the
-site-specific files for each version. It will then be necessary for
-users to specify explicitly the location of local site libraries
-(e.g., with <code>LIBRARY_PATH</code>).
-</p>
-<p>The same value can be used for both <samp>--with-local-prefix</samp> and
-<samp>--prefix</samp> provided it is not <samp>/usr</samp>. This can be used
-to avoid the default search of <samp>/usr/local/include</samp>.
-</p>
-<p><strong>Do not</strong> specify <samp>/usr</samp> as the <samp>--with-local-prefix</samp>!
-The directory you use for <samp>--with-local-prefix</samp> <strong>must not</strong>
-contain any of the system&rsquo;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 <code>fixincludes</code> script.
-</p>
-<p>Indications are that people who use this option use it based on mistaken
-ideas of what it is for. People use it as if it specified where to
-install part of GCC. Perhaps they make this assumption because
-installing GCC creates the directory.
-</p>
-</dd>
-<dt><code>--with-native-system-header-dir=<var>dirname</var></code></dt>
-<dd><p>Specifies that <var>dirname</var> is the directory that contains native system
-header files, rather than <samp>/usr/include</samp>. This option is most useful
-if you are creating a compiler that should be isolated from the system
-as much as possible. It is most commonly used with the
-<samp>--with-sysroot</samp> option and will cause GCC to search
-<var>dirname</var> inside the system root specified by that option.
-</p>
-</dd>
-<dt><code>--enable-shared[=<var>package</var>[,&hellip;]]</code></dt>
-<dd><p>Build shared versions of libraries, if shared libraries are supported on
-the target platform. Unlike GCC 2.95.x and earlier, shared libraries
-are enabled by default on all platforms that support shared libraries.
-</p>
-<p>If a list of packages is given as an argument, build shared libraries
-only for the listed packages. For other packages, only static libraries
-will be built. Package names currently recognized in the GCC tree are
-&lsquo;<samp>libgcc</samp>&rsquo; (also known as &lsquo;<samp>gcc</samp>&rsquo;), &lsquo;<samp>libstdc++</samp>&rsquo; (not
-&lsquo;<samp>libstdc++-v3</samp>&rsquo;), &lsquo;<samp>libffi</samp>&rsquo;, &lsquo;<samp>zlib</samp>&rsquo;, &lsquo;<samp>boehm-gc</samp>&rsquo;,
-&lsquo;<samp>ada</samp>&rsquo;, &lsquo;<samp>libada</samp>&rsquo;, &lsquo;<samp>libjava</samp>&rsquo;, &lsquo;<samp>libgo</samp>&rsquo;, and &lsquo;<samp>libobjc</samp>&rsquo;.
-Note &lsquo;<samp>libiberty</samp>&rsquo; does not support shared libraries at all.
-</p>
-<p>Use <samp>--disable-shared</samp> to build only static libraries. Note that
-<samp>--disable-shared</samp> does not accept a list of package names as
-argument, only <samp>--enable-shared</samp> does.
-</p>
-<p>Contrast with <samp>--enable-host-shared</samp>, which affects <em>host</em>
-code.
-</p>
-</dd>
-<dt><code>--enable-host-shared</code></dt>
-<dd><p>Specify that the <em>host</em> code should be built into position-independent
-machine code (with -fPIC), allowing it to be used within shared libraries,
-but yielding a slightly slower compiler.
-</p>
-<p>Currently this option is only of use to people developing GCC itself.
-</p>
-<p>Contrast with <samp>--enable-shared</samp>, which affects <em>target</em>
-libraries.
-</p>
-</dd>
-<dt><code><a name="with_002dgnu_002das"></a>--with-gnu-as</code></dt>
-<dd><p>Specify that the compiler should assume that the
-assembler it finds is the GNU assembler. However, this does not modify
-the rules to find an assembler and will result in confusion if the
-assembler found is not actually the GNU assembler. (Confusion may also
-result if the compiler finds the GNU assembler but has not been
-configured with <samp>--with-gnu-as</samp>.) If you have more than one
-assembler installed on your system, you may want to use this option in
-connection with <samp>--with-as=<var>pathname</var></samp> or
-<samp>--with-build-time-tools=<var>pathname</var></samp>.
-</p>
-<p>The following systems are the only ones where it makes a difference
-whether you use the GNU assembler. On any other system,
-<samp>--with-gnu-as</samp> has no effect.
-</p>
-<ul>
-<li> &lsquo;<samp>hppa1.0-<var>any</var>-<var>any</var></samp>&rsquo;
-</li><li> &lsquo;<samp>hppa1.1-<var>any</var>-<var>any</var></samp>&rsquo;
-</li><li> &lsquo;<samp>sparc-sun-solaris2.<var>any</var></samp>&rsquo;
-</li><li> &lsquo;<samp>sparc64-<var>any</var>-solaris2.<var>any</var></samp>&rsquo;
-</li></ul>
-
-</dd>
-<dt><code><a name="with_002das"></a>--with-as=<var>pathname</var></code></dt>
-<dd><p>Specify that the compiler should use the assembler pointed to by
-<var>pathname</var>, rather than the one found by the standard rules to find
-an assembler, which are:
-</p><ul>
-<li> Unless GCC is being built with a cross compiler, check the
-<samp><var>libexec</var>/gcc/<var>target</var>/<var>version</var></samp> directory.
-<var>libexec</var> defaults to <samp><var>exec-prefix</var>/libexec</samp>;
-<var>exec-prefix</var> defaults to <var>prefix</var>, which
-defaults to <samp>/usr/local</samp> unless overridden by the
-<samp>--prefix=<var>pathname</var></samp> switch described above. <var>target</var>
-is the target system triple, such as &lsquo;<samp>sparc-sun-solaris2.7</samp>&rsquo;, and
-<var>version</var> denotes the GCC version, such as 3.0.
-
-</li><li> If the target system is the same that you are building on, check
-operating system specific directories (e.g. <samp>/usr/ccs/bin</samp> on
-Sun Solaris 2).
-
-</li><li> Check in the <code>PATH</code> for a tool whose name is prefixed by the
-target system triple.
-
-</li><li> Check in the <code>PATH</code> 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).
-</li></ul>
-
-<p>You may want to use <samp>--with-as</samp> if no assembler
-is installed in the directories listed above, or if you have multiple
-assemblers installed and want to choose one that is not found by the
-above rules.
-</p>
-</dd>
-<dt><code><a name="with_002dgnu_002dld"></a>--with-gnu-ld</code></dt>
-<dd><p>Same as <a href="#with-gnu-as"><samp>--with-gnu-as</samp></a>
-but for the linker.
-</p>
-</dd>
-<dt><code>--with-ld=<var>pathname</var></code></dt>
-<dd><p>Same as <a href="#with-as"><samp>--with-as</samp></a>
-but for the linker.
-</p>
-</dd>
-<dt><code>--with-stabs</code></dt>
-<dd><p>Specify that stabs debugging
-information should be used instead of whatever format the host normally
-uses. Normally GCC uses the same debug format as the host system.
-</p>
-<p>On MIPS based systems and on Alphas, you must specify whether you want
-GCC to create the normal ECOFF debugging format, or to use BSD-style
-stabs passed through the ECOFF symbol table. The normal ECOFF debug
-format cannot fully handle languages other than C. BSD stabs format can
-handle other languages, but it only works with the GNU debugger GDB.
-</p>
-<p>Normally, GCC uses the ECOFF debugging format by default; if you
-prefer BSD stabs, specify <samp>--with-stabs</samp> when you configure GCC.
-</p>
-<p>No matter which default you choose when you configure GCC, the user
-can use the <samp>-gcoff</samp> and <samp>-gstabs+</samp> options to specify explicitly
-the debug format for a particular compilation.
-</p>
-<p><samp>--with-stabs</samp> is meaningful on the ISC system on the 386, also, if
-<samp>--with-gas</samp> is used. It selects use of stabs debugging
-information embedded in COFF output. This kind of debugging information
-supports C++ well; ordinary COFF debugging information does not.
-</p>
-<p><samp>--with-stabs</samp> is also meaningful on 386 systems running SVR4. It
-selects use of stabs debugging information embedded in ELF output. The
-C++ compiler currently (2.6.0) does not support the DWARF debugging
-information normally used on 386 SVR4 platforms; stabs provide a
-workable alternative. This requires gas and gdb, as the normal SVR4
-tools can not generate or interpret stabs.
-</p>
-</dd>
-<dt><code>--with-tls=<var>dialect</var></code></dt>
-<dd><p>Specify the default TLS dialect, for systems were there is a choice.
-For ARM targets, possible values for <var>dialect</var> are <code>gnu</code> or
-<code>gnu2</code>, which select between the original GNU dialect and the GNU TLS
-descriptor-based dialect.
-</p>
-</dd>
-<dt><code>--enable-multiarch</code></dt>
-<dd><p>Specify whether to enable or disable multiarch support. The default is
-to check for glibc start files in a multiarch location, and enable it
-if the files are found. The auto detection is enabled for native builds,
-and for cross builds configured with <samp>--with-sysroot</samp>, and without
-<samp>--with-native-system-header-dir</samp>.
-More documentation about multiarch can be found at
-<a href="http://wiki.debian.org/Multiarch">http://wiki.debian.org/Multiarch</a>.
-</p>
-</dd>
-<dt><code>--enable-vtable-verify</code></dt>
-<dd><p>Specify whether to enable or disable the vtable verification feature.
-Enabling this feature causes libstdc++ to be built with its virtual calls
-in verifiable mode. This means that, when linked with libvtv, every
-virtual call in libstdc++ will verify the vtable pointer through which the
-call will be made before actually making the call. If not linked with libvtv,
-the verifier will call stub functions (in libstdc++ itself) and do nothing.
-If vtable verification is disabled, then libstdc++ is not built with its
-virtual calls in verifiable mode at all. However the libvtv library will
-still be built (see <samp>--disable-libvtv</samp> to turn off building libvtv).
-<samp>--disable-vtable-verify</samp> is the default.
-</p>
-</dd>
-<dt><code>--disable-multilib</code></dt>
-<dd><p>Specify that multiple target
-libraries to support different target variants, calling
-conventions, etc. should not be built. The default is to build a
-predefined set of them.
-</p>
-<p>Some targets provide finer-grained control over which multilibs are built
-(e.g., <samp>--disable-softfloat</samp>):
-</p><dl compact="compact">
-<dt><code>arm-*-*</code></dt>
-<dd><p>fpu, 26bit, underscore, interwork, biendian, nofmult.
-</p>
-</dd>
-<dt><code>m68*-*-*</code></dt>
-<dd><p>softfloat, m68881, m68000, m68020.
-</p>
-</dd>
-<dt><code>mips*-*-*</code></dt>
-<dd><p>single-float, biendian, softfloat.
-</p>
-</dd>
-<dt><code>powerpc*-*-*, rs6000*-*-*</code></dt>
-<dd><p>aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
-sysv, aix.
-</p>
-</dd>
-</dl>
-
-</dd>
-<dt><code>--with-multilib-list=<var>list</var></code></dt>
-<dt><code>--without-multilib-list</code></dt>
-<dd><p>Specify what multilibs to build.
-Currently only implemented for sh*-*-* and x86-64-*-linux*.
-</p>
-<dl compact="compact">
-<dt><code>sh*-*-*</code></dt>
-<dd><p><var>list</var> is a comma separated list of CPU names. These must be of the
-form <code>sh*</code> or <code>m*</code> (in which case they match the compiler option
-for that processor). The list should not contain any endian options -
-these are handled by <samp>--with-endian</samp>.
-</p>
-<p>If <var>list</var> is empty, then there will be no multilibs for extra
-processors. The multilib for the secondary endian remains enabled.
-</p>
-<p>As a special case, if an entry in the list starts with a <code>!</code>
-(exclamation point), then it is added to the list of excluded multilibs.
-Entries of this sort should be compatible with &lsquo;<samp>MULTILIB_EXCLUDES</samp>&rsquo;
-(once the leading <code>!</code> has been stripped).
-</p>
-<p>If <samp>--with-multilib-list</samp> is not given, then a default set of
-multilibs is selected based on the value of <samp>--target</samp>. This is
-usually the complete set of libraries, but some targets imply a more
-specialized subset.
-</p>
-<p>Example 1: to configure a compiler for SH4A only, but supporting both
-endians, with little endian being the default:
-</p><div class="smallexample">
-<pre class="smallexample">--with-cpu=sh4a --with-endian=little,big --with-multilib-list=
-</pre></div>
-
-<p>Example 2: to configure a compiler for both SH4A and SH4AL-DSP, but with
-only little endian SH4AL:
-</p><div class="smallexample">
-<pre class="smallexample">--with-cpu=sh4a --with-endian=little,big \
---with-multilib-list=sh4al,!mb/m4al
-</pre></div>
-
-</dd>
-<dt><code>x86-64-*-linux*</code></dt>
-<dd><p><var>list</var> is a comma separated list of <code>m32</code>, <code>m64</code> and
-<code>mx32</code> to enable 32-bit, 64-bit and x32 run-time libraries,
-respectively. If <var>list</var> is empty, then there will be no multilibs
-and only the default run-time library will be enabled.
-</p>
-<p>If <samp>--with-multilib-list</samp> is not given, then only 32-bit and
-64-bit run-time libraries will be enabled.
-</p></dd>
-</dl>
-
-</dd>
-<dt><code>--with-endian=<var>endians</var></code></dt>
-<dd><p>Specify what endians to use.
-Currently only implemented for sh*-*-*.
-</p>
-<p><var>endians</var> may be one of the following:
-</p><dl compact="compact">
-<dt><code>big</code></dt>
-<dd><p>Use big endian exclusively.
-</p></dd>
-<dt><code>little</code></dt>
-<dd><p>Use little endian exclusively.
-</p></dd>
-<dt><code>big,little</code></dt>
-<dd><p>Use big endian by default. Provide a multilib for little endian.
-</p></dd>
-<dt><code>little,big</code></dt>
-<dd><p>Use little endian by default. Provide a multilib for big endian.
-</p></dd>
-</dl>
-
-</dd>
-<dt><code>--enable-threads</code></dt>
-<dd><p>Specify that the target
-supports threads. This affects the Objective-C compiler and runtime
-library, and exception handling for other languages like C++ and Java.
-On some systems, this is the default.
-</p>
-<p>In general, the best (and, in many cases, the only known) threading
-model available will be configured for use. Beware that on some
-systems, GCC has not been taught what threading models are generally
-available for the system. In this case, <samp>--enable-threads</samp> is an
-alias for <samp>--enable-threads=single</samp>.
-</p>
-</dd>
-<dt><code>--disable-threads</code></dt>
-<dd><p>Specify that threading support should be disabled for the system.
-This is an alias for <samp>--enable-threads=single</samp>.
-</p>
-</dd>
-<dt><code>--enable-threads=<var>lib</var></code></dt>
-<dd><p>Specify that
-<var>lib</var> is the thread support library. This affects the Objective-C
-compiler and runtime library, and exception handling for other languages
-like C++ and Java. The possibilities for <var>lib</var> are:
-</p>
-<dl compact="compact">
-<dt><code>aix</code></dt>
-<dd><p>AIX thread support.
-</p></dd>
-<dt><code>dce</code></dt>
-<dd><p>DCE thread support.
-</p></dd>
-<dt><code>lynx</code></dt>
-<dd><p>LynxOS thread support.
-</p></dd>
-<dt><code>mipssde</code></dt>
-<dd><p>MIPS SDE thread support.
-</p></dd>
-<dt><code>no</code></dt>
-<dd><p>This is an alias for &lsquo;<samp>single</samp>&rsquo;.
-</p></dd>
-<dt><code>posix</code></dt>
-<dd><p>Generic POSIX/Unix98 thread support.
-</p></dd>
-<dt><code>rtems</code></dt>
-<dd><p>RTEMS thread support.
-</p></dd>
-<dt><code>single</code></dt>
-<dd><p>Disable thread support, should work for all platforms.
-</p></dd>
-<dt><code>tpf</code></dt>
-<dd><p>TPF thread support.
-</p></dd>
-<dt><code>vxworks</code></dt>
-<dd><p>VxWorks thread support.
-</p></dd>
-<dt><code>win32</code></dt>
-<dd><p>Microsoft Win32 API thread support.
-</p></dd>
-</dl>
-
-</dd>
-<dt><code>--enable-tls</code></dt>
-<dd><p>Specify that the target supports TLS (Thread Local Storage). Usually
-configure can correctly determine if TLS is supported. In cases where
-it guesses incorrectly, TLS can be explicitly enabled or disabled with
-<samp>--enable-tls</samp> or <samp>--disable-tls</samp>. This can happen if
-the assembler supports TLS but the C library does not, or if the
-assumptions made by the configure test are incorrect.
-</p>
-</dd>
-<dt><code>--disable-tls</code></dt>
-<dd><p>Specify that the target does not support TLS.
-This is an alias for <samp>--enable-tls=no</samp>.
-</p>
-</dd>
-<dt><code>--with-cpu=<var>cpu</var></code></dt>
-<dt><code>--with-cpu-32=<var>cpu</var></code></dt>
-<dt><code>--with-cpu-64=<var>cpu</var></code></dt>
-<dd><p>Specify which cpu variant the compiler should generate code for by default.
-<var>cpu</var> will be used as the default value of the <samp>-mcpu=</samp> switch.
-This option is only supported on some targets, including ARC, ARM, i386, M68k,
-PowerPC, and SPARC. It is mandatory for ARC. The <samp>--with-cpu-32</samp> and
-<samp>--with-cpu-64</samp> options specify separate default CPUs for
-32-bit and 64-bit modes; these options are only supported for i386,
-x86-64 and PowerPC.
-</p>
-</dd>
-<dt><code>--with-schedule=<var>cpu</var></code></dt>
-<dt><code>--with-arch=<var>cpu</var></code></dt>
-<dt><code>--with-arch-32=<var>cpu</var></code></dt>
-<dt><code>--with-arch-64=<var>cpu</var></code></dt>
-<dt><code>--with-tune=<var>cpu</var></code></dt>
-<dt><code>--with-tune-32=<var>cpu</var></code></dt>
-<dt><code>--with-tune-64=<var>cpu</var></code></dt>
-<dt><code>--with-abi=<var>abi</var></code></dt>
-<dt><code>--with-fpu=<var>type</var></code></dt>
-<dt><code>--with-float=<var>type</var></code></dt>
-<dd><p>These configure options provide default values for the <samp>-mschedule=</samp>,
-<samp>-march=</samp>, <samp>-mtune=</samp>, <samp>-mabi=</samp>, and <samp>-mfpu=</samp>
-options and for <samp>-mhard-float</samp> or <samp>-msoft-float</samp>. As with
-<samp>--with-cpu</samp>, which switches will be accepted and acceptable values
-of the arguments depend on the target.
-</p>
-</dd>
-<dt><code>--with-mode=<var>mode</var></code></dt>
-<dd><p>Specify if the compiler should default to <samp>-marm</samp> or <samp>-mthumb</samp>.
-This option is only supported on ARM targets.
-</p>
-</dd>
-<dt><code>--with-stack-offset=<var>num</var></code></dt>
-<dd><p>This option sets the default for the -mstack-offset=<var>num</var> option,
-and will thus generally also control the setting of this option for
-libraries. This option is only supported on Epiphany targets.
-</p>
-</dd>
-<dt><code>--with-fpmath=<var>isa</var></code></dt>
-<dd><p>This options sets <samp>-mfpmath=sse</samp> by default and specifies the default
-ISA for floating-point arithmetics. You can select either &lsquo;<samp>sse</samp>&rsquo; which
-enables <samp>-msse2</samp> or &lsquo;<samp>avx</samp>&rsquo; which enables <samp>-mavx</samp> by default.
-This option is only supported on i386 and x86-64 targets.
-</p>
-</dd>
-<dt><code>--with-nan=<var>encoding</var></code></dt>
-<dd><p>On MIPS targets, set the default encoding convention to use for the
-special not-a-number (NaN) IEEE 754 floating-point data. The
-possibilities for <var>encoding</var> are:
-</p><dl compact="compact">
-<dt><code>legacy</code></dt>
-<dd><p>Use the legacy encoding, as with the <samp>-mnan=legacy</samp> command-line
-option.
-</p></dd>
-<dt><code>2008</code></dt>
-<dd><p>Use the 754-2008 encoding, as with the <samp>-mnan=2008</samp> command-line
-option.
-</p></dd>
-</dl>
-<p>To use this configuration option you must have an assembler version
-installed that supports the <samp>-mnan=</samp> command-line option too.
-In the absence of this configuration option the default convention is
-the legacy encoding, as when neither of the <samp>-mnan=2008</samp> and
-<samp>-mnan=legacy</samp> command-line options has been used.
-</p>
-</dd>
-<dt><code>--with-divide=<var>type</var></code></dt>
-<dd><p>Specify how the compiler should generate code for checking for
-division by zero. This option is only supported on the MIPS target.
-The possibilities for <var>type</var> are:
-</p><dl compact="compact">
-<dt><code>traps</code></dt>
-<dd><p>Division by zero checks use conditional traps (this is the default on
-systems that support conditional traps).
-</p></dd>
-<dt><code>breaks</code></dt>
-<dd><p>Division by zero checks use the break instruction.
-</p></dd>
-</dl>
-
-
-</dd>
-<dt><code>--with-llsc</code></dt>
-<dd><p>On MIPS targets, make <samp>-mllsc</samp> the default when no
-<samp>-mno-llsc</samp> option is passed. This is the default for
-Linux-based targets, as the kernel will emulate them if the ISA does
-not provide them.
-</p>
-</dd>
-<dt><code>--without-llsc</code></dt>
-<dd><p>On MIPS targets, make <samp>-mno-llsc</samp> the default when no
-<samp>-mllsc</samp> option is passed.
-</p>
-</dd>
-<dt><code>--with-synci</code></dt>
-<dd><p>On MIPS targets, make <samp>-msynci</samp> the default when no
-<samp>-mno-synci</samp> option is passed.
-</p>
-</dd>
-<dt><code>--without-synci</code></dt>
-<dd><p>On MIPS targets, make <samp>-mno-synci</samp> the default when no
-<samp>-msynci</samp> option is passed. This is the default.
-</p>
-</dd>
-<dt><code>--with-mips-plt</code></dt>
-<dd><p>On MIPS targets, make use of copy relocations and PLTs.
-These features are extensions to the traditional
-SVR4-based MIPS ABIs and require support from GNU binutils
-and the runtime C library.
-</p>
-</dd>
-<dt><code>--enable-__cxa_atexit</code></dt>
-<dd><p>Define if you want to use __cxa_atexit, rather than atexit, to
-register C++ destructors for local statics and global objects.
-This is essential for fully standards-compliant handling of
-destructors, but requires __cxa_atexit in libc. This option is currently
-only available on systems with GNU libc. When enabled, this will cause
-<samp>-fuse-cxa-atexit</samp> to be passed by default.
-</p>
-</dd>
-<dt><code>--enable-gnu-indirect-function</code></dt>
-<dd><p>Define if you want to enable the <code>ifunc</code> attribute. This option is
-currently only available on systems with GNU libc on certain targets.
-</p>
-</dd>
-<dt><code>--enable-target-optspace</code></dt>
-<dd><p>Specify that target
-libraries should be optimized for code space instead of code speed.
-This is the default for the m32r platform.
-</p>
-</dd>
-<dt><code>--with-cpp-install-dir=<var>dirname</var></code></dt>
-<dd><p>Specify that the user visible <code>cpp</code> program should be installed
-in <samp><var>prefix</var>/<var>dirname</var>/cpp</samp>, in addition to <var>bindir</var>.
-</p>
-</dd>
-<dt><code>--enable-comdat</code></dt>
-<dd><p>Enable COMDAT group support. This is primarily used to override the
-automatically detected value.
-</p>
-</dd>
-<dt><code>--enable-initfini-array</code></dt>
-<dd><p>Force the use of sections <code>.init_array</code> and <code>.fini_array</code>
-(instead of <code>.init</code> and <code>.fini</code>) for constructors and
-destructors. Option <samp>--disable-initfini-array</samp> has the
-opposite effect. If neither option is specified, the configure script
-will try to guess whether the <code>.init_array</code> and
-<code>.fini_array</code> sections are supported and, if they are, use them.
-</p>
-</dd>
-<dt><code>--enable-link-mutex</code></dt>
-<dd><p>When building GCC, use a mutex to avoid linking the compilers for
-multiple languages at the same time, to avoid thrashing on build
-systems with limited free memory. The default is not to use such a mutex.
-</p>
-</dd>
-<dt><code>--enable-maintainer-mode</code></dt>
-<dd><p>The build rules that regenerate the Autoconf and Automake output files as
-well as the GCC master message catalog <samp>gcc.pot</samp> are normally
-disabled. This is because it can only be rebuilt if the complete source
-tree is present. If you have changed the sources and want to rebuild the
-catalog, configuring with <samp>--enable-maintainer-mode</samp> will enable
-this. Note that you need a recent version of the <code>gettext</code> tools
-to do so.
-</p>
-</dd>
-<dt><code>--disable-bootstrap</code></dt>
-<dd><p>For a native build, the default configuration is to perform
-a 3-stage bootstrap of the compiler when &lsquo;<samp>make</samp>&rsquo; is invoked,
-testing that GCC can compile itself correctly. If you want to disable
-this process, you can configure with <samp>--disable-bootstrap</samp>.
-</p>
-</dd>
-<dt><code>--enable-bootstrap</code></dt>
-<dd><p>In special cases, you may want to perform a 3-stage build
-even if the target and host triplets are different.
-This is possible when the host can run code compiled for
-the target (e.g. host is i686-linux, target is i486-linux).
-Starting from GCC 4.2, to do this you have to configure explicitly
-with <samp>--enable-bootstrap</samp>.
-</p>
-</dd>
-<dt><code>--enable-generated-files-in-srcdir</code></dt>
-<dd><p>Neither the .c and .h files that are generated from Bison and flex nor the
-info manuals and man pages that are built from the .texi files are present
-in the SVN development tree. When building GCC from that development tree,
-or from one of our snapshots, those generated files are placed in your
-build directory, which allows for the source to be in a readonly
-directory.
-</p>
-<p>If you configure with <samp>--enable-generated-files-in-srcdir</samp> then those
-generated files will go into the source directory. This is mainly intended
-for generating release or prerelease tarballs of the GCC sources, since it
-is not a requirement that the users of source releases to have flex, Bison,
-or makeinfo.
-</p>
-</dd>
-<dt><code>--enable-version-specific-runtime-libs</code></dt>
-<dd><p>Specify
-that runtime libraries should be installed in the compiler specific
-subdirectory (<samp><var>libdir</var>/gcc</samp>) rather than the usual places. In
-addition, &lsquo;<samp>libstdc++</samp>&rsquo;&rsquo;s include files will be installed into
-<samp><var>libdir</var></samp> unless you overruled it by using
-<samp>--with-gxx-include-dir=<var>dirname</var></samp>. Using this option is
-particularly useful if you intend to use several versions of GCC in
-parallel. This is currently supported by &lsquo;<samp>libgfortran</samp>&rsquo;,
-&lsquo;<samp>libjava</samp>&rsquo;, &lsquo;<samp>libstdc++</samp>&rsquo;, and &lsquo;<samp>libobjc</samp>&rsquo;.
-</p>
-</dd>
-<dt><code>--enable-languages=<var>lang1</var>,<var>lang2</var>,&hellip;</code></dt>
-<dd><p>Specify that only a particular subset of compilers and
-their runtime libraries should be built. For a list of valid values for
-<var>langN</var> you can issue the following command in the
-<samp>gcc</samp> directory of your GCC source tree:<br>
-</p><div class="smallexample">
-<pre class="smallexample">grep language= */config-lang.in
-</pre></div>
-<p>Currently, you can use any of the following:
-<code>all</code>, <code>ada</code>, <code>c</code>, <code>c++</code>, <code>fortran</code>,
-<code>go</code>, <code>java</code>, <code>objc</code>, <code>obj-c++</code>.
-Building the Ada compiler has special requirements, see below.
-If you do not pass this flag, or specify the option <code>all</code>, then all
-default languages available in the <samp>gcc</samp> sub-tree will be configured.
-Ada, Go and Objective-C++ are not default languages; the rest are.
-</p>
-</dd>
-<dt><code>--enable-stage1-languages=<var>lang1</var>,<var>lang2</var>,&hellip;</code></dt>
-<dd><p>Specify that a particular subset of compilers and their runtime
-libraries should be built with the system C compiler during stage 1 of
-the bootstrap process, rather than only in later stages with the
-bootstrapped C compiler. The list of valid values is the same as for
-<samp>--enable-languages</samp>, and the option <code>all</code> will select all
-of the languages enabled by <samp>--enable-languages</samp>. This option is
-primarily useful for GCC development; for instance, when a development
-version of the compiler cannot bootstrap due to compiler bugs, or when
-one is debugging front ends other than the C front end. When this
-option is used, one can then build the target libraries for the
-specified languages with the stage-1 compiler by using <code>make
-stage1-bubble all-target</code>, or run the testsuite on the stage-1 compiler
-for the specified languages using <code>make stage1-start check-gcc</code>.
-</p>
-</dd>
-<dt><code>--disable-libada</code></dt>
-<dd><p>Specify that the run-time libraries and tools used by GNAT should not
-be built. This can be useful for debugging, or for compatibility with
-previous Ada build procedures, when it was required to explicitly
-do a &lsquo;<samp>make -C gcc gnatlib_and_tools</samp>&rsquo;.
-</p>
-</dd>
-<dt><code>--disable-libssp</code></dt>
-<dd><p>Specify that the run-time libraries for stack smashing protection
-should not be built.
-</p>
-</dd>
-<dt><code>--disable-libquadmath</code></dt>
-<dd><p>Specify that the GCC quad-precision math library should not be built.
-On some systems, the library is required to be linkable when building
-the Fortran front end, unless <samp>--disable-libquadmath-support</samp>
-is used.
-</p>
-</dd>
-<dt><code>--disable-libquadmath-support</code></dt>
-<dd><p>Specify that the Fortran front end and <code>libgfortran</code> do not add
-support for <code>libquadmath</code> on systems supporting it.
-</p>
-</dd>
-<dt><code>--disable-libgomp</code></dt>
-<dd><p>Specify that the run-time libraries used by GOMP should not be built.
-</p>
-</dd>
-<dt><code>--disable-libvtv</code></dt>
-<dd><p>Specify that the run-time libraries used by vtable verification
-should not be built.
-</p>
-</dd>
-<dt><code>--with-dwarf2</code></dt>
-<dd><p>Specify that the compiler should
-use DWARF 2 debugging information as the default.
-</p>
-</dd>
-<dt><code>--enable-targets=all</code></dt>
-<dt><code>--enable-targets=<var>target_list</var></code></dt>
-<dd><p>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.
-On mips-linux, this will build a tri-arch compiler (ABI o32/n32/64),
-defaulted to o32.
-Currently, this option only affects sparc-linux, powerpc-linux, x86-linux,
-mips-linux and s390-linux.
-</p>
-</dd>
-<dt><code>--enable-secureplt</code></dt>
-<dd><p>This option enables <samp>-msecure-plt</samp> by default for powerpc-linux.
-See &ldquo;RS/6000 and PowerPC Options&rdquo; in the main manual
-</p>
-</dd>
-<dt><code>--enable-cld</code></dt>
-<dd><p>This option enables <samp>-mcld</samp> by default for 32-bit x86 targets.
-See &ldquo;i386 and x86-64 Options&rdquo; in the main manual
-</p>
-</dd>
-<dt><code>--enable-win32-registry</code></dt>
-<dt><code>--enable-win32-registry=<var>key</var></code></dt>
-<dt><code>--disable-win32-registry</code></dt>
-<dd><p>The <samp>--enable-win32-registry</samp> option enables Microsoft Windows-hosted GCC
-to look up installations paths in the registry using the following key:
-</p>
-<div class="smallexample">
-<pre class="smallexample"><code>HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\<var>key</var></code>
-</pre></div>
-
-<p><var>key</var> defaults to GCC version number, and can be overridden by the
-<samp>--enable-win32-registry=<var>key</var></samp> option. Vendors and distributors
-who use custom installers are encouraged to provide a different key,
-perhaps one comprised of vendor name and GCC version number, to
-avoid conflict with existing installations. This feature is enabled
-by default, and can be disabled by <samp>--disable-win32-registry</samp>
-option. This option has no effect on the other hosts.
-</p>
-</dd>
-<dt><code>--nfp</code></dt>
-<dd><p>Specify that the machine does not have a floating point unit. This
-option only applies to &lsquo;<samp>m68k-sun-sunos<var>n</var></samp>&rsquo;. On any other
-system, <samp>--nfp</samp> has no effect.
-</p>
-</dd>
-<dt><code>--enable-werror</code></dt>
-<dt><code>--disable-werror</code></dt>
-<dt><code>--enable-werror=yes</code></dt>
-<dt><code>--enable-werror=no</code></dt>
-<dd><p>When you specify this option, it controls whether certain files in the
-compiler are built with <samp>-Werror</samp> in bootstrap stage2 and later.
-If you don&rsquo;t specify it, <samp>-Werror</samp> is turned on for the main
-development trunk. However it defaults to off for release branches and
-final releases. The specific files which get <samp>-Werror</samp> are
-controlled by the Makefiles.
-</p>
-</dd>
-<dt><code>--enable-checking</code></dt>
-<dt><code>--enable-checking=<var>list</var></code></dt>
-<dd><p>When you specify this option, the compiler is built to perform internal
-consistency checks of the requested complexity. This does not change the
-generated code, but adds error checking within the compiler. This will
-slow down the compiler and may only work properly if you are building
-the compiler with GCC. This is &lsquo;<samp>yes</samp>&rsquo; by default when building
-from SVN or snapshots, but &lsquo;<samp>release</samp>&rsquo; for releases. The default
-for building the stage1 compiler is &lsquo;<samp>yes</samp>&rsquo;. More control
-over the checks may be had by specifying <var>list</var>. The categories of
-checks available are &lsquo;<samp>yes</samp>&rsquo; (most common checks
-&lsquo;<samp>assert,misc,tree,gc,rtlflag,runtime</samp>&rsquo;), &lsquo;<samp>no</samp>&rsquo; (no checks at
-all), &lsquo;<samp>all</samp>&rsquo; (all but &lsquo;<samp>valgrind</samp>&rsquo;), &lsquo;<samp>release</samp>&rsquo; (cheapest
-checks &lsquo;<samp>assert,runtime</samp>&rsquo;) or &lsquo;<samp>none</samp>&rsquo; (same as &lsquo;<samp>no</samp>&rsquo;).
-Individual checks can be enabled with these flags &lsquo;<samp>assert</samp>&rsquo;,
-&lsquo;<samp>df</samp>&rsquo;, &lsquo;<samp>fold</samp>&rsquo;, &lsquo;<samp>gc</samp>&rsquo;, &lsquo;<samp>gcac</samp>&rsquo; &lsquo;<samp>misc</samp>&rsquo;, &lsquo;<samp>rtl</samp>&rsquo;,
-&lsquo;<samp>rtlflag</samp>&rsquo;, &lsquo;<samp>runtime</samp>&rsquo;, &lsquo;<samp>tree</samp>&rsquo;, and &lsquo;<samp>valgrind</samp>&rsquo;.
-</p>
-<p>The &lsquo;<samp>valgrind</samp>&rsquo; check requires the external <code>valgrind</code>
-simulator, available from <a href="http://valgrind.org/">http://valgrind.org/</a>. The
-&lsquo;<samp>df</samp>&rsquo;, &lsquo;<samp>rtl</samp>&rsquo;, &lsquo;<samp>gcac</samp>&rsquo; and &lsquo;<samp>valgrind</samp>&rsquo; checks are very expensive.
-To disable all checking, &lsquo;<samp>--disable-checking</samp>&rsquo; or
-&lsquo;<samp>--enable-checking=none</samp>&rsquo; must be explicitly requested. Disabling
-assertions will make the compiler and runtime slightly faster but
-increase the risk of undetected internal errors causing wrong code to be
-generated.
-</p>
-</dd>
-<dt><code>--disable-stage1-checking</code></dt>
-<dt><code>--enable-stage1-checking</code></dt>
-<dt><code>--enable-stage1-checking=<var>list</var></code></dt>
-<dd><p>If no <samp>--enable-checking</samp> option is specified the stage1
-compiler will be built with &lsquo;<samp>yes</samp>&rsquo; checking enabled, otherwise
-the stage1 checking flags are the same as specified by
-<samp>--enable-checking</samp>. To build the stage1 compiler with
-different checking options use <samp>--enable-stage1-checking</samp>.
-The list of checking options is the same as for <samp>--enable-checking</samp>.
-If your system is too slow or too small to bootstrap a released compiler
-with checking for stage1 enabled, you can use &lsquo;<samp>--disable-stage1-checking</samp>&rsquo;
-to disable checking for the stage1 compiler.
-</p>
-</dd>
-<dt><code>--enable-coverage</code></dt>
-<dt><code>--enable-coverage=<var>level</var></code></dt>
-<dd><p>With this option, the compiler is built to collect self coverage
-information, every time it is run. This is for internal development
-purposes, and only works when the compiler is being built with gcc. The
-<var>level</var> argument controls whether the compiler is built optimized or
-not, values are &lsquo;<samp>opt</samp>&rsquo; and &lsquo;<samp>noopt</samp>&rsquo;. For coverage analysis you
-want to disable optimization, for performance analysis you want to
-enable optimization. When coverage is enabled, the default level is
-without optimization.
-</p>
-</dd>
-<dt><code>--enable-gather-detailed-mem-stats</code></dt>
-<dd><p>When this option is specified more detailed information on memory
-allocation is gathered. This information is printed when using
-<samp>-fmem-report</samp>.
-</p>
-</dd>
-<dt><code>--enable-nls</code></dt>
-<dt><code>--disable-nls</code></dt>
-<dd><p>The <samp>--enable-nls</samp> option enables Native Language Support (NLS),
-which lets GCC output diagnostics in languages other than American
-English. Native Language Support is enabled by default if not doing a
-canadian cross build. The <samp>--disable-nls</samp> option disables NLS.
-</p>
-</dd>
-<dt><code>--with-included-gettext</code></dt>
-<dd><p>If NLS is enabled, the <samp>--with-included-gettext</samp> option causes the build
-procedure to prefer its copy of GNU <code>gettext</code>.
-</p>
-</dd>
-<dt><code>--with-catgets</code></dt>
-<dd><p>If NLS is enabled, and if the host lacks <code>gettext</code> but has the
-inferior <code>catgets</code> interface, the GCC build procedure normally
-ignores <code>catgets</code> and instead uses GCC&rsquo;s copy of the GNU
-<code>gettext</code> library. The <samp>--with-catgets</samp> option causes the
-build procedure to use the host&rsquo;s <code>catgets</code> in this situation.
-</p>
-</dd>
-<dt><code>--with-libiconv-prefix=<var>dir</var></code></dt>
-<dd><p>Search for libiconv header files in <samp><var>dir</var>/include</samp> and
-libiconv library files in <samp><var>dir</var>/lib</samp>.
-</p>
-</dd>
-<dt><code>--enable-obsolete</code></dt>
-<dd><p>Enable configuration for an obsoleted system. If you attempt to
-configure GCC for a system (build, host, or target) which has been
-obsoleted, and you do not specify this flag, configure will halt with an
-error message.
-</p>
-<p>All support for systems which have been obsoleted in one release of GCC
-is removed entirely in the next major release, unless someone steps
-forward to maintain the port.
-</p>
-</dd>
-<dt><code>--enable-decimal-float</code></dt>
-<dt><code>--enable-decimal-float=yes</code></dt>
-<dt><code>--enable-decimal-float=no</code></dt>
-<dt><code>--enable-decimal-float=bid</code></dt>
-<dt><code>--enable-decimal-float=dpd</code></dt>
-<dt><code>--disable-decimal-float</code></dt>
-<dd><p>Enable (or disable) support for the C decimal floating point extension
-that is in the IEEE 754-2008 standard. This is enabled by default only
-on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also
-support it, but require the user to specifically enable it. You can
-optionally control which decimal floating point format is used (either
-&lsquo;<samp>bid</samp>&rsquo; or &lsquo;<samp>dpd</samp>&rsquo;). The &lsquo;<samp>bid</samp>&rsquo; (binary integer decimal)
-format is default on i386 and x86_64 systems, and the &lsquo;<samp>dpd</samp>&rsquo;
-(densely packed decimal) format is default on PowerPC systems.
-</p>
-</dd>
-<dt><code>--enable-fixed-point</code></dt>
-<dt><code>--disable-fixed-point</code></dt>
-<dd><p>Enable (or disable) support for C fixed-point arithmetic.
-This option is enabled by default for some targets (such as MIPS) which
-have hardware-support for fixed-point operations. On other targets, you
-may enable this option manually.
-</p>
-</dd>
-<dt><code>--with-long-double-128</code></dt>
-<dd><p>Specify if <code>long double</code> type should be 128-bit by default on selected
-GNU/Linux architectures. If using <code>--without-long-double-128</code>,
-<code>long double</code> will be by default 64-bit, the same as <code>double</code> type.
-When neither of these configure options are used, the default will be
-128-bit <code>long double</code> when built against GNU C Library 2.4 and later,
-64-bit <code>long double</code> otherwise.
-</p>
-</dd>
-<dt><code>--with-gmp=<var>pathname</var></code></dt>
-<dt><code>--with-gmp-include=<var>pathname</var></code></dt>
-<dt><code>--with-gmp-lib=<var>pathname</var></code></dt>
-<dt><code>--with-mpfr=<var>pathname</var></code></dt>
-<dt><code>--with-mpfr-include=<var>pathname</var></code></dt>
-<dt><code>--with-mpfr-lib=<var>pathname</var></code></dt>
-<dt><code>--with-mpc=<var>pathname</var></code></dt>
-<dt><code>--with-mpc-include=<var>pathname</var></code></dt>
-<dt><code>--with-mpc-lib=<var>pathname</var></code></dt>
-<dd><p>If you want to build GCC but do not have the GMP library, the MPFR
-library and/or the MPC library installed in a standard location and
-do not have their sources present in the GCC source tree then you
-can explicitly specify the directory where they are installed
-(&lsquo;<samp>--with-gmp=<var>gmpinstalldir</var></samp>&rsquo;,
-&lsquo;<samp>--with-mpfr=<var>mpfrinstalldir</var></samp>&rsquo;,
-&lsquo;<samp>--with-mpc=<var>mpcinstalldir</var></samp>&rsquo;). The
-<samp>--with-gmp=<var>gmpinstalldir</var></samp> option is shorthand for
-<samp>--with-gmp-lib=<var>gmpinstalldir</var>/lib</samp> and
-<samp>--with-gmp-include=<var>gmpinstalldir</var>/include</samp>. Likewise the
-<samp>--with-mpfr=<var>mpfrinstalldir</var></samp> option is shorthand for
-<samp>--with-mpfr-lib=<var>mpfrinstalldir</var>/lib</samp> and
-<samp>--with-mpfr-include=<var>mpfrinstalldir</var>/include</samp>, also the
-<samp>--with-mpc=<var>mpcinstalldir</var></samp> option is shorthand for
-<samp>--with-mpc-lib=<var>mpcinstalldir</var>/lib</samp> and
-<samp>--with-mpc-include=<var>mpcinstalldir</var>/include</samp>. If these
-shorthand assumptions are not correct, you can use the explicit
-include and lib options directly. You might also need to ensure the
-shared libraries can be found by the dynamic linker when building and
-using GCC, for example by setting the runtime shared library path
-variable (<code>LD_LIBRARY_PATH</code> on GNU/Linux and Solaris systems).
-</p>
-<p>These flags are applicable to the host platform only. When building
-a cross compiler, they will not be used to configure target libraries.
-</p>
-</dd>
-<dt><code>--with-isl=<var>pathname</var></code></dt>
-<dt><code>--with-isl-include=<var>pathname</var></code></dt>
-<dt><code>--with-isl-lib=<var>pathname</var></code></dt>
-<dt><code>--with-cloog=<var>pathname</var></code></dt>
-<dt><code>--with-cloog-include=<var>pathname</var></code></dt>
-<dt><code>--with-cloog-lib=<var>pathname</var></code></dt>
-<dd><p>If you do not have ISL and the CLooG
-libraries installed in a standard location and you want to build GCC,
-you can explicitly specify the directory where they are installed
-(&lsquo;<samp>--with-isl=<var>islinstalldir</var></samp>&rsquo;,
-&lsquo;<samp>--with-cloog=<var>clooginstalldir</var></samp>&rsquo;). The
-<samp>--with-isl=<var>islinstalldir</var></samp> option is shorthand for
-<samp>--with-isl-lib=<var>islinstalldir</var>/lib</samp> and
-<samp>--with-isl-include=<var>islinstalldir</var>/include</samp>. Likewise the
-<samp>--with-cloog=<var>clooginstalldir</var></samp> option is shorthand for
-<samp>--with-cloog-lib=<var>clooginstalldir</var>/lib</samp> and
-<samp>--with-cloog-include=<var>clooginstalldir</var>/include</samp>. If these
-shorthand assumptions are not correct, you can use the explicit
-include and lib options directly.
-</p>
-<p>These flags are applicable to the host platform only. When building
-a cross compiler, they will not be used to configure target libraries.
-</p>
-</dd>
-<dt><code>--with-host-libstdcxx=<var>linker-args</var></code></dt>
-<dd><p>If you are linking with a static copy of PPL, you can use this option
-to specify how the linker should find the standard C++ library used
-internally by PPL. Typical values of <var>linker-args</var> might be
-&lsquo;<samp>-lstdc++</samp>&rsquo; or &lsquo;<samp>-Wl,-Bstatic,-lstdc++,-Bdynamic -lm</samp>&rsquo;. If you are
-linking with a shared copy of PPL, you probably do not need this
-option; shared library dependencies will cause the linker to search
-for the standard C++ library automatically.
-</p>
-</dd>
-<dt><code>--with-stage1-ldflags=<var>flags</var></code></dt>
-<dd><p>This option may be used to set linker flags to be used when linking
-stage 1 of GCC. These are also used when linking GCC if configured with
-<samp>--disable-bootstrap</samp>. By default no special flags are used.
-</p>
-</dd>
-<dt><code>--with-stage1-libs=<var>libs</var></code></dt>
-<dd><p>This option may be used to set libraries to be used when linking stage 1
-of GCC. These are also used when linking GCC if configured with
-<samp>--disable-bootstrap</samp>. The default is the argument to
-<samp>--with-host-libstdcxx</samp>, if specified.
-</p>
-</dd>
-<dt><code>--with-boot-ldflags=<var>flags</var></code></dt>
-<dd><p>This option may be used to set linker flags to be used when linking
-stage 2 and later when bootstrapping GCC. If neither &ndash;with-boot-libs
-nor &ndash;with-host-libstdcxx is set to a value, then the default is
-&lsquo;<samp>-static-libstdc++ -static-libgcc</samp>&rsquo;.
-</p>
-</dd>
-<dt><code>--with-boot-libs=<var>libs</var></code></dt>
-<dd><p>This option may be used to set libraries to be used when linking stage 2
-and later when bootstrapping GCC. The default is the argument to
-<samp>--with-host-libstdcxx</samp>, if specified.
-</p>
-</dd>
-<dt><code>--with-debug-prefix-map=<var>map</var></code></dt>
-<dd><p>Convert source directory names using <samp>-fdebug-prefix-map</samp> when
-building runtime libraries. &lsquo;<samp><var>map</var></samp>&rsquo; is a space-separated
-list of maps of the form &lsquo;<samp><var>old</var>=<var>new</var></samp>&rsquo;.
-</p>
-</dd>
-<dt><code>--enable-linker-build-id</code></dt>
-<dd><p>Tells GCC to pass <samp>--build-id</samp> option to the linker for all final
-links (links performed without the <samp>-r</samp> or <samp>--relocatable</samp>
-option), if the linker supports it. If you specify
-<samp>--enable-linker-build-id</samp>, but your linker does not
-support <samp>--build-id</samp> option, a warning is issued and the
-<samp>--enable-linker-build-id</samp> option is ignored. The default is off.
-</p>
-</dd>
-<dt><code>--with-linker-hash-style=<var>choice</var></code></dt>
-<dd><p>Tells GCC to pass <samp>--hash-style=<var>choice</var></samp> option to the
-linker for all final links. <var>choice</var> can be one of
-&lsquo;<samp>sysv</samp>&rsquo;, &lsquo;<samp>gnu</samp>&rsquo;, and &lsquo;<samp>both</samp>&rsquo; where &lsquo;<samp>sysv</samp>&rsquo; is the default.
-</p>
-</dd>
-<dt><code>--enable-gnu-unique-object</code></dt>
-<dt><code>--disable-gnu-unique-object</code></dt>
-<dd><p>Tells GCC to use the gnu_unique_object relocation for C++ template
-static data members and inline function local statics. Enabled by
-default for a toolchain with an assembler that accepts it and
-GLIBC 2.11 or above, otherwise disabled.
-</p>
-</dd>
-<dt><code>--enable-lto</code></dt>
-<dt><code>--disable-lto</code></dt>
-<dd><p>Enable support for link-time optimization (LTO). This is enabled by
-default, and may be disabled using <samp>--disable-lto</samp>.
-</p>
-</dd>
-<dt><code>--with-plugin-ld=<var>pathname</var></code></dt>
-<dd><p>Enable an alternate linker to be used at link-time optimization (LTO)
-link time when <samp>-fuse-linker-plugin</samp> is enabled.
-This linker should have plugin support such as gold starting with
-version 2.20 or GNU ld starting with version 2.21.
-See <samp>-fuse-linker-plugin</samp> for details.
-</p>
-</dd>
-<dt><code>--enable-canonical-system-headers</code></dt>
-<dt><code>--disable-canonical-system-headers</code></dt>
-<dd><p>Enable system header path canonicalization for <samp>libcpp</samp>. This can
-produce shorter header file paths in diagnostics and dependency output
-files, but these changed header paths may conflict with some compilation
-environments. Enabled by default, and may be disabled using
-<samp>--disable-canonical-system-headers</samp>.
-</p>
-</dd>
-<dt><code>--with-glibc-version=<var>major</var>.<var>minor</var></code></dt>
-<dd><p>Tell GCC that when the GNU C Library (glibc) is used on the target it
-will be version <var>major</var>.<var>minor</var> or later. Normally this can
-be detected from the C library&rsquo;s header files, but this option may be
-needed when bootstrapping a cross toolchain without the header files
-available for building the initial bootstrap compiler.
-</p>
-<p>If GCC is configured with some multilibs that use glibc and some that
-do not, this option applies only to the multilibs that use glibc.
-However, such configurations may not work well as not all the relevant
-configuration in GCC is on a per-multilib basis.
-</p></dd>
-</dl>
-
-<a name="Cross_002dCompiler_002dSpecific-Options"></a>
-<h4 class="subheading">Cross-Compiler-Specific Options</h4>
-<p>The following options only apply to building cross compilers.
-</p>
-<dl compact="compact">
-<dt><code>--with-sysroot</code></dt>
-<dt><code>--with-sysroot=<var>dir</var></code></dt>
-<dd><p>Tells GCC to consider <var>dir</var> as the root of a tree that contains
-(a subset of) the root filesystem of the target operating system.
-Target system headers, libraries and run-time object files will be
-searched for in there. More specifically, this acts as if
-<samp>--sysroot=<var>dir</var></samp> was added to the default options of the built
-compiler. The specified directory is not copied into the
-install tree, unlike the options <samp>--with-headers</samp> and
-<samp>--with-libs</samp> that this option obsoletes. The default value,
-in case <samp>--with-sysroot</samp> is not given an argument, is
-<samp>${gcc_tooldir}/sys-root</samp>. If the specified directory is a
-subdirectory of <samp>${exec_prefix}</samp>, then it will be found relative to
-the GCC binaries if the installation tree is moved.
-</p>
-<p>This option affects the system root for the compiler used to build
-target libraries (which runs on the build system) and the compiler newly
-installed with <code>make install</code>; it does not affect the compiler which is
-used to build GCC itself.
-</p>
-<p>If you specify the <samp>--with-native-system-header-dir=<var>dirname</var></samp>
-option then the compiler will search that directory within <var>dirname</var> for
-native system headers rather than the default <samp>/usr/include</samp>.
-</p>
-</dd>
-<dt><code>--with-build-sysroot</code></dt>
-<dt><code>--with-build-sysroot=<var>dir</var></code></dt>
-<dd><p>Tells GCC to consider <var>dir</var> as the system root (see
-<samp>--with-sysroot</samp>) while building target libraries, instead of
-the directory specified with <samp>--with-sysroot</samp>. This option is
-only useful when you are already using <samp>--with-sysroot</samp>. You
-can use <samp>--with-build-sysroot</samp> when you are configuring with
-<samp>--prefix</samp> set to a directory that is different from the one in
-which you are installing GCC and your target libraries.
-</p>
-<p>This option affects the system root for the compiler used to build
-target libraries (which runs on the build system); it does not affect
-the compiler which is used to build GCC itself.
-</p>
-<p>If you specify the <samp>--with-native-system-header-dir=<var>dirname</var></samp>
-option then the compiler will search that directory within <var>dirname</var> for
-native system headers rather than the default <samp>/usr/include</samp>.
-</p>
-</dd>
-<dt><code>--with-headers</code></dt>
-<dt><code>--with-headers=<var>dir</var></code></dt>
-<dd><p>Deprecated in favor of <samp>--with-sysroot</samp>.
-Specifies that target headers are available when building a cross compiler.
-The <var>dir</var> argument specifies a directory which has the target include
-files. These include files will be copied into the <samp>gcc</samp> install
-directory. <em>This option with the <var>dir</var> argument is required</em> when
-building a cross compiler, if <samp><var>prefix</var>/<var>target</var>/sys-include</samp>
-doesn&rsquo;t pre-exist. If <samp><var>prefix</var>/<var>target</var>/sys-include</samp> does
-pre-exist, the <var>dir</var> argument may be omitted. <code>fixincludes</code>
-will be run on these files to make them compatible with GCC.
-</p>
-</dd>
-<dt><code>--without-headers</code></dt>
-<dd><p>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.
-</p>
-</dd>
-<dt><code>--with-libs</code></dt>
-<dt><code>--with-libs=&quot;<var>dir1</var> <var>dir2</var> &hellip; <var>dirN</var>&quot;</code></dt>
-<dd><p>Deprecated in favor of <samp>--with-sysroot</samp>.
-Specifies a list of directories which contain the target runtime
-libraries. These libraries will be copied into the <samp>gcc</samp> install
-directory. If the directory list is omitted, this option has no
-effect.
-</p>
-</dd>
-<dt><code>--with-newlib</code></dt>
-<dd><p>Specifies that &lsquo;<samp>newlib</samp>&rsquo; is
-being used as the target C library. This causes <code>__eprintf</code> to be
-omitted from <samp>libgcc.a</samp> on the assumption that it will be provided by
-&lsquo;<samp>newlib</samp>&rsquo;.
-</p>
-</dd>
-<dt><code>--with-avrlibc</code></dt>
-<dd><p>Specifies that &lsquo;<samp>AVR-Libc</samp>&rsquo; is
-being used as the target C library. This causes float support
-functions like <code>__addsf3</code> to be omitted from <samp>libgcc.a</samp> on
-the assumption that it will be provided by <samp>libm.a</samp>. For more
-technical details, cf. <a href="http://gcc.gnu.org/PR54461">PR54461</a>.
-This option is only supported for the AVR target. It is not supported for
-RTEMS configurations, which currently use newlib. The option is
-supported since version 4.7.2 and is the default in 4.8.0 and newer.
-</p>
-</dd>
-<dt><code>--with-nds32-lib=<var>library</var></code></dt>
-<dd><p>Specifies that <var>library</var> setting is used for building <samp>libgcc.a</samp>.
-Currently, the valid <var>library</var> is &lsquo;<samp>newlib</samp>&rsquo; or &lsquo;<samp>mculib</samp>&rsquo;.
-This option is only supported for the NDS32 target.
-</p>
-</dd>
-<dt><code>--with-build-time-tools=<var>dir</var></code></dt>
-<dd><p>Specifies where to find the set of target tools (assembler, linker, etc.)
-that will be used while building GCC itself. This option can be useful
-if the directory layouts are different between the system you are building
-GCC on, and the system where you will deploy it.
-</p>
-<p>For example, on an &lsquo;<samp>ia64-hp-hpux</samp>&rsquo; system, you may have the GNU
-assembler and linker in <samp>/usr/bin</samp>, and the native tools in a
-different path, and build a toolchain that expects to find the
-native tools in <samp>/usr/bin</samp>.
-</p>
-<p>When you use this option, you should ensure that <var>dir</var> includes
-<code>ar</code>, <code>as</code>, <code>ld</code>, <code>nm</code>,
-<code>ranlib</code> and <code>strip</code> if necessary, and possibly
-<code>objdump</code>. Otherwise, GCC may use an inconsistent set of
-tools.
-</p></dd>
-</dl>
-
-<a name="Java_002dSpecific-Options"></a>
-<h4 class="subheading">Java-Specific Options</h4>
-
-<p>The following option applies to the build of the Java front end.
-</p>
-<dl compact="compact">
-<dt><code>--disable-libgcj</code></dt>
-<dd><p>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&rsquo;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&rsquo;re known to not work on
-the target platform. If GCJ is enabled but &lsquo;<samp>libgcj</samp>&rsquo; isn&rsquo;t built, you
-may need to port it; in this case, before modifying the top-level
-<samp>configure.in</samp> so that &lsquo;<samp>libgcj</samp>&rsquo; is enabled by default on this platform,
-you may use <samp>--enable-libgcj</samp> to override the default.
-</p>
-</dd>
-</dl>
-
-<p>The following options apply to building &lsquo;<samp>libgcj</samp>&rsquo;.
-</p>
-<a name="General-Options"></a>
-<h4 class="subsubheading">General Options</h4>
-
-<dl compact="compact">
-<dt><code>--enable-java-maintainer-mode</code></dt>
-<dd><p>By default the &lsquo;<samp>libjava</samp>&rsquo; build will not attempt to compile the
-<samp>.java</samp> source files to <samp>.class</samp>. Instead, it will use the
-<samp>.class</samp> files from the source tree. If you use this option you
-must have executables named <code>ecj1</code> and <code>gjavah</code> in your path
-for use by the build. You must use this option if you intend to
-modify any <samp>.java</samp> files in <samp>libjava</samp>.
-</p>
-</dd>
-<dt><code>--with-java-home=<var>dirname</var></code></dt>
-<dd><p>This &lsquo;<samp>libjava</samp>&rsquo; option overrides the default value of the
-&lsquo;<samp>java.home</samp>&rsquo; system property. It is also used to set
-&lsquo;<samp>sun.boot.class.path</samp>&rsquo; to <samp><var>dirname</var>/lib/rt.jar</samp>. By
-default &lsquo;<samp>java.home</samp>&rsquo; is set to <samp><var>prefix</var></samp> and
-&lsquo;<samp>sun.boot.class.path</samp>&rsquo; to
-<samp><var>datadir</var>/java/libgcj-<var>version</var>.jar</samp>.
-</p>
-</dd>
-<dt><code>--with-ecj-jar=<var>filename</var></code></dt>
-<dd><p>This option can be used to specify the location of an external jar
-file containing the Eclipse Java compiler. A specially modified
-version of this compiler is used by <code>gcj</code> to parse
-<samp>.java</samp> source files. If this option is given, the
-&lsquo;<samp>libjava</samp>&rsquo; build will create and install an <samp>ecj1</samp> executable
-which uses this jar file at runtime.
-</p>
-<p>If this option is not given, but an <samp>ecj.jar</samp> file is found in
-the topmost source tree at configure time, then the &lsquo;<samp>libgcj</samp>&rsquo;
-build will create and install <samp>ecj1</samp>, and will also install the
-discovered <samp>ecj.jar</samp> into a suitable place in the install tree.
-</p>
-<p>If <samp>ecj1</samp> is not installed, then the user will have to supply one
-on his path in order for <code>gcj</code> to properly parse <samp>.java</samp>
-source files. A suitable jar is available from
-<a href="ftp://sourceware.org/pub/java/">ftp://sourceware.org/pub/java/</a>.
-</p>
-</dd>
-<dt><code>--disable-getenv-properties</code></dt>
-<dd><p>Don&rsquo;t set system properties from <code>GCJ_PROPERTIES</code>.
-</p>
-</dd>
-<dt><code>--enable-hash-synchronization</code></dt>
-<dd><p>Use a global hash table for monitor locks. Ordinarily,
-&lsquo;<samp>libgcj</samp>&rsquo;&rsquo;s &lsquo;<samp>configure</samp>&rsquo; script automatically makes
-the correct choice for this option for your platform. Only use
-this if you know you need the library to be configured differently.
-</p>
-</dd>
-<dt><code>--enable-interpreter</code></dt>
-<dd><p>Enable the Java interpreter. The interpreter is automatically
-enabled by default on all platforms that support it. This option
-is really only useful if you want to disable the interpreter
-(using <samp>--disable-interpreter</samp>).
-</p>
-</dd>
-<dt><code>--disable-java-net</code></dt>
-<dd><p>Disable java.net. This disables the native part of java.net only,
-using non-functional stubs for native method implementations.
-</p>
-</dd>
-<dt><code>--disable-jvmpi</code></dt>
-<dd><p>Disable JVMPI support.
-</p>
-</dd>
-<dt><code>--disable-libgcj-bc</code></dt>
-<dd><p>Disable BC ABI compilation of certain parts of libgcj. By default,
-some portions of libgcj are compiled with <samp>-findirect-dispatch</samp>
-and <samp>-fno-indirect-classes</samp>, allowing them to be overridden at
-run-time.
-</p>
-<p>If <samp>--disable-libgcj-bc</samp> is specified, libgcj is built without
-these options. This allows the compile-time linker to resolve
-dependencies when statically linking to libgcj. However it makes it
-impossible to override the affected portions of libgcj at run-time.
-</p>
-</dd>
-<dt><code>--enable-reduced-reflection</code></dt>
-<dd><p>Build most of libgcj with <samp>-freduced-reflection</samp>. This reduces
-the size of libgcj at the expense of not being able to do accurate
-reflection on the classes it contains. This option is safe if you
-know that code using libgcj will never use reflection on the standard
-runtime classes in libgcj (including using serialization, RMI or CORBA).
-</p>
-</dd>
-<dt><code>--with-ecos</code></dt>
-<dd><p>Enable runtime eCos target support.
-</p>
-</dd>
-<dt><code>--without-libffi</code></dt>
-<dd><p>Don&rsquo;t use &lsquo;<samp>libffi</samp>&rsquo;. This will disable the interpreter and JNI
-support as well, as these require &lsquo;<samp>libffi</samp>&rsquo; to work.
-</p>
-</dd>
-<dt><code>--enable-libgcj-debug</code></dt>
-<dd><p>Enable runtime debugging code.
-</p>
-</dd>
-<dt><code>--enable-libgcj-multifile</code></dt>
-<dd><p>If specified, causes all <samp>.java</samp> source files to be
-compiled into <samp>.class</samp> files in one invocation of
-&lsquo;<samp>gcj</samp>&rsquo;. This can speed up build time, but is more
-resource-intensive. If this option is unspecified or
-disabled, &lsquo;<samp>gcj</samp>&rsquo; is invoked once for each <samp>.java</samp>
-file to compile into a <samp>.class</samp> file.
-</p>
-</dd>
-<dt><code>--with-libiconv-prefix=DIR</code></dt>
-<dd><p>Search for libiconv in <samp>DIR/include</samp> and <samp>DIR/lib</samp>.
-</p>
-</dd>
-<dt><code>--enable-sjlj-exceptions</code></dt>
-<dd><p>Force use of the <code>setjmp</code>/<code>longjmp</code>-based scheme for exceptions.
-&lsquo;<samp>configure</samp>&rsquo; ordinarily picks the correct value based on the platform.
-Only use this option if you are sure you need a different setting.
-</p>
-</dd>
-<dt><code>--with-system-zlib</code></dt>
-<dd><p>Use installed &lsquo;<samp>zlib</samp>&rsquo; rather than that included with GCC.
-</p>
-</dd>
-<dt><code>--with-win32-nlsapi=ansi, unicows or unicode</code></dt>
-<dd><p>Indicates how MinGW &lsquo;<samp>libgcj</samp>&rsquo; translates between UNICODE
-characters and the Win32 API.
-</p>
-</dd>
-<dt><code>--enable-java-home</code></dt>
-<dd><p>If enabled, this creates a JPackage compatible SDK environment during install.
-Note that if &ndash;enable-java-home is used, &ndash;with-arch-directory=ARCH must also
-be specified.
-</p>
-</dd>
-<dt><code>--with-arch-directory=ARCH</code></dt>
-<dd><p>Specifies the name to use for the <samp>jre/lib/ARCH</samp> directory in the SDK
-environment created when &ndash;enable-java-home is passed. Typical names for this
-directory include i386, amd64, ia64, etc.
-</p>
-</dd>
-<dt><code>--with-os-directory=DIR</code></dt>
-<dd><p>Specifies the OS directory for the SDK include directory. This is set to auto
-detect, and is typically &rsquo;linux&rsquo;.
-</p>
-</dd>
-<dt><code>--with-origin-name=NAME</code></dt>
-<dd><p>Specifies the JPackage origin name. This defaults to the &rsquo;gcj&rsquo; in
-java-1.5.0-gcj.
-</p>
-</dd>
-<dt><code>--with-arch-suffix=SUFFIX</code></dt>
-<dd><p>Specifies the suffix for the sdk directory. Defaults to the empty string.
-Examples include &rsquo;.x86_64&rsquo; in &rsquo;java-1.5.0-gcj-1.5.0.0.x86_64&rsquo;.
-</p>
-</dd>
-<dt><code>--with-jvm-root-dir=DIR</code></dt>
-<dd><p>Specifies where to install the SDK. Default is $(prefix)/lib/jvm.
-</p>
-</dd>
-<dt><code>--with-jvm-jar-dir=DIR</code></dt>
-<dd><p>Specifies where to install jars. Default is $(prefix)/lib/jvm-exports.
-</p>
-</dd>
-<dt><code>--with-python-dir=DIR</code></dt>
-<dd><p>Specifies where to install the Python modules used for aot-compile. DIR should
-not include the prefix used in installation. For example, if the Python modules
-are to be installed in /usr/lib/python2.5/site-packages, then
-&ndash;with-python-dir=/lib/python2.5/site-packages should be passed. If this is
-not specified, then the Python modules are installed in $(prefix)/share/python.
-</p>
-</dd>
-<dt><code>--enable-aot-compile-rpm</code></dt>
-<dd><p>Adds aot-compile-rpm to the list of installed scripts.
-</p>
-</dd>
-<dt><code>--enable-browser-plugin</code></dt>
-<dd><p>Build the gcjwebplugin web browser plugin.
-</p>
-</dd>
-<dt><code>--enable-static-libjava</code></dt>
-<dd><p>Build static libraries in libjava. The default is to only build shared
-libraries.
-</p>
-<dl compact="compact">
-<dt><code>ansi</code></dt>
-<dd><p>Use the single-byte <code>char</code> and the Win32 A functions natively,
-translating to and from UNICODE when using these functions. If
-unspecified, this is the default.
-</p>
-</dd>
-<dt><code>unicows</code></dt>
-<dd><p>Use the <code>WCHAR</code> and Win32 W functions natively. Adds
-<code>-lunicows</code> to <samp>libgcj.spec</samp> to link with &lsquo;<samp>libunicows</samp>&rsquo;.
-<samp>unicows.dll</samp> needs to be deployed on Microsoft Windows 9X machines
-running built executables. <samp>libunicows.a</samp>, an open-source
-import library around Microsoft&rsquo;s <code>unicows.dll</code>, is obtained from
-<a href="http://libunicows.sourceforge.net/">http://libunicows.sourceforge.net/</a>, which also gives details
-on getting <samp>unicows.dll</samp> from Microsoft.
-</p>
-</dd>
-<dt><code>unicode</code></dt>
-<dd><p>Use the <code>WCHAR</code> and Win32 W functions natively. Does <em>not</em>
-add <code>-lunicows</code> to <samp>libgcj.spec</samp>. The built executables will
-only run on Microsoft Windows NT and above.
-</p></dd>
-</dl>
-</dd>
-</dl>
-
-<a name="AWT_002dSpecific-Options"></a>
-<h4 class="subsubheading">AWT-Specific Options</h4>
-
-<dl compact="compact">
-<dt><code>--with-x</code></dt>
-<dd><p>Use the X Window System.
-</p>
-</dd>
-<dt><code>--enable-java-awt=PEER(S)</code></dt>
-<dd><p>Specifies the AWT peer library or libraries to build alongside
-&lsquo;<samp>libgcj</samp>&rsquo;. If this option is unspecified or disabled, AWT
-will be non-functional. Current valid values are <samp>gtk</samp> and
-<samp>xlib</samp>. Multiple libraries should be separated by a
-comma (i.e. <samp>--enable-java-awt=gtk,xlib</samp>).
-</p>
-</dd>
-<dt><code>--enable-gtk-cairo</code></dt>
-<dd><p>Build the cairo Graphics2D implementation on GTK.
-</p>
-</dd>
-<dt><code>--enable-java-gc=TYPE</code></dt>
-<dd><p>Choose garbage collector. Defaults to <samp>boehm</samp> if unspecified.
-</p>
-</dd>
-<dt><code>--disable-gtktest</code></dt>
-<dd><p>Do not try to compile and run a test GTK+ program.
-</p>
-</dd>
-<dt><code>--disable-glibtest</code></dt>
-<dd><p>Do not try to compile and run a test GLIB program.
-</p>
-</dd>
-<dt><code>--with-libart-prefix=PFX</code></dt>
-<dd><p>Prefix where libart is installed (optional).
-</p>
-</dd>
-<dt><code>--with-libart-exec-prefix=PFX</code></dt>
-<dd><p>Exec prefix where libart is installed (optional).
-</p>
-</dd>
-<dt><code>--disable-libarttest</code></dt>
-<dd><p>Do not try to compile and run a test libart program.
-</p>
-</dd>
-</dl>
-
-<a name="Overriding-configure-test-results"></a>
-<h4 class="subsubheading">Overriding <code>configure</code> test results</h4>
-
-<p>Sometimes, it might be necessary to override the result of some
-<code>configure</code> test, for example in order to ease porting to a new
-system or work around a bug in a test. The toplevel <code>configure</code>
-script provides three variables for this:
-</p>
-<dl compact="compact">
-<dt><code>build_configargs</code></dt>
-<dd><a name="index-build_005fconfigargs"></a>
-<p>The contents of this variable is passed to all build <code>configure</code>
-scripts.
-</p>
-</dd>
-<dt><code>host_configargs</code></dt>
-<dd><a name="index-host_005fconfigargs"></a>
-<p>The contents of this variable is passed to all host <code>configure</code>
-scripts.
-</p>
-</dd>
-<dt><code>target_configargs</code></dt>
-<dd><a name="index-target_005fconfigargs"></a>
-<p>The contents of this variable is passed to all target <code>configure</code>
-scripts.
-</p>
-</dd>
-</dl>
-
-<p>In order to avoid shell and <code>make</code> quoting issues for complex
-overrides, you can pass a setting for <code>CONFIG_SITE</code> and set
-variables in the site file.
-</p>
-<hr />
-<p><p><a href="./index.html">Return to the GCC Installation page</a>
-</p>
-
-
-
-
-
-
-
-
-
-
-
-</body>
-</html>
diff --git a/gcc-4.9/INSTALL/download.html b/gcc-4.9/INSTALL/download.html
deleted file mode 100644
index d64706e..0000000
--- a/gcc-4.9/INSTALL/download.html
+++ /dev/null
@@ -1,132 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<!-- Copyright (C) 1988-2014 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.3 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. -->
-<!-- Created by GNU Texinfo 5.1, http://www.gnu.org/software/texinfo/ -->
-<head>
-<title>Installing GCC</title>
-
-<meta name="description" content="Installing GCC">
-<meta name="keywords" content="Installing GCC">
-<meta name="resource-type" content="document">
-<meta name="distribution" content="global">
-<meta name="Generator" content="makeinfo">
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<style type="text/css">
-<!--
-a.summary-letter {text-decoration: none}
-blockquote.smallquotation {font-size: smaller}
-div.display {margin-left: 3.2em}
-div.example {margin-left: 3.2em}
-div.indentedblock {margin-left: 3.2em}
-div.lisp {margin-left: 3.2em}
-div.smalldisplay {margin-left: 3.2em}
-div.smallexample {margin-left: 3.2em}
-div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
-div.smalllisp {margin-left: 3.2em}
-kbd {font-style:oblique}
-pre.display {font-family: inherit}
-pre.format {font-family: inherit}
-pre.menu-comment {font-family: serif}
-pre.menu-preformatted {font-family: serif}
-pre.smalldisplay {font-family: inherit; font-size: smaller}
-pre.smallexample {font-size: smaller}
-pre.smallformat {font-family: inherit; font-size: smaller}
-pre.smalllisp {font-size: smaller}
-span.nocodebreak {white-space:nowrap}
-span.nolinebreak {white-space:nowrap}
-span.roman {font-family:serif; font-weight:normal}
-span.sansserif {font-family:sans-serif; font-weight:normal}
-ul.no-bullet {list-style: none}
--->
-</style>
-
-
-</head>
-
-<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
-<h1 class="settitle" align="center">Installing GCC</h1>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<a name="index-Downloading-GCC"></a>
-<a name="index-Downloading-the-Source"></a>
-
-<p>GCC is distributed via <a href="http://gcc.gnu.org/svn.html">SVN</a> and FTP
-tarballs compressed with <code>gzip</code> or
-<code>bzip2</code>.
-</p>
-<p>Please refer to the <a href="http://gcc.gnu.org/releases.html">releases web page</a>
-for information on how to obtain GCC.
-</p>
-<p>The source distribution includes the C, C++, Objective-C, Fortran, Java,
-and Ada (in the case of GCC 3.1 and later) compilers, as well as
-runtime libraries for C++, Objective-C, Fortran, and Java.
-For previous versions these were downloadable as separate components such
-as the core GCC distribution, which included the C language front end and
-shared components, and language-specific distributions including the
-language front end and the language runtime (where appropriate).
-</p>
-<p>If you also intend to build binutils (either to upgrade an existing
-installation or for use in place of the corresponding tools of your
-OS), unpack the binutils distribution either in the same directory or
-a separate one. In the latter case, add symbolic links to any
-components of the binutils you intend to build alongside the compiler
-(<samp>bfd</samp>, <samp>binutils</samp>, <samp>gas</samp>, <samp>gprof</samp>, <samp>ld</samp>,
-<samp>opcodes</samp>, &hellip;) to the directory containing the GCC sources.
-</p>
-<p>Likewise the GMP, MPFR and MPC libraries can be automatically built
-together with GCC. Unpack the GMP, MPFR and/or MPC source
-distributions in the directory containing the GCC sources and rename
-their directories to <samp>gmp</samp>, <samp>mpfr</samp> and <samp>mpc</samp>,
-respectively (or use symbolic links with the same name).
-</p>
-<hr />
-<p><p><a href="./index.html">Return to the GCC Installation page</a>
-</p>
-
-
-
-
-
-
-
-
-
-
-
-
-</body>
-</html>
diff --git a/gcc-4.9/INSTALL/finalinstall.html b/gcc-4.9/INSTALL/finalinstall.html
deleted file mode 100644
index 645635a..0000000
--- a/gcc-4.9/INSTALL/finalinstall.html
+++ /dev/null
@@ -1,227 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<!-- Copyright (C) 1988-2014 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.3 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. -->
-<!-- Created by GNU Texinfo 5.1, http://www.gnu.org/software/texinfo/ -->
-<head>
-<title>Installing GCC</title>
-
-<meta name="description" content="Installing GCC">
-<meta name="keywords" content="Installing GCC">
-<meta name="resource-type" content="document">
-<meta name="distribution" content="global">
-<meta name="Generator" content="makeinfo">
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<style type="text/css">
-<!--
-a.summary-letter {text-decoration: none}
-blockquote.smallquotation {font-size: smaller}
-div.display {margin-left: 3.2em}
-div.example {margin-left: 3.2em}
-div.indentedblock {margin-left: 3.2em}
-div.lisp {margin-left: 3.2em}
-div.smalldisplay {margin-left: 3.2em}
-div.smallexample {margin-left: 3.2em}
-div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
-div.smalllisp {margin-left: 3.2em}
-kbd {font-style:oblique}
-pre.display {font-family: inherit}
-pre.format {font-family: inherit}
-pre.menu-comment {font-family: serif}
-pre.menu-preformatted {font-family: serif}
-pre.smalldisplay {font-family: inherit; font-size: smaller}
-pre.smallexample {font-size: smaller}
-pre.smallformat {font-family: inherit; font-size: smaller}
-pre.smalllisp {font-size: smaller}
-span.nocodebreak {white-space:nowrap}
-span.nolinebreak {white-space:nowrap}
-span.roman {font-family:serif; font-weight:normal}
-span.sansserif {font-family:sans-serif; font-weight:normal}
-ul.no-bullet {list-style: none}
--->
-</style>
-
-
-</head>
-
-<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
-<h1 class="settitle" align="center">Installing GCC</h1>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<p>Now that GCC has been built (and optionally tested), you can install it with
-</p><div class="smallexample">
-<pre class="smallexample">cd <var>objdir</var> &amp;&amp; make install
-</pre></div>
-
-<p>We strongly recommend to install into a target directory where there is
-no previous version of GCC present. Also, the GNAT runtime should not
-be stripped, as this would break certain features of the debugger that
-depend on this debugging information (catching Ada exceptions for
-instance).
-</p>
-<p>That step completes the installation of GCC; user level binaries can
-be found in <samp><var>prefix</var>/bin</samp> where <var>prefix</var> is the value
-you specified with the <samp>--prefix</samp> to configure (or
-<samp>/usr/local</samp> by default). (If you specified <samp>--bindir</samp>,
-that directory will be used instead; otherwise, if you specified
-<samp>--exec-prefix</samp>, <samp><var>exec-prefix</var>/bin</samp> will be used.)
-Headers for the C++ and Java libraries are installed in
-<samp><var>prefix</var>/include</samp>; libraries in <samp><var>libdir</var></samp>
-(normally <samp><var>prefix</var>/lib</samp>); internal parts of the compiler in
-<samp><var>libdir</var>/gcc</samp> and <samp><var>libexecdir</var>/gcc</samp>; documentation
-in info format in <samp><var>infodir</var></samp> (normally
-<samp><var>prefix</var>/info</samp>).
-</p>
-<p>When installing cross-compilers, GCC&rsquo;s executables
-are not only installed into <samp><var>bindir</var></samp>, that
-is, <samp><var>exec-prefix</var>/bin</samp>, but additionally into
-<samp><var>exec-prefix</var>/<var>target-alias</var>/bin</samp>, if that directory
-exists. Typically, such <em>tooldirs</em> hold target-specific
-binutils, including assembler and linker.
-</p>
-<p>Installation into a temporary staging area or into a <code>chroot</code>
-jail can be achieved with the command
-</p>
-<div class="smallexample">
-<pre class="smallexample">make DESTDIR=<var>path-to-rootdir</var> install
-</pre></div>
-
-<p>where <var>path-to-rootdir</var> is the absolute path of
-a directory relative to which all installation paths will be
-interpreted. Note that the directory specified by <code>DESTDIR</code>
-need not exist yet; it will be created if necessary.
-</p>
-<p>There is a subtle point with tooldirs and <code>DESTDIR</code>:
-If you relocate a cross-compiler installation with
-e.g. &lsquo;<samp>DESTDIR=<var>rootdir</var></samp>&rsquo;, then the directory
-<samp><var>rootdir</var>/<var>exec-prefix</var>/<var>target-alias</var>/bin</samp> will
-be filled with duplicated GCC executables only if it already exists,
-it will not be created otherwise. This is regarded as a feature,
-not as a bug, because it gives slightly more control to the packagers
-using the <code>DESTDIR</code> feature.
-</p>
-<p>You can install stripped programs and libraries with
-</p>
-<div class="smallexample">
-<pre class="smallexample">make install-strip
-</pre></div>
-
-<p>If you are bootstrapping a released version of GCC then please
-quickly review the build status page for your release, available from
-<a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>.
-If your system is not listed for the version of GCC that you built,
-send a note to
-<a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a> indicating
-that you successfully built and installed GCC.
-Include the following information:
-</p>
-<ul>
-<li> Output from running <samp><var>srcdir</var>/config.guess</samp>. Do not send
-that file itself, just the one-line output from running it.
-
-</li><li> The output of &lsquo;<samp>gcc -v</samp>&rsquo; for your newly installed <code>gcc</code>.
-This tells us which version of GCC you built and the options you passed to
-configure.
-
-</li><li> Whether you enabled all languages or a subset of them. If you used a
-full distribution then this information is part of the configure
-options in the output of &lsquo;<samp>gcc -v</samp>&rsquo;, but if you downloaded the
-&ldquo;core&rdquo; compiler plus additional front ends then it isn&rsquo;t apparent
-which ones you built unless you tell us about it.
-
-</li><li> If the build was for GNU/Linux, also include:
-<ul>
-<li> The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
-this information should be available from <samp>/etc/issue</samp>.
-
-</li><li> The version of the Linux kernel, available from &lsquo;<samp>uname --version</samp>&rsquo;
-or &lsquo;<samp>uname -a</samp>&rsquo;.
-
-</li><li> The version of glibc you used; for RPM-based systems like Red Hat,
-Mandrake, and SuSE type &lsquo;<samp>rpm -q glibc</samp>&rsquo; to get the glibc version,
-and on systems like Debian and Progeny use &lsquo;<samp>dpkg -l libc6</samp>&rsquo;.
-</li></ul>
-<p>For other systems, you can include similar information if you think it is
-relevant.
-</p>
-</li><li> Any other information that you think would be useful to people building
-GCC on the same configuration. The new entry in the build status list
-will include a link to the archived copy of your message.
-</li></ul>
-
-<p>We&rsquo;d also like to know if the
-<a href="specific.html">host/target specific installation notes</a>
-didn&rsquo;t include your host/target information or if that information is
-incomplete or out of date. Send a note to
-<a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a> detailing how the information should be changed.
-</p>
-<p>If you find a bug, please report it following the
-<a href="../bugs/">bug reporting guidelines</a>.
-</p>
-<p>If you want to print the GCC manuals, do &lsquo;<samp>cd <var>objdir</var>; make
-dvi</samp>&rsquo;. You will need to have <code>texi2dvi</code> (version at least 4.7)
-and TeX installed. This creates a number of <samp>.dvi</samp> files in
-subdirectories of <samp><var>objdir</var></samp>; these may be converted for
-printing with programs such as <code>dvips</code>. Alternately, by using
-&lsquo;<samp>make pdf</samp>&rsquo; in place of &lsquo;<samp>make dvi</samp>&rsquo;, you can create documentation
-in the form of <samp>.pdf</samp> files; this requires <code>texi2pdf</code>, which
-is included with Texinfo version 4.8 and later. You can also
-<a href="http://shop.fsf.org/">buy printed manuals from the
-Free Software Foundation</a>, though such manuals may not be for the most
-recent version of GCC.
-</p>
-<p>If you would like to generate online HTML documentation, do &lsquo;<samp>cd
-<var>objdir</var>; make html</samp>&rsquo; and HTML will be generated for the gcc manuals in
-<samp><var>objdir</var>/gcc/HTML</samp>.
-</p>
-<hr />
-<p><p><a href="./index.html">Return to the GCC Installation page</a>
-</p>
-
-
-
-
-
-
-
-
-</body>
-</html>
diff --git a/gcc-4.9/INSTALL/gfdl.html b/gcc-4.9/INSTALL/gfdl.html
deleted file mode 100644
index 10dafce..0000000
--- a/gcc-4.9/INSTALL/gfdl.html
+++ /dev/null
@@ -1,571 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<!-- Copyright (C) 1988-2014 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.3 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. -->
-<!-- Created by GNU Texinfo 5.1, http://www.gnu.org/software/texinfo/ -->
-<head>
-<title>Installing GCC</title>
-
-<meta name="description" content="Installing GCC">
-<meta name="keywords" content="Installing GCC">
-<meta name="resource-type" content="document">
-<meta name="distribution" content="global">
-<meta name="Generator" content="makeinfo">
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<style type="text/css">
-<!--
-a.summary-letter {text-decoration: none}
-blockquote.smallquotation {font-size: smaller}
-div.display {margin-left: 3.2em}
-div.example {margin-left: 3.2em}
-div.indentedblock {margin-left: 3.2em}
-div.lisp {margin-left: 3.2em}
-div.smalldisplay {margin-left: 3.2em}
-div.smallexample {margin-left: 3.2em}
-div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
-div.smalllisp {margin-left: 3.2em}
-kbd {font-style:oblique}
-pre.display {font-family: inherit}
-pre.format {font-family: inherit}
-pre.menu-comment {font-family: serif}
-pre.menu-preformatted {font-family: serif}
-pre.smalldisplay {font-family: inherit; font-size: smaller}
-pre.smallexample {font-size: smaller}
-pre.smallformat {font-family: inherit; font-size: smaller}
-pre.smalllisp {font-size: smaller}
-span.nocodebreak {white-space:nowrap}
-span.nolinebreak {white-space:nowrap}
-span.roman {font-family:serif; font-weight:normal}
-span.sansserif {font-family:sans-serif; font-weight:normal}
-ul.no-bullet {list-style: none}
--->
-</style>
-
-
-</head>
-
-<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
-<h1 class="settitle" align="center">Installing GCC</h1>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<h1 align="center">Installing GCC: GNU Free Documentation License</h1>
-<a name="index-FDL_002c-GNU-Free-Documentation-License"></a>
-<div align="center">Version 1.3, 3 November 2008
-</div>
-<div class="display">
-<pre class="display">Copyright &copy; 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
-<a href="http://fsf.org/">http://fsf.org/</a>
-
-Everyone is permitted to copy and distribute verbatim copies
-of this license document, but changing it is not allowed.
-</pre></div>
-
-<ol>
-<li> PREAMBLE
-
-<p>The purpose of this License is to make a manual, textbook, or other
-functional and useful document <em>free</em> in the sense of freedom: to
-assure everyone the effective freedom to copy and redistribute it,
-with or without modifying it, either commercially or noncommercially.
-Secondarily, this License preserves for the author and publisher a way
-to get credit for their work, while not being considered responsible
-for modifications made by others.
-</p>
-<p>This License is a kind of &ldquo;copyleft&rdquo;, which means that derivative
-works of the document must themselves be free in the same sense. It
-complements the GNU General Public License, which is a copyleft
-license designed for free software.
-</p>
-<p>We have designed this License in order to use it for manuals for free
-software, because free software needs free documentation: a free
-program should come with manuals providing the same freedoms that the
-software does. But this License is not limited to software manuals;
-it can be used for any textual work, regardless of subject matter or
-whether it is published as a printed book. We recommend this License
-principally for works whose purpose is instruction or reference.
-</p>
-</li><li> APPLICABILITY AND DEFINITIONS
-
-<p>This License applies to any manual or other work, in any medium, that
-contains a notice placed by the copyright holder saying it can be
-distributed under the terms of this License. Such a notice grants a
-world-wide, royalty-free license, unlimited in duration, to use that
-work under the conditions stated herein. The &ldquo;Document&rdquo;, below,
-refers to any such manual or work. Any member of the public is a
-licensee, and is addressed as &ldquo;you&rdquo;. You accept the license if you
-copy, modify or distribute the work in a way requiring permission
-under copyright law.
-</p>
-<p>A &ldquo;Modified Version&rdquo; of the Document means any work containing the
-Document or a portion of it, either copied verbatim, or with
-modifications and/or translated into another language.
-</p>
-<p>A &ldquo;Secondary Section&rdquo; is a named appendix or a front-matter section
-of the Document that deals exclusively with the relationship of the
-publishers or authors of the Document to the Document&rsquo;s overall
-subject (or to related matters) and contains nothing that could fall
-directly within that overall subject. (Thus, if the Document is in
-part a textbook of mathematics, a Secondary Section may not explain
-any mathematics.) The relationship could be a matter of historical
-connection with the subject or with related matters, or of legal,
-commercial, philosophical, ethical or political position regarding
-them.
-</p>
-<p>The &ldquo;Invariant Sections&rdquo; are certain Secondary Sections whose titles
-are designated, as being those of Invariant Sections, in the notice
-that says that the Document is released under this License. If a
-section does not fit the above definition of Secondary then it is not
-allowed to be designated as Invariant. The Document may contain zero
-Invariant Sections. If the Document does not identify any Invariant
-Sections then there are none.
-</p>
-<p>The &ldquo;Cover Texts&rdquo; are certain short passages of text that are listed,
-as Front-Cover Texts or Back-Cover Texts, in the notice that says that
-the Document is released under this License. A Front-Cover Text may
-be at most 5 words, and a Back-Cover Text may be at most 25 words.
-</p>
-<p>A &ldquo;Transparent&rdquo; copy of the Document means a machine-readable copy,
-represented in a format whose specification is available to the
-general public, that is suitable for revising the document
-straightforwardly with generic text editors or (for images composed of
-pixels) generic paint programs or (for drawings) some widely available
-drawing editor, and that is suitable for input to text formatters or
-for automatic translation to a variety of formats suitable for input
-to text formatters. A copy made in an otherwise Transparent file
-format whose markup, or absence of markup, has been arranged to thwart
-or discourage subsequent modification by readers is not Transparent.
-An image format is not Transparent if used for any substantial amount
-of text. A copy that is not &ldquo;Transparent&rdquo; is called &ldquo;Opaque&rdquo;.
-</p>
-<p>Examples of suitable formats for Transparent copies include plain
-<small>ASCII</small> without markup, Texinfo input format, LaTeX input
-format, <acronym>SGML</acronym> or <acronym>XML</acronym> using a publicly available
-<acronym>DTD</acronym>, and standard-conforming simple <acronym>HTML</acronym>,
-PostScript or <acronym>PDF</acronym> designed for human modification. Examples
-of transparent image formats include <acronym>PNG</acronym>, <acronym>XCF</acronym> and
-<acronym>JPG</acronym>. Opaque formats include proprietary formats that can be
-read and edited only by proprietary word processors, <acronym>SGML</acronym> or
-<acronym>XML</acronym> for which the <acronym>DTD</acronym> and/or processing tools are
-not generally available, and the machine-generated <acronym>HTML</acronym>,
-PostScript or <acronym>PDF</acronym> produced by some word processors for
-output purposes only.
-</p>
-<p>The &ldquo;Title Page&rdquo; means, for a printed book, the title page itself,
-plus such following pages as are needed to hold, legibly, the material
-this License requires to appear in the title page. For works in
-formats which do not have any title page as such, &ldquo;Title Page&rdquo; means
-the text near the most prominent appearance of the work&rsquo;s title,
-preceding the beginning of the body of the text.
-</p>
-<p>The &ldquo;publisher&rdquo; means any person or entity that distributes copies
-of the Document to the public.
-</p>
-<p>A section &ldquo;Entitled XYZ&rdquo; means a named subunit of the Document whose
-title either is precisely XYZ or contains XYZ in parentheses following
-text that translates XYZ in another language. (Here XYZ stands for a
-specific section name mentioned below, such as &ldquo;Acknowledgements&rdquo;,
-&ldquo;Dedications&rdquo;, &ldquo;Endorsements&rdquo;, or &ldquo;History&rdquo;.) To &ldquo;Preserve the Title&rdquo;
-of such a section when you modify the Document means that it remains a
-section &ldquo;Entitled XYZ&rdquo; according to this definition.
-</p>
-<p>The Document may include Warranty Disclaimers next to the notice which
-states that this License applies to the Document. These Warranty
-Disclaimers are considered to be included by reference in this
-License, but only as regards disclaiming warranties: any other
-implication that these Warranty Disclaimers may have is void and has
-no effect on the meaning of this License.
-</p>
-</li><li> VERBATIM COPYING
-
-<p>You may copy and distribute the Document in any medium, either
-commercially or noncommercially, provided that this License, the
-copyright notices, and the license notice saying this License applies
-to the Document are reproduced in all copies, and that you add no other
-conditions whatsoever to those of this License. You may not use
-technical measures to obstruct or control the reading or further
-copying of the copies you make or distribute. However, you may accept
-compensation in exchange for copies. If you distribute a large enough
-number of copies you must also follow the conditions in section 3.
-</p>
-<p>You may also lend copies, under the same conditions stated above, and
-you may publicly display copies.
-</p>
-</li><li> COPYING IN QUANTITY
-
-<p>If you publish printed copies (or copies in media that commonly have
-printed covers) of the Document, numbering more than 100, and the
-Document&rsquo;s license notice requires Cover Texts, you must enclose the
-copies in covers that carry, clearly and legibly, all these Cover
-Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
-the back cover. Both covers must also clearly and legibly identify
-you as the publisher of these copies. The front cover must present
-the full title with all words of the title equally prominent and
-visible. You may add other material on the covers in addition.
-Copying with changes limited to the covers, as long as they preserve
-the title of the Document and satisfy these conditions, can be treated
-as verbatim copying in other respects.
-</p>
-<p>If the required texts for either cover are too voluminous to fit
-legibly, you should put the first ones listed (as many as fit
-reasonably) on the actual cover, and continue the rest onto adjacent
-pages.
-</p>
-<p>If you publish or distribute Opaque copies of the Document numbering
-more than 100, you must either include a machine-readable Transparent
-copy along with each Opaque copy, or state in or with each Opaque copy
-a computer-network location from which the general network-using
-public has access to download using public-standard network protocols
-a complete Transparent copy of the Document, free of added material.
-If you use the latter option, you must take reasonably prudent steps,
-when you begin distribution of Opaque copies in quantity, to ensure
-that this Transparent copy will remain thus accessible at the stated
-location until at least one year after the last time you distribute an
-Opaque copy (directly or through your agents or retailers) of that
-edition to the public.
-</p>
-<p>It is requested, but not required, that you contact the authors of the
-Document well before redistributing any large number of copies, to give
-them a chance to provide you with an updated version of the Document.
-</p>
-</li><li> MODIFICATIONS
-
-<p>You may copy and distribute a Modified Version of the Document under
-the conditions of sections 2 and 3 above, provided that you release
-the Modified Version under precisely this License, with the Modified
-Version filling the role of the Document, thus licensing distribution
-and modification of the Modified Version to whoever possesses a copy
-of it. In addition, you must do these things in the Modified Version:
-</p>
-<ol>
-<li> Use in the Title Page (and on the covers, if any) a title distinct
-from that of the Document, and from those of previous versions
-(which should, if there were any, be listed in the History section
-of the Document). You may use the same title as a previous version
-if the original publisher of that version gives permission.
-
-</li><li> List on the Title Page, as authors, one or more persons or entities
-responsible for authorship of the modifications in the Modified
-Version, together with at least five of the principal authors of the
-Document (all of its principal authors, if it has fewer than five),
-unless they release you from this requirement.
-
-</li><li> State on the Title page the name of the publisher of the
-Modified Version, as the publisher.
-
-</li><li> Preserve all the copyright notices of the Document.
-
-</li><li> Add an appropriate copyright notice for your modifications
-adjacent to the other copyright notices.
-
-</li><li> Include, immediately after the copyright notices, a license notice
-giving the public permission to use the Modified Version under the
-terms of this License, in the form shown in the Addendum below.
-
-</li><li> Preserve in that license notice the full lists of Invariant Sections
-and required Cover Texts given in the Document&rsquo;s license notice.
-
-</li><li> Include an unaltered copy of this License.
-
-</li><li> Preserve the section Entitled &ldquo;History&rdquo;, Preserve its Title, and add
-to it an item stating at least the title, year, new authors, and
-publisher of the Modified Version as given on the Title Page. If
-there is no section Entitled &ldquo;History&rdquo; in the Document, create one
-stating the title, year, authors, and publisher of the Document as
-given on its Title Page, then add an item describing the Modified
-Version as stated in the previous sentence.
-
-</li><li> Preserve the network location, if any, given in the Document for
-public access to a Transparent copy of the Document, and likewise
-the network locations given in the Document for previous versions
-it was based on. These may be placed in the &ldquo;History&rdquo; section.
-You may omit a network location for a work that was published at
-least four years before the Document itself, or if the original
-publisher of the version it refers to gives permission.
-
-</li><li> For any section Entitled &ldquo;Acknowledgements&rdquo; or &ldquo;Dedications&rdquo;, Preserve
-the Title of the section, and preserve in the section all the
-substance and tone of each of the contributor acknowledgements and/or
-dedications given therein.
-
-</li><li> Preserve all the Invariant Sections of the Document,
-unaltered in their text and in their titles. Section numbers
-or the equivalent are not considered part of the section titles.
-
-</li><li> Delete any section Entitled &ldquo;Endorsements&rdquo;. Such a section
-may not be included in the Modified Version.
-
-</li><li> Do not retitle any existing section to be Entitled &ldquo;Endorsements&rdquo; or
-to conflict in title with any Invariant Section.
-
-</li><li> Preserve any Warranty Disclaimers.
-</li></ol>
-
-<p>If the Modified Version includes new front-matter sections or
-appendices that qualify as Secondary Sections and contain no material
-copied from the Document, you may at your option designate some or all
-of these sections as invariant. To do this, add their titles to the
-list of Invariant Sections in the Modified Version&rsquo;s license notice.
-These titles must be distinct from any other section titles.
-</p>
-<p>You may add a section Entitled &ldquo;Endorsements&rdquo;, provided it contains
-nothing but endorsements of your Modified Version by various
-parties&mdash;for example, statements of peer review or that the text has
-been approved by an organization as the authoritative definition of a
-standard.
-</p>
-<p>You may add a passage of up to five words as a Front-Cover Text, and a
-passage of up to 25 words as a Back-Cover Text, to the end of the list
-of Cover Texts in the Modified Version. Only one passage of
-Front-Cover Text and one of Back-Cover Text may be added by (or
-through arrangements made by) any one entity. If the Document already
-includes a cover text for the same cover, previously added by you or
-by arrangement made by the same entity you are acting on behalf of,
-you may not add another; but you may replace the old one, on explicit
-permission from the previous publisher that added the old one.
-</p>
-<p>The author(s) and publisher(s) of the Document do not by this License
-give permission to use their names for publicity for or to assert or
-imply endorsement of any Modified Version.
-</p>
-</li><li> COMBINING DOCUMENTS
-
-<p>You may combine the Document with other documents released under this
-License, under the terms defined in section 4 above for modified
-versions, provided that you include in the combination all of the
-Invariant Sections of all of the original documents, unmodified, and
-list them all as Invariant Sections of your combined work in its
-license notice, and that you preserve all their Warranty Disclaimers.
-</p>
-<p>The combined work need only contain one copy of this License, and
-multiple identical Invariant Sections may be replaced with a single
-copy. If there are multiple Invariant Sections with the same name but
-different contents, make the title of each such section unique by
-adding at the end of it, in parentheses, the name of the original
-author or publisher of that section if known, or else a unique number.
-Make the same adjustment to the section titles in the list of
-Invariant Sections in the license notice of the combined work.
-</p>
-<p>In the combination, you must combine any sections Entitled &ldquo;History&rdquo;
-in the various original documents, forming one section Entitled
-&ldquo;History&rdquo;; likewise combine any sections Entitled &ldquo;Acknowledgements&rdquo;,
-and any sections Entitled &ldquo;Dedications&rdquo;. You must delete all
-sections Entitled &ldquo;Endorsements.&rdquo;
-</p>
-</li><li> COLLECTIONS OF DOCUMENTS
-
-<p>You may make a collection consisting of the Document and other documents
-released under this License, and replace the individual copies of this
-License in the various documents with a single copy that is included in
-the collection, provided that you follow the rules of this License for
-verbatim copying of each of the documents in all other respects.
-</p>
-<p>You may extract a single document from such a collection, and distribute
-it individually under this License, provided you insert a copy of this
-License into the extracted document, and follow this License in all
-other respects regarding verbatim copying of that document.
-</p>
-</li><li> AGGREGATION WITH INDEPENDENT WORKS
-
-<p>A compilation of the Document or its derivatives with other separate
-and independent documents or works, in or on a volume of a storage or
-distribution medium, is called an &ldquo;aggregate&rdquo; if the copyright
-resulting from the compilation is not used to limit the legal rights
-of the compilation&rsquo;s users beyond what the individual works permit.
-When the Document is included in an aggregate, this License does not
-apply to the other works in the aggregate which are not themselves
-derivative works of the Document.
-</p>
-<p>If the Cover Text requirement of section 3 is applicable to these
-copies of the Document, then if the Document is less than one half of
-the entire aggregate, the Document&rsquo;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.
-</p>
-</li><li> TRANSLATION
-
-<p>Translation is considered a kind of modification, so you may
-distribute translations of the Document under the terms of section 4.
-Replacing Invariant Sections with translations requires special
-permission from their copyright holders, but you may include
-translations of some or all Invariant Sections in addition to the
-original versions of these Invariant Sections. You may include a
-translation of this License, and all the license notices in the
-Document, and any Warranty Disclaimers, provided that you also include
-the original English version of this License and the original versions
-of those notices and disclaimers. In case of a disagreement between
-the translation and the original version of this License or a notice
-or disclaimer, the original version will prevail.
-</p>
-<p>If a section in the Document is Entitled &ldquo;Acknowledgements&rdquo;,
-&ldquo;Dedications&rdquo;, or &ldquo;History&rdquo;, the requirement (section 4) to Preserve
-its Title (section 1) will typically require changing the actual
-title.
-</p>
-</li><li> TERMINATION
-
-<p>You may not copy, modify, sublicense, or distribute the Document
-except as expressly provided under this License. Any attempt
-otherwise to copy, modify, sublicense, or distribute it is void, and
-will automatically terminate your rights under this License.
-</p>
-<p>However, if you cease all violation of this License, then your license
-from a particular copyright holder is reinstated (a) provisionally,
-unless and until the copyright holder explicitly and finally
-terminates your license, and (b) permanently, if the copyright holder
-fails to notify you of the violation by some reasonable means prior to
-60 days after the cessation.
-</p>
-<p>Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-</p>
-<p>Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License. If your rights have been terminated and not permanently
-reinstated, receipt of a copy of some or all of the same material does
-not give you any rights to use it.
-</p>
-</li><li> FUTURE REVISIONS OF THIS LICENSE
-
-<p>The Free Software Foundation may publish new, revised versions
-of the GNU Free Documentation License from time to time. Such new
-versions will be similar in spirit to the present version, but may
-differ in detail to address new problems or concerns. See
-<a href="http://www.gnu.org/copyleft/">http://www.gnu.org/copyleft/</a>.
-</p>
-<p>Each version of the License is given a distinguishing version number.
-If the Document specifies that a particular numbered version of this
-License &ldquo;or any later version&rdquo; applies to it, you have the option of
-following the terms and conditions either of that specified version or
-of any later version that has been published (not as a draft) by the
-Free Software Foundation. If the Document does not specify a version
-number of this License, you may choose any version ever published (not
-as a draft) by the Free Software Foundation. If the Document
-specifies that a proxy can decide which future versions of this
-License can be used, that proxy&rsquo;s public statement of acceptance of a
-version permanently authorizes you to choose that version for the
-Document.
-</p>
-</li><li> RELICENSING
-
-<p>&ldquo;Massive Multiauthor Collaboration Site&rdquo; (or &ldquo;MMC Site&rdquo;) means any
-World Wide Web server that publishes copyrightable works and also
-provides prominent facilities for anybody to edit those works. A
-public wiki that anybody can edit is an example of such a server. A
-&ldquo;Massive Multiauthor Collaboration&rdquo; (or &ldquo;MMC&rdquo;) contained in the
-site means any set of copyrightable works thus published on the MMC
-site.
-</p>
-<p>&ldquo;CC-BY-SA&rdquo; means the Creative Commons Attribution-Share Alike 3.0
-license published by Creative Commons Corporation, a not-for-profit
-corporation with a principal place of business in San Francisco,
-California, as well as future copyleft versions of that license
-published by that same organization.
-</p>
-<p>&ldquo;Incorporate&rdquo; means to publish or republish a Document, in whole or
-in part, as part of another Document.
-</p>
-<p>An MMC is &ldquo;eligible for relicensing&rdquo; if it is licensed under this
-License, and if all works that were first published under this License
-somewhere other than this MMC, and subsequently incorporated in whole
-or in part into the MMC, (1) had no cover texts or invariant sections,
-and (2) were thus incorporated prior to November 1, 2008.
-</p>
-<p>The operator of an MMC Site may republish an MMC contained in the site
-under CC-BY-SA on the same site at any time before August 1, 2009,
-provided the MMC is eligible for relicensing.
-</p>
-</li></ol>
-
-<a name="ADDENDUM_003a-How-to-use-this-License-for-your-documents"></a>
-<h3 class="unnumberedsec">ADDENDUM: How to use this License for your documents</h3>
-
-<p>To use this License in a document you have written, include a copy of
-the License in the document and put the following copyright and
-license notices just after the title page:
-</p>
-<div class="smallexample">
-<pre class="smallexample"> Copyright (C) <var>year</var> <var>your name</var>.
- Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.3
- or any later version published by the Free Software Foundation;
- with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
- Texts. A copy of the license is included in the section entitled ``GNU
- Free Documentation License''.
-</pre></div>
-
-<p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
-replace the &ldquo;with...Texts.&rdquo; line with this:
-</p>
-<div class="smallexample">
-<pre class="smallexample"> with the Invariant Sections being <var>list their titles</var>, with
- the Front-Cover Texts being <var>list</var>, and with the Back-Cover Texts
- being <var>list</var>.
-</pre></div>
-
-<p>If you have Invariant Sections without Cover Texts, or some other
-combination of the three, merge those two alternatives to suit the
-situation.
-</p>
-<p>If your document contains nontrivial examples of program code, we
-recommend releasing these examples in parallel under your choice of
-free software license, such as the GNU General Public License,
-to permit their use in free software.
-</p>
-
-<hr />
-<p><p><a href="./index.html">Return to the GCC Installation page</a>
-</p>
-
-<hr>
-
-
-
-</body>
-</html>
diff --git a/gcc-4.9/INSTALL/index.html b/gcc-4.9/INSTALL/index.html
deleted file mode 100644
index 23872e7..0000000
--- a/gcc-4.9/INSTALL/index.html
+++ /dev/null
@@ -1,165 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<!-- Copyright (C) 1988-2014 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.3 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. -->
-<!-- Created by GNU Texinfo 5.1, http://www.gnu.org/software/texinfo/ -->
-<head>
-<title>Installing GCC</title>
-
-<meta name="description" content="Installing GCC">
-<meta name="keywords" content="Installing GCC">
-<meta name="resource-type" content="document">
-<meta name="distribution" content="global">
-<meta name="Generator" content="makeinfo">
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<style type="text/css">
-<!--
-a.summary-letter {text-decoration: none}
-blockquote.smallquotation {font-size: smaller}
-div.display {margin-left: 3.2em}
-div.example {margin-left: 3.2em}
-div.indentedblock {margin-left: 3.2em}
-div.lisp {margin-left: 3.2em}
-div.smalldisplay {margin-left: 3.2em}
-div.smallexample {margin-left: 3.2em}
-div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
-div.smalllisp {margin-left: 3.2em}
-kbd {font-style:oblique}
-pre.display {font-family: inherit}
-pre.format {font-family: inherit}
-pre.menu-comment {font-family: serif}
-pre.menu-preformatted {font-family: serif}
-pre.smalldisplay {font-family: inherit; font-size: smaller}
-pre.smallexample {font-size: smaller}
-pre.smallformat {font-family: inherit; font-size: smaller}
-pre.smalllisp {font-size: smaller}
-span.nocodebreak {white-space:nowrap}
-span.nolinebreak {white-space:nowrap}
-span.roman {font-family:serif; font-weight:normal}
-span.sansserif {font-family:sans-serif; font-weight:normal}
-ul.no-bullet {list-style: none}
--->
-</style>
-
-
-</head>
-
-<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
-<h1 class="settitle" align="center">Installing GCC</h1>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<p>The latest version of this document is always available at
-<a href="http://gcc.gnu.org/install/">http://gcc.gnu.org/install/</a>.
-It refers to the current development sources, instructions for
-specific released versions are included with the sources.
-</p>
-<p>This document describes the generic installation procedure for GCC as well
-as detailing some target specific installation instructions.
-</p>
-<p>GCC includes several components that previously were separate distributions
-with their own installation instructions. This document supersedes all
-package-specific installation instructions.
-</p>
-<p><em>Before</em> starting the build/install procedure please check the
-<a href="specific.html">host/target specific installation notes</a>.
-We recommend you browse the entire generic installation instructions before
-you proceed.
-</p>
-<p>Lists of successful builds for released versions of GCC are
-available at <a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>.
-These lists are updated as new information becomes available.
-</p>
-<p>The installation procedure itself is broken into five steps.
-</p>
-<ol>
-<li> <a href="prerequisites.html">Prerequisites</a>
-</li><li> <a href="download.html">Downloading the source</a>
-</li><li> <a href="configure.html">Configuration</a>
-</li><li> <a href="build.html">Building</a>
-</li><li> <a href="test.html">Testing</a> (optional)
-</li><li> <a href="finalinstall.html">Final install</a>
-</li></ol>
-
-<p>Please note that GCC does not support &lsquo;<samp>make uninstall</samp>&rsquo; and probably
-won&rsquo;t do so in the near future as this would open a can of worms. Instead,
-we suggest that you install GCC into a directory of its own and simply
-remove that directory when you do not need that specific version of GCC
-any longer, and, if shared libraries are installed there as well, no
-more binaries exist that use them.
-</p>
-<p>There are also some <a href="old.html">old installation instructions</a>,
-which are mostly obsolete but still contain some information which has
-not yet been merged into the main part of this manual.
-</p>
-<hr />
-<p><p><a href="./index.html">Return to the GCC Installation page</a>
-</p>
-<p>Copyright &copy; 1988-2014 Free Software Foundation, Inc.
-</p><br>
-<p>Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.3 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, the Front-Cover texts being (a) (see below), and
-with the Back-Cover Texts being (b) (see below). A copy of the
-license is included in the section entitled &ldquo;<a href="./gfdl.html">GNU
-Free Documentation License</a>&rdquo;.
-</p>
-<p>(a) The FSF&rsquo;s Front-Cover Text is:
-</p>
-<p>A GNU Manual
-</p>
-<p>(b) The FSF&rsquo;s Back-Cover Text is:
-</p>
-<p>You have freedom to copy and modify this GNU Manual, like GNU
- software. Copies published by the Free Software Foundation raise
- funds for GNU development.
-</p>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-</body>
-</html>
diff --git a/gcc-4.9/INSTALL/old.html b/gcc-4.9/INSTALL/old.html
deleted file mode 100644
index 8aaf8b1..0000000
--- a/gcc-4.9/INSTALL/old.html
+++ /dev/null
@@ -1,253 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<!-- Copyright (C) 1988-2014 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.3 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. -->
-<!-- Created by GNU Texinfo 5.1, http://www.gnu.org/software/texinfo/ -->
-<head>
-<title>Installing GCC</title>
-
-<meta name="description" content="Installing GCC">
-<meta name="keywords" content="Installing GCC">
-<meta name="resource-type" content="document">
-<meta name="distribution" content="global">
-<meta name="Generator" content="makeinfo">
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<style type="text/css">
-<!--
-a.summary-letter {text-decoration: none}
-blockquote.smallquotation {font-size: smaller}
-div.display {margin-left: 3.2em}
-div.example {margin-left: 3.2em}
-div.indentedblock {margin-left: 3.2em}
-div.lisp {margin-left: 3.2em}
-div.smalldisplay {margin-left: 3.2em}
-div.smallexample {margin-left: 3.2em}
-div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
-div.smalllisp {margin-left: 3.2em}
-kbd {font-style:oblique}
-pre.display {font-family: inherit}
-pre.format {font-family: inherit}
-pre.menu-comment {font-family: serif}
-pre.menu-preformatted {font-family: serif}
-pre.smalldisplay {font-family: inherit; font-size: smaller}
-pre.smallexample {font-size: smaller}
-pre.smallformat {font-family: inherit; font-size: smaller}
-pre.smalllisp {font-size: smaller}
-span.nocodebreak {white-space:nowrap}
-span.nolinebreak {white-space:nowrap}
-span.roman {font-family:serif; font-weight:normal}
-span.sansserif {font-family:sans-serif; font-weight:normal}
-ul.no-bullet {list-style: none}
--->
-</style>
-
-
-</head>
-
-<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
-<h1 class="settitle" align="center">Installing GCC</h1>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<h1 align="center">Old installation documentation</h1>
-<p>Note most of this information is out of date and superseded by the
-previous chapters of this manual. It is provided for historical
-reference only, because of a lack of volunteers to merge it into the
-main manual.
-</p>
-
-<p>Here is the procedure for installing GCC on a GNU or Unix system.
-</p>
-<ol>
-<li> If you have chosen a configuration for GCC which requires other GNU
-tools (such as GAS or the GNU linker) instead of the standard system
-tools, install the required tools in the build directory under the names
-<samp>as</samp>, <samp>ld</samp> or whatever is appropriate.
-
-<p>Alternatively, you can do subsequent compilation using a value of the
-<code>PATH</code> environment variable such that the necessary GNU tools come
-before the standard system tools.
-</p>
-</li><li> Specify the host, build and target machine configurations. You do this
-when you run the <samp>configure</samp> script.
-
-<p>The <em>build</em> machine is the system which you are using, the
-<em>host</em> machine is the system where you want to run the resulting
-compiler (normally the build machine), and the <em>target</em> machine is
-the system for which you want the compiler to generate code.
-</p>
-<p>If you are building a compiler to produce code for the machine it runs
-on (a native compiler), you normally do not need to specify any operands
-to <samp>configure</samp>; it will try to guess the type of machine you are on
-and use that as the build, host and target machines. So you don&rsquo;t need
-to specify a configuration when building a native compiler unless
-<samp>configure</samp> cannot figure out what your configuration is or guesses
-wrong.
-</p>
-<p>In those cases, specify the build machine&rsquo;s <em>configuration name</em>
-with the <samp>--host</samp> option; the host and target will default to be
-the same as the host machine.
-</p>
-<p>Here is an example:
-</p>
-<div class="smallexample">
-<pre class="smallexample">./configure --host=sparc-sun-sunos4.1
-</pre></div>
-
-<p>A configuration name may be canonical or it may be more or less
-abbreviated.
-</p>
-<p>A canonical configuration name has three parts, separated by dashes.
-It looks like this: &lsquo;<samp><var>cpu</var>-<var>company</var>-<var>system</var></samp>&rsquo;.
-(The three parts may themselves contain dashes; <samp>configure</samp>
-can figure out which dashes serve which purpose.) For example,
-&lsquo;<samp>m68k-sun-sunos4.1</samp>&rsquo; specifies a Sun 3.
-</p>
-<p>You can also replace parts of the configuration by nicknames or aliases.
-For example, &lsquo;<samp>sun3</samp>&rsquo; stands for &lsquo;<samp>m68k-sun</samp>&rsquo;, so
-&lsquo;<samp>sun3-sunos4.1</samp>&rsquo; is another way to specify a Sun 3.
-</p>
-<p>You can specify a version number after any of the system types, and some
-of the CPU types. In most cases, the version is irrelevant, and will be
-ignored. So you might as well specify the version if you know it.
-</p>
-<p>See <a href="#Configurations">Configurations</a>, for a list of supported configuration names and
-notes on many of the configurations. You should check the notes in that
-section before proceeding any further with the installation of GCC.
-</p>
-</li></ol>
-
-<h2><a name="Configurations"></a>Configurations Supported by GCC</h2><a name="index-configurations-supported-by-GCC"></a>
-
-<p>Here are the possible CPU types:
-</p>
-<blockquote>
-<p>1750a, a29k, alpha, arm, avr, c<var>n</var>, clipper, dsp16xx, elxsi, fr30, h8300,
-hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860, i960, ip2k, m32r,
-m68000, m68k, m88k, mcore, mips, mipsel, mips64, mips64el,
-mn10200, mn10300, ns32k, pdp11, powerpc, powerpcle, romp, rs6000, sh, sparc,
-sparclite, sparc64, v850, vax, we32k.
-</p></blockquote>
-
-<p>Here are the recognized company names. As you can see, customary
-abbreviations are used rather than the longer official names.
-</p>
-<blockquote>
-<p>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.
-</p></blockquote>
-
-<p>The company name is meaningful only to disambiguate when the rest of
-the information supplied is insufficient. You can omit it, writing
-just &lsquo;<samp><var>cpu</var>-<var>system</var></samp>&rsquo;, if it is not needed. For example,
-&lsquo;<samp>vax-ultrix4.2</samp>&rsquo; is equivalent to &lsquo;<samp>vax-dec-ultrix4.2</samp>&rsquo;.
-</p>
-<p>Here is a list of system types:
-</p>
-<blockquote>
-<p>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.
-</p></blockquote>
-
-<p>You can omit the system type; then <samp>configure</samp> guesses the
-operating system from the CPU and company.
-</p>
-<p>You can add a version number to the system type; this may or may not
-make a difference. For example, you can write &lsquo;<samp>bsd4.3</samp>&rsquo; or
-&lsquo;<samp>bsd4.4</samp>&rsquo; to distinguish versions of BSD. In practice, the version
-number is most needed for &lsquo;<samp>sysv3</samp>&rsquo; and &lsquo;<samp>sysv4</samp>&rsquo;, which are often
-treated differently.
-</p>
-<p>&lsquo;<samp>linux-gnu</samp>&rsquo; is the canonical name for the GNU/Linux target; however
-GCC will also accept &lsquo;<samp>linux</samp>&rsquo;. The version of the kernel in use is
-not relevant on these systems. A suffix such as &lsquo;<samp>libc1</samp>&rsquo; or &lsquo;<samp>aout</samp>&rsquo;
-distinguishes major versions of the C library; all of the suffixed versions
-are obsolete.
-</p>
-<p>If you specify an impossible combination such as &lsquo;<samp>i860-dg-vms</samp>&rsquo;,
-then you may get an error message from <samp>configure</samp>, or it may
-ignore part of the information and do the best it can with the rest.
-<samp>configure</samp> always prints the canonical name for the alternative
-that it used. GCC does not support all possible alternatives.
-</p>
-<p>Often a particular model of machine has a name. Many machine names are
-recognized as aliases for CPU/company combinations. Thus, the machine
-name &lsquo;<samp>sun3</samp>&rsquo;, mentioned above, is an alias for &lsquo;<samp>m68k-sun</samp>&rsquo;.
-Sometimes we accept a company name as a machine name, when the name is
-popularly used for a particular machine. Here is a table of the known
-machine names:
-</p>
-<blockquote>
-<p>3300, 3b1, 3b<var>n</var>, 7300, altos3068, altos,
-apollo68, att-7300, balance,
-convex-c<var>n</var>, crds, decstation-3100,
-decstation, delta, encore,
-fx2800, gmicro, hp7<var>nn</var>, hp8<var>nn</var>,
-hp9k2<var>nn</var>, hp9k3<var>nn</var>, hp9k7<var>nn</var>,
-hp9k8<var>nn</var>, iris4d, iris, isi68,
-m3230, magnum, merlin, miniframe,
-mmax, news-3600, news800, news, next,
-pbd, pc532, pmax, powerpc, powerpcle, ps2, risc-news,
-rtpc, sun2, sun386i, sun386, sun3,
-sun4, symmetry, tower-32, tower.
-</p></blockquote>
-
-<p>Remember that a machine name specifies both the cpu type and the company
-name.
-<hr />
-<p><a href="./index.html">Return to the GCC Installation page</a>
-</p>
-
-
-
-
-
-</body>
-</html>
diff --git a/gcc-4.9/INSTALL/prerequisites.html b/gcc-4.9/INSTALL/prerequisites.html
deleted file mode 100644
index 79dcc9e..0000000
--- a/gcc-4.9/INSTALL/prerequisites.html
+++ /dev/null
@@ -1,431 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<!-- Copyright (C) 1988-2014 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.3 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. -->
-<!-- Created by GNU Texinfo 5.1, http://www.gnu.org/software/texinfo/ -->
-<head>
-<title>Installing GCC</title>
-
-<meta name="description" content="Installing GCC">
-<meta name="keywords" content="Installing GCC">
-<meta name="resource-type" content="document">
-<meta name="distribution" content="global">
-<meta name="Generator" content="makeinfo">
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<style type="text/css">
-<!--
-a.summary-letter {text-decoration: none}
-blockquote.smallquotation {font-size: smaller}
-div.display {margin-left: 3.2em}
-div.example {margin-left: 3.2em}
-div.indentedblock {margin-left: 3.2em}
-div.lisp {margin-left: 3.2em}
-div.smalldisplay {margin-left: 3.2em}
-div.smallexample {margin-left: 3.2em}
-div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
-div.smalllisp {margin-left: 3.2em}
-kbd {font-style:oblique}
-pre.display {font-family: inherit}
-pre.format {font-family: inherit}
-pre.menu-comment {font-family: serif}
-pre.menu-preformatted {font-family: serif}
-pre.smalldisplay {font-family: inherit; font-size: smaller}
-pre.smallexample {font-size: smaller}
-pre.smallformat {font-family: inherit; font-size: smaller}
-pre.smalllisp {font-size: smaller}
-span.nocodebreak {white-space:nowrap}
-span.nolinebreak {white-space:nowrap}
-span.roman {font-family:serif; font-weight:normal}
-span.sansserif {font-family:sans-serif; font-weight:normal}
-ul.no-bullet {list-style: none}
--->
-</style>
-
-
-</head>
-
-<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
-<h1 class="settitle" align="center">Installing GCC</h1>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<a name="index-Prerequisites"></a>
-
-<p>GCC requires that various tools and packages be available for use in the
-build procedure. Modifying GCC sources requires additional tools
-described below.
-</p>
-<a name="Tools_002fpackages-necessary-for-building-GCC"></a>
-<h3 class="heading">Tools/packages necessary for building GCC</h3>
-<dl compact="compact">
-<dt>ISO C++98 compiler</dt>
-<dd><p>Necessary to bootstrap GCC, although versions of GCC prior
-to 4.8 also allow bootstrapping with a ISO C89 compiler and versions
-of GCC prior to 3.4 also allow bootstrapping with a traditional
-(K&amp;R) C compiler.
-</p>
-<p>To build all languages in a cross-compiler or other configuration where
-3-stage bootstrap is not performed, you need to start with an existing
-GCC binary (version 3.4 or later) because source code for language
-frontends other than C might use GCC extensions.
-</p>
-<p>Note that to bootstrap GCC with versions of GCC earlier than 3.4, you
-may need to use <samp>--disable-stage1-checking</samp>, though
-bootstrapping the compiler with such earlier compilers is strongly
-discouraged.
-</p>
-</dd>
-<dt>C standard library and headers</dt>
-<dd>
-<p>In order to build GCC, the C standard library and headers must be present
-for all target variants for which target libraries will be built (and not
-only the variant of the host C++ compiler).
-</p>
-<p>This affects the popular &lsquo;<samp>x86_64-unknown-linux-gnu</samp>&rsquo; platform (among
-other multilib targets), for which 64-bit (&lsquo;<samp>x86_64</samp>&rsquo;) and 32-bit
-(&lsquo;<samp>i386</samp>&rsquo;) libc headers are usually packaged separately. If you do a
-build of a native compiler on &lsquo;<samp>x86_64-unknown-linux-gnu</samp>&rsquo;, make sure you
-either have the 32-bit libc developer package properly installed (the exact
-name of the package depends on your distro) or you must build GCC as a
-64-bit only compiler by configuring with the option
-<samp>--disable-multilib</samp>. Otherwise, you may encounter an error such as
-&lsquo;<samp>fatal error: gnu/stubs-32.h: No such file</samp>&rsquo;
-</p>
-</dd>
-<dt>GNAT</dt>
-<dd>
-<p>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.
-</p>
-</dd>
-<dt>A &ldquo;working&rdquo; POSIX compatible shell, or GNU bash</dt>
-<dd>
-<p>Necessary when running <code>configure</code> because some
-<code>/bin/sh</code> shells have bugs and may crash when configuring the
-target libraries. In other cases, <code>/bin/sh</code> or <code>ksh</code>
-have disastrous corner-case performance problems. This
-can cause target <code>configure</code> runs to literally take days to
-complete in some cases.
-</p>
-<p>So on some platforms <code>/bin/ksh</code> is sufficient, on others it
-isn&rsquo;t. See the host/target specific instructions for your platform, or
-use <code>bash</code> to be sure. Then set <code>CONFIG_SHELL</code> in your
-environment to your &ldquo;good&rdquo; shell prior to running
-<code>configure</code>/<code>make</code>.
-</p>
-<p><code>zsh</code> is not a fully compliant POSIX shell and will not
-work when configuring GCC.
-</p>
-</dd>
-<dt>A POSIX or SVR4 awk</dt>
-<dd>
-<p>Necessary for creating some of the generated source files for GCC.
-If in doubt, use a recent GNU awk version, as some of the older ones
-are broken. GNU awk version 3.1.5 is known to work.
-</p>
-</dd>
-<dt>GNU binutils</dt>
-<dd>
-<p>Necessary in some circumstances, optional in others. See the
-host/target specific instructions for your platform for the exact
-requirements.
-</p>
-</dd>
-<dt>gzip version 1.2.4 (or later) or</dt>
-<dt>bzip2 version 1.0.2 (or later)</dt>
-<dd>
-<p>Necessary to uncompress GCC <code>tar</code> files when source code is
-obtained via FTP mirror sites.
-</p>
-</dd>
-<dt>GNU make version 3.80 (or later)</dt>
-<dd>
-<p>You must have GNU make installed to build GCC.
-</p>
-</dd>
-<dt>GNU tar version 1.14 (or later)</dt>
-<dd>
-<p>Necessary (only on some platforms) to untar the source code. Many
-systems&rsquo; <code>tar</code> programs will also work, only try GNU
-<code>tar</code> if you have problems.
-</p>
-</dd>
-<dt>Perl version 5.6.1 (or later)</dt>
-<dd>
-<p>Necessary when targeting Darwin, building &lsquo;<samp>libstdc++</samp>&rsquo;,
-and not using <samp>--disable-symvers</samp>.
-Necessary when targeting Solaris 2 with Sun <code>ld</code> and not using
-<samp>--disable-symvers</samp>. The bundled <code>perl</code> in Solaris&nbsp;8
-and up works.
-</p>
-<p>Necessary when regenerating <samp>Makefile</samp> dependencies in libiberty.
-Necessary when regenerating <samp>libiberty/functions.texi</samp>.
-Necessary when generating manpages from Texinfo manuals.
-Used by various scripts to generate some files included in SVN (mainly
-Unicode-related and rarely changing) from source tables.
-</p>
-</dd>
-<dt><code>jar</code>, or InfoZIP (<code>zip</code> and <code>unzip</code>)</dt>
-<dd>
-<p>Necessary to build libgcj, the GCJ runtime.
-</p>
-</dd>
-</dl>
-
-<p>Several support libraries are necessary to build GCC, some are required,
-others optional. While any sufficiently new version of required tools
-usually work, library requirements are generally stricter. Newer
-versions may work in some cases, but it&rsquo;s safer to use the exact
-versions documented. We appreciate bug reports about problems with
-newer versions, though. If your OS vendor provides packages for the
-support libraries then using those packages may be the simplest way to
-install the libraries.
-</p>
-<dl compact="compact">
-<dt>GNU Multiple Precision Library (GMP) version 4.3.2 (or later)</dt>
-<dd>
-<p>Necessary to build GCC. If a GMP source distribution is found in a
-subdirectory of your GCC sources named <samp>gmp</samp>, it will be built
-together with GCC. Alternatively, if GMP is already installed but it
-is not in your library search path, you will have to configure with the
-<samp>--with-gmp</samp> configure option. See also <samp>--with-gmp-lib</samp>
-and <samp>--with-gmp-include</samp>.
-</p>
-</dd>
-<dt>MPFR Library version 2.4.2 (or later)</dt>
-<dd>
-<p>Necessary to build GCC. It can be downloaded from
-<a href="http://www.mpfr.org/">http://www.mpfr.org/</a>. If an MPFR source distribution is found
-in a subdirectory of your GCC sources named <samp>mpfr</samp>, it will be
-built together with GCC. Alternatively, if MPFR is already installed
-but it is not in your default library search path, the
-<samp>--with-mpfr</samp> configure option should be used. See also
-<samp>--with-mpfr-lib</samp> and <samp>--with-mpfr-include</samp>.
-</p>
-</dd>
-<dt>MPC Library version 0.8.1 (or later)</dt>
-<dd>
-<p>Necessary to build GCC. It can be downloaded from
-<a href="http://www.multiprecision.org/">http://www.multiprecision.org/</a>. If an MPC source distribution
-is found in a subdirectory of your GCC sources named <samp>mpc</samp>, it
-will be built together with GCC. Alternatively, if MPC is already
-installed but it is not in your default library search path, the
-<samp>--with-mpc</samp> configure option should be used. See also
-<samp>--with-mpc-lib</samp> and <samp>--with-mpc-include</samp>.
-</p>
-</dd>
-<dt>ISL Library version 0.12.2</dt>
-<dd>
-<p>Necessary to build GCC with the Graphite loop optimizations.
-It can be downloaded from <a href="ftp://gcc.gnu.org/pub/gcc/infrastructure/">ftp://gcc.gnu.org/pub/gcc/infrastructure/</a>
-as <samp>isl-0.12.2.tar.bz2</samp>. If an ISL source distribution is found
-in a subdirectory of your GCC sources named <samp>isl</samp>, it will be
-built together with GCC. Alternatively, the <samp>--with-isl</samp> configure
-option should be used if ISL is not installed in your default library
-search path.
-</p>
-</dd>
-<dt>CLooG 0.18.1</dt>
-<dd>
-<p>Necessary to build GCC with the Graphite loop optimizations. It can be
-downloaded from <a href="ftp://gcc.gnu.org/pub/gcc/infrastructure/">ftp://gcc.gnu.org/pub/gcc/infrastructure/</a> as
-<samp>cloog-0.18.1.tar.gz</samp>. If a CLooG source distribution is found
-in a subdirectory of your GCC sources named <samp>cloog</samp>, it will be
-built together with GCC. Alternatively, the <samp>--with-cloog</samp> configure
-option should be used if CLooG is not installed in your default library search
-path.
-</p>
-<p>If you want to install CLooG separately it needs to be built against
-ISL 0.12.2 by using the <samp>--with-isl=system</samp> to direct CLooG to pick
-up an already installed ISL. Using the ISL library as bundled with CLooG
-is not supported.
-</p>
-</dd>
-</dl>
-
-<a name="Tools_002fpackages-necessary-for-modifying-GCC"></a>
-<h3 class="heading">Tools/packages necessary for modifying GCC</h3>
-<dl compact="compact">
-<dt>autoconf version 2.64</dt>
-<dt>GNU m4 version 1.4.6 (or later)</dt>
-<dd>
-<p>Necessary when modifying <samp>configure.ac</samp>, <samp>aclocal.m4</samp>, etc.
-to regenerate <samp>configure</samp> and <samp>config.in</samp> files.
-</p>
-</dd>
-<dt>automake version 1.11.1</dt>
-<dd>
-<p>Necessary when modifying a <samp>Makefile.am</samp> file to regenerate its
-associated <samp>Makefile.in</samp>.
-</p>
-<p>Much of GCC does not use automake, so directly edit the <samp>Makefile.in</samp>
-file. Specifically this applies to the <samp>gcc</samp>, <samp>intl</samp>,
-<samp>libcpp</samp>, <samp>libiberty</samp>, <samp>libobjc</samp> directories as well
-as any of their subdirectories.
-</p>
-<p>For directories that use automake, GCC requires the latest release in
-the 1.11 series, which is currently 1.11.1. When regenerating a directory
-to a newer version, please update all the directories using an older 1.11
-to the latest released version.
-</p>
-</dd>
-<dt>gettext version 0.14.5 (or later)</dt>
-<dd>
-<p>Needed to regenerate <samp>gcc.pot</samp>.
-</p>
-</dd>
-<dt>gperf version 2.7.2 (or later)</dt>
-<dd>
-<p>Necessary when modifying <code>gperf</code> input files, e.g.
-<samp>gcc/cp/cfns.gperf</samp> to regenerate its associated header file, e.g.
-<samp>gcc/cp/cfns.h</samp>.
-</p>
-</dd>
-<dt>DejaGnu 1.4.4</dt>
-<dt>Expect</dt>
-<dt>Tcl</dt>
-<dd>
-<p>Necessary to run the GCC testsuite; see the section on testing for
-details. Tcl 8.6 has a known regression in RE pattern handling that
-make parts of the testsuite fail. See
-<a href="http://core.tcl.tk/tcl/tktview/267b7e2334ee2e9de34c4b00d6e72e2f1997085f">http://core.tcl.tk/tcl/tktview/267b7e2334ee2e9de34c4b00d6e72e2f1997085f</a>
-for more information.
-</p>
-</dd>
-<dt>autogen version 5.5.4 (or later) and</dt>
-<dt>guile version 1.4.1 (or later)</dt>
-<dd>
-<p>Necessary to regenerate <samp>fixinc/fixincl.x</samp> from
-<samp>fixinc/inclhack.def</samp> and <samp>fixinc/*.tpl</samp>.
-</p>
-<p>Necessary to run &lsquo;<samp>make check</samp>&rsquo; for <samp>fixinc</samp>.
-</p>
-<p>Necessary to regenerate the top level <samp>Makefile.in</samp> file from
-<samp>Makefile.tpl</samp> and <samp>Makefile.def</samp>.
-</p>
-</dd>
-<dt>Flex version 2.5.4 (or later)</dt>
-<dd>
-<p>Necessary when modifying <samp>*.l</samp> files.
-</p>
-<p>Necessary to build GCC during development because the generated output
-files are not included in the SVN repository. They are included in
-releases.
-</p>
-</dd>
-<dt>Texinfo version 4.7 (or later)</dt>
-<dd>
-<p>Necessary for running <code>makeinfo</code> when modifying <samp>*.texi</samp>
-files to test your changes.
-</p>
-<p>Necessary for running <code>make dvi</code> or <code>make pdf</code> to
-create printable documentation in DVI or PDF format. Texinfo version
-4.8 or later is required for <code>make pdf</code>.
-</p>
-<p>Necessary to build GCC documentation during development because the
-generated output files are not included in the SVN repository. They are
-included in releases.
-</p>
-</dd>
-<dt>TeX (any working version)</dt>
-<dd>
-<p>Necessary for running <code>texi2dvi</code> and <code>texi2pdf</code>, which
-are used when running <code>make dvi</code> or <code>make pdf</code> to create
-DVI or PDF files, respectively.
-</p>
-</dd>
-<dt>SVN (any version)</dt>
-<dt>SSH (any version)</dt>
-<dd>
-<p>Necessary to access the SVN repository. Public releases and weekly
-snapshots of the development sources are also available via FTP.
-</p>
-</dd>
-<dt>GNU diffutils version 2.7 (or later)</dt>
-<dd>
-<p>Useful when submitting patches for the GCC source code.
-</p>
-</dd>
-<dt>patch version 2.5.4 (or later)</dt>
-<dd>
-<p>Necessary when applying patches, created with <code>diff</code>, to one&rsquo;s
-own sources.
-</p>
-</dd>
-<dt>ecj1</dt>
-<dt>gjavah</dt>
-<dd>
-<p>If you wish to modify <samp>.java</samp> files in libjava, you will need to
-configure with <samp>--enable-java-maintainer-mode</samp>, and you will need
-to have executables named <code>ecj1</code> and <code>gjavah</code> in your path.
-The <code>ecj1</code> executable should run the Eclipse Java compiler via
-the GCC-specific entry point. You can download a suitable jar from
-<a href="ftp://sourceware.org/pub/java/">ftp://sourceware.org/pub/java/</a>, or by running the script
-<code>contrib/download_ecj</code>.
-</p>
-</dd>
-<dt>antlr.jar version 2.7.1 (or later)</dt>
-<dt>antlr binary</dt>
-<dd>
-<p>If you wish to build the <code>gjdoc</code> binary in libjava, you will
-need to have an <samp>antlr.jar</samp> library available. The library is
-searched for in system locations but can be specified with
-<samp>--with-antlr-jar=</samp> instead. When configuring with
-<samp>--enable-java-maintainer-mode</samp>, you will need to have one of
-the executables named <code>cantlr</code>, <code>runantlr</code> or
-<code>antlr</code> in your path.
-</p>
-</dd>
-</dl>
-
-<hr />
-<p><p><a href="./index.html">Return to the GCC Installation page</a>
-</p>
-
-
-
-
-
-
-
-
-
-
-
-
-
-</body>
-</html>
diff --git a/gcc-4.9/INSTALL/specific.html b/gcc-4.9/INSTALL/specific.html
deleted file mode 100644
index dc47a69..0000000
--- a/gcc-4.9/INSTALL/specific.html
+++ /dev/null
@@ -1,1454 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<!-- Copyright (C) 1988-2014 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.3 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. -->
-<!-- Created by GNU Texinfo 5.1, http://www.gnu.org/software/texinfo/ -->
-<head>
-<title>Installing GCC</title>
-
-<meta name="description" content="Installing GCC">
-<meta name="keywords" content="Installing GCC">
-<meta name="resource-type" content="document">
-<meta name="distribution" content="global">
-<meta name="Generator" content="makeinfo">
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<style type="text/css">
-<!--
-a.summary-letter {text-decoration: none}
-blockquote.smallquotation {font-size: smaller}
-div.display {margin-left: 3.2em}
-div.example {margin-left: 3.2em}
-div.indentedblock {margin-left: 3.2em}
-div.lisp {margin-left: 3.2em}
-div.smalldisplay {margin-left: 3.2em}
-div.smallexample {margin-left: 3.2em}
-div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
-div.smalllisp {margin-left: 3.2em}
-kbd {font-style:oblique}
-pre.display {font-family: inherit}
-pre.format {font-family: inherit}
-pre.menu-comment {font-family: serif}
-pre.menu-preformatted {font-family: serif}
-pre.smalldisplay {font-family: inherit; font-size: smaller}
-pre.smallexample {font-size: smaller}
-pre.smallformat {font-family: inherit; font-size: smaller}
-pre.smalllisp {font-size: smaller}
-span.nocodebreak {white-space:nowrap}
-span.nolinebreak {white-space:nowrap}
-span.roman {font-family:serif; font-weight:normal}
-span.sansserif {font-family:sans-serif; font-weight:normal}
-ul.no-bullet {list-style: none}
--->
-</style>
-
-
-</head>
-
-<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
-<h1 class="settitle" align="center">Installing GCC</h1>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<a name="index-Specific"></a>
-<a name="index-Specific-installation-notes"></a>
-<a name="index-Target-specific-installation"></a>
-<a name="index-Host-specific-installation"></a>
-<a name="index-Target-specific-installation-notes"></a>
-
-<p>Please read this document carefully <em>before</em> installing the
-GNU Compiler Collection on your machine.
-</p>
-<p>Note that this list of install notes is <em>not</em> a list of supported
-hosts or targets. Not all supported hosts and targets are listed
-here, only the ones that require host-specific or target-specific
-information have to.
-</p>
-<ul>
-<li> <a href="#alpha-x-x">alpha*-*-*</a>
-</li><li> <a href="#alpha-dec-osf51">alpha*-dec-osf5.1</a>
-</li><li> <a href="#amd64-x-solaris210">amd64-*-solaris2.10</a>
-</li><li> <a href="#arm-x-eabi">arm-*-eabi</a>
-</li><li> <a href="#avr">avr</a>
-</li><li> <a href="#bfin">Blackfin</a>
-</li><li> <a href="#dos">DOS</a>
-</li><li> <a href="#x-x-freebsd">*-*-freebsd*</a>
-</li><li> <a href="#h8300-hms">h8300-hms</a>
-</li><li> <a href="#hppa-hp-hpux">hppa*-hp-hpux*</a>
-</li><li> <a href="#hppa-hp-hpux10">hppa*-hp-hpux10</a>
-</li><li> <a href="#hppa-hp-hpux11">hppa*-hp-hpux11</a>
-</li><li> <a href="#x-x-linux-gnu">*-*-linux-gnu</a>
-</li><li> <a href="#ix86-x-linux">i?86-*-linux*</a>
-</li><li> <a href="#ix86-x-solaris289">i?86-*-solaris2.9</a>
-</li><li> <a href="#ix86-x-solaris210">i?86-*-solaris2.10</a>
-</li><li> <a href="#ia64-x-linux">ia64-*-linux</a>
-</li><li> <a href="#ia64-x-hpux">ia64-*-hpux*</a>
-</li><li> <a href="#x-ibm-aix">*-ibm-aix*</a>
-</li><li> <a href="#iq2000-x-elf">iq2000-*-elf</a>
-</li><li> <a href="#lm32-x-elf">lm32-*-elf</a>
-</li><li> <a href="#lm32-x-uclinux">lm32-*-uclinux</a>
-</li><li> <a href="#m32c-x-elf">m32c-*-elf</a>
-</li><li> <a href="#m32r-x-elf">m32r-*-elf</a>
-</li><li> <a href="#m68k-x-x">m68k-*-*</a>
-</li><li> <a href="#m68k-uclinux">m68k-uclinux</a>
-</li><li> <a href="#mep-x-elf">mep-*-elf</a>
-</li><li> <a href="#microblaze-x-elf">microblaze-*-elf</a>
-</li><li> <a href="#mips-x-x">mips-*-*</a>
-</li><li> <a href="#mips-sgi-irix5">mips-sgi-irix5</a>
-</li><li> <a href="#mips-sgi-irix6">mips-sgi-irix6</a>
-</li><li> <a href="#nds32le-x-elf">nds32le-*-elf</a>
-</li><li> <a href="#nds32be-x-elf">nds32be-*-elf</a>
-</li><li> <a href="#powerpc-x-x">powerpc*-*-*</a>
-</li><li> <a href="#powerpc-x-darwin">powerpc-*-darwin*</a>
-</li><li> <a href="#powerpc-x-elf">powerpc-*-elf</a>
-</li><li> <a href="#powerpc-x-linux-gnu">powerpc*-*-linux-gnu*</a>
-</li><li> <a href="#powerpc-x-netbsd">powerpc-*-netbsd*</a>
-</li><li> <a href="#powerpc-x-eabisim">powerpc-*-eabisim</a>
-</li><li> <a href="#powerpc-x-eabi">powerpc-*-eabi</a>
-</li><li> <a href="#powerpcle-x-elf">powerpcle-*-elf</a>
-</li><li> <a href="#powerpcle-x-eabisim">powerpcle-*-eabisim</a>
-</li><li> <a href="#powerpcle-x-eabi">powerpcle-*-eabi</a>
-</li><li> <a href="#s390-x-linux">s390-*-linux*</a>
-</li><li> <a href="#s390x-x-linux">s390x-*-linux*</a>
-</li><li> <a href="#s390x-ibm-tpf">s390x-ibm-tpf*</a>
-</li><li> <a href="#x-x-solaris2">*-*-solaris2*</a>
-</li><li> <a href="#sparc-x-x">sparc*-*-*</a>
-</li><li> <a href="#sparc-sun-solaris2">sparc-sun-solaris2*</a>
-</li><li> <a href="#sparc-sun-solaris210">sparc-sun-solaris2.10</a>
-</li><li> <a href="#sparc-x-linux">sparc-*-linux*</a>
-</li><li> <a href="#sparc64-x-solaris2">sparc64-*-solaris2*</a>
-</li><li> <a href="#sparcv9-x-solaris2">sparcv9-*-solaris2*</a>
-</li><li> <a href="#c6x-x-x">c6x-*-*</a>
-</li><li> <a href="#tilegx-x-linux">tilegx-*-linux*</a>
-</li><li> <a href="#tilegxbe-x-linux">tilegxbe-*-linux*</a>
-</li><li> <a href="#tilepro-x-linux">tilepro-*-linux*</a>
-</li><li> <a href="#x-x-vxworks">*-*-vxworks*</a>
-</li><li> <a href="#x86-64-x-x">x86_64-*-*, amd64-*-*</a>
-</li><li> <a href="#x86-64-x-solaris210">x86_64-*-solaris2.1[0-9]*</a>
-</li><li> <a href="#xtensa-x-elf">xtensa*-*-elf</a>
-</li><li> <a href="#xtensa-x-linux">xtensa*-*-linux*</a>
-</li><li> <a href="#windows">Microsoft Windows</a>
-</li><li> <a href="#x-x-cygwin">*-*-cygwin</a>
-</li><li> <a href="#x-x-interix">*-*-interix</a>
-</li><li> <a href="#x-x-mingw32">*-*-mingw32</a>
-</li><li> <a href="#os2">OS/2</a>
-</li><li> <a href="#older">Older systems</a>
-</li></ul>
-
-<ul>
-<li> <a href="#elf">all ELF targets</a> (SVR4, Solaris 2, etc.)
-</li></ul>
-
-
-<!-- -------- host/target specific issues start here ---------------- -->
-<hr /><a name="alpha_002dx_002dx"></a><a name="alpha_002a_002d_002a_002d_002a"></a>
-<h3 class="heading">alpha*-*-*</h3>
-<p>This section contains general configuration information for all
-alpha-based platforms using ELF (in particular, ignore this section for
-DEC OSF/1, Digital UNIX and Tru64 UNIX). In addition to reading this
-section, please read all other sections that match your target.
-</p>
-<p>We require binutils 2.11.2 or newer.
-Previous binutils releases had a number of problems with DWARF 2
-debugging information, not the least of which is incorrect linking of
-shared libraries.
-</p>
-<hr /><a name="alpha_002ddec_002dosf51"></a><a name="alpha_002a_002ddec_002dosf5_002e1"></a>
-<h3 class="heading">alpha*-dec-osf5.1</h3>
-<p>Systems using processors that implement the DEC Alpha architecture and
-are running the DEC/Compaq/HP Unix (DEC OSF/1, Digital UNIX, or Compaq/HP
-Tru64 UNIX) operating system, for example the DEC Alpha AXP systems.
-</p>
-<p>Support for Tru64 UNIX V5.1 has been removed in GCC 4.8. As of GCC 4.6,
-support for Tru64 UNIX V4.0 and V5.0 has been removed. As of GCC 3.2,
-versions before <code>alpha*-dec-osf4</code> are no longer supported. (These
-are the versions which identify themselves as DEC OSF/1.)
-</p>
-<hr /><a name="amd64_002dx_002dsolaris210"></a><a name="amd64_002d_002a_002dsolaris2_002e1_005b0_002d9_005d_002a"></a>
-<h3 class="heading">amd64-*-solaris2.1[0-9]*</h3>
-<p>This is a synonym for &lsquo;<samp>x86_64-*-solaris2.1[0-9]*</samp>&rsquo;.
-</p>
-<hr /><a name="arc_002dx_002delf32"></a><a name="arc_002d_002a_002delf32"></a>
-<h3 class="heading">arc-*-elf32</h3>
-
-<p>Use &lsquo;<samp>configure --target=arc-elf32 --with-cpu=<var>cpu</var> --enable-languages=&quot;c,c++&quot;</samp>&rsquo;
-to configure GCC, with <var>cpu</var> being one of &lsquo;<samp>arc600</samp>&rsquo;, &lsquo;<samp>arc601</samp>&rsquo;,
-or &lsquo;<samp>arc700</samp>&rsquo;.
-</p>
-<hr /><a name="arc_002dlinux_002duclibc"></a><a name="arc_002dlinux_002duclibc-1"></a>
-<h3 class="heading">arc-linux-uclibc</h3>
-
-<p>Use &lsquo;<samp>configure --target=arc-linux-uclibc --with-cpu=arc700 --enable-languages=&quot;c,c++&quot;</samp>&rsquo; to configure GCC.
-</p>
-<hr /><a name="arm_002dx_002deabi"></a><a name="arm_002d_002a_002deabi"></a>
-<h3 class="heading">arm-*-eabi</h3>
-<p>ARM-family processors. Subtargets that use the ELF object format
-require GNU binutils 2.13 or newer. Such subtargets include:
-<code>arm-*-netbsdelf</code>, <code>arm-*-*linux-*</code>
-and <code>arm-*-rtemseabi</code>.
-</p>
-<hr /><a name="avr"></a><a name="avr-1"></a>
-<h3 class="heading">avr</h3>
-<p>ATMEL AVR-family micro controllers. These are used in embedded
-applications. There are no standard Unix configurations.
-See &ldquo;AVR Options&rdquo; in the main manual
-for the list of supported MCU types.
-</p>
-<p>Use &lsquo;<samp>configure --target=avr --enable-languages=&quot;c&quot;</samp>&rsquo; to configure GCC.
-</p>
-<p>Further installation notes and other useful information about AVR tools
-can also be obtained from:
-</p>
-<ul>
-<li> <a href="http://www.nongnu.org/avr/">http://www.nongnu.org/avr/</a>
-</li><li> <a href="http://www.amelek.gda.pl/avr/">http://www.amelek.gda.pl/avr/</a>
-</li></ul>
-
-<p>We <em>strongly</em> recommend using binutils 2.13 or newer.
-</p>
-<p>The following error:
-</p><div class="smallexample">
-<pre class="smallexample">Error: register required
-</pre></div>
-
-<p>indicates that you should upgrade to a newer version of the binutils.
-</p>
-<hr /><a name="bfin"></a><a name="Blackfin"></a>
-<h3 class="heading">Blackfin</h3>
-<p>The Blackfin processor, an Analog Devices DSP.
-See &ldquo;Blackfin Options&rdquo; in the main manual
-</p>
-<p>More information, and a version of binutils with support for this processor,
-is available at <a href="http://blackfin.uclinux.org">http://blackfin.uclinux.org</a>
-</p>
-<hr /><a name="cr16"></a><a name="CR16"></a>
-<h3 class="heading">CR16</h3>
-<p>The CR16 CompactRISC architecture is a 16-bit architecture. This
-architecture is used in embedded applications.
-</p>
-
-<p>See &ldquo;CR16 Options&rdquo; in the main manual for a list of CR16-specific options.
-</p>
-<p>Use &lsquo;<samp>configure --target=cr16-elf --enable-languages=c,c++</samp>&rsquo; to configure
-GCC&nbsp;for building a CR16 elf cross-compiler.
-</p>
-<p>Use &lsquo;<samp>configure --target=cr16-uclinux --enable-languages=c,c++</samp>&rsquo; to
-configure GCC&nbsp;for building a CR16 uclinux cross-compiler.
-</p>
-<hr /><a name="cris"></a><a name="CRIS"></a>
-<h3 class="heading">CRIS</h3>
-<p>CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
-series. These are used in embedded applications.
-</p>
-<p>See &ldquo;CRIS Options&rdquo; in the main manual
-for a list of CRIS-specific options.
-</p>
-<p>There are a few different CRIS targets:
-</p><dl compact="compact">
-<dt><code>cris-axis-elf</code></dt>
-<dd><p>Mainly for monolithic embedded systems. Includes a multilib for the
-&lsquo;<samp>v10</samp>&rsquo; core used in &lsquo;<samp>ETRAX 100 LX</samp>&rsquo;.
-</p></dd>
-<dt><code>cris-axis-linux-gnu</code></dt>
-<dd><p>A GNU/Linux port for the CRIS architecture, currently targeting
-&lsquo;<samp>ETRAX 100 LX</samp>&rsquo; by default.
-</p></dd>
-</dl>
-
-<p>For <code>cris-axis-elf</code> you need binutils 2.11
-or newer. For <code>cris-axis-linux-gnu</code> you need binutils 2.12 or newer.
-</p>
-<p>Pre-packaged tools can be obtained from
-<a href="ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/">ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/</a>. More
-information about this platform is available at
-<a href="http://developer.axis.com/">http://developer.axis.com/</a>.
-</p>
-<hr /><a name="dos"></a><a name="DOS"></a>
-<h3 class="heading">DOS</h3>
-<p>Please have a look at the <a href="binaries.html">binaries page</a>.
-</p>
-<p>You cannot install GCC by itself on MSDOS; it will not compile under
-any MSDOS compiler except itself. You need to get the complete
-compilation package DJGPP, which includes binaries as well as sources,
-and includes all the necessary compilation tools and libraries.
-</p>
-<hr /><a name="epiphany_002dx_002delf"></a><a name="epiphany_002d_002a_002delf"></a>
-<h3 class="heading">epiphany-*-elf</h3>
-<p>Adapteva Epiphany.
-This configuration is intended for embedded systems.
-</p>
-<hr /><a name="x_002dx_002dfreebsd"></a><a name="g_t_002a_002d_002a_002dfreebsd_002a"></a>
-<h3 class="heading">*-*-freebsd*</h3>
-<p>Support for FreeBSD 1 was discontinued in GCC 3.2. Support for
-FreeBSD 2 (and any mutant a.out variants of FreeBSD 3) was
-discontinued in GCC 4.0.
-</p>
-<p>In order to better utilize FreeBSD base system functionality and match
-the configuration of the system compiler, GCC 4.5 and above as well as
-GCC 4.4 past 2010-06-20 leverage SSP support in libc (which is present
-on FreeBSD 7 or later) and the use of <code>__cxa_atexit</code> by default
-(on FreeBSD 6 or later). The use of <code>dl_iterate_phdr</code> inside
-<samp>libgcc_s.so.1</samp> and boehm-gc (on FreeBSD 7 or later) is enabled
-by GCC 4.5 and above.
-</p>
-<p>We support FreeBSD using the ELF file format with DWARF 2 debugging
-for all CPU architectures. You may use <samp>-gstabs</samp> instead of
-<samp>-g</samp>, if you really want the old debugging format. There are
-no known issues with mixing object files and libraries with different
-debugging formats. Otherwise, this release of GCC should now match
-more of the configuration used in the stock FreeBSD configuration of
-GCC. In particular, <samp>--enable-threads</samp> is now configured by
-default. However, as a general user, do not attempt to replace the
-system compiler with this release. Known to bootstrap and check with
-good results on FreeBSD 7.2-STABLE. 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, 4.9 and 5-CURRENT.
-</p>
-<p>The version of binutils installed in <samp>/usr/bin</samp> probably works
-with this release of GCC. Bootstrapping against the latest GNU
-binutils and/or the version found in <samp>/usr/ports/devel/binutils</samp> has
-been known to enable additional features and improve overall testsuite
-results. However, it is currently known that boehm-gc (which itself
-is required for java) may not configure properly on FreeBSD prior to
-the FreeBSD 7.0 release with GNU binutils after 2.16.1.
-</p>
-<hr /><a name="h8300_002dhms"></a><a name="h8300_002dhms-1"></a>
-<h3 class="heading">h8300-hms</h3>
-<p>Renesas H8/300 series of processors.
-</p>
-<p>Please have a look at the <a href="binaries.html">binaries page</a>.
-</p>
-<p>The calling convention and structure layout has changed in release 2.6.
-All code must be recompiled. The calling convention now passes the
-first three arguments in function calls in registers. Structures are no
-longer a multiple of 2 bytes.
-</p>
-<hr /><a name="hppa_002dhp_002dhpux"></a><a name="hppa_002a_002dhp_002dhpux_002a"></a>
-<h3 class="heading">hppa*-hp-hpux*</h3>
-<p>Support for HP-UX version 9 and older was discontinued in GCC 3.4.
-</p>
-<p>We require using gas/binutils on all hppa platforms. Version 2.19 or
-later is recommended.
-</p>
-<p>It may be helpful to configure GCC with the
-<a href="./configure.html#with-gnu-as"><samp>--with-gnu-as</samp></a> and
-<samp>--with-as=&hellip;</samp> options to ensure that GCC can find GAS.
-</p>
-<p>The HP assembler should not be used with GCC. It is rarely tested and may
-not work. It shouldn&rsquo;t be used with any languages other than C due to its
-many limitations.
-</p>
-<p>Specifically, <samp>-g</samp> does not work (HP-UX uses a peculiar debugging
-format which GCC does not know about). It also inserts timestamps
-into each object file it creates, causing the 3-stage comparison test to
-fail during a bootstrap. You should be able to continue by saying
-&lsquo;<samp>make all-host all-target</samp>&rsquo; after getting the failure from &lsquo;<samp>make</samp>&rsquo;.
-</p>
-<p>Various GCC features are not supported. For example, it does not support weak
-symbols or alias definitions. As a result, explicit template instantiations
-are required when using C++. This makes it difficult if not impossible to
-build many C++ applications.
-</p>
-<p>There are two default scheduling models for instructions. These are
-PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
-architecture specified for the target machine when configuring.
-PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
-the target is a &lsquo;<samp>hppa1*</samp>&rsquo; machine.
-</p>
-<p>The PROCESSOR_8000 model is not well suited to older processors. Thus,
-it is important to completely specify the machine architecture when
-configuring if you want a model other than PROCESSOR_8000. The macro
-TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
-default scheduling model is desired.
-</p>
-<p>As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
-through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
-This namespace change might cause problems when bootstrapping with
-an earlier version of GCC or the HP compiler as essentially the same
-namespace is required for an entire build. This problem can be avoided
-in a number of ways. With HP cc, <code>UNIX_STD</code> can be set to &lsquo;<samp>95</samp>&rsquo;
-or &lsquo;<samp>98</samp>&rsquo;. Another way is to add an appropriate set of predefines
-to <code>CC</code>. The description for the <samp>munix=</samp> option contains
-a list of the predefines used with each standard.
-</p>
-<p>More specific information to &lsquo;<samp>hppa*-hp-hpux*</samp>&rsquo; targets follows.
-</p>
-<hr /><a name="hppa_002dhp_002dhpux10"></a><a name="hppa_002a_002dhp_002dhpux10"></a>
-<h3 class="heading">hppa*-hp-hpux10</h3>
-<p>For hpux10.20, we <em>highly</em> recommend you pick up the latest sed patch
-<code>PHCO_19798</code> from HP.
-</p>
-<p>The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
-used for one-only code and data. This resolves many of the previous
-problems in using C++ on this target. However, the ABI is not compatible
-with the one implemented under HP-UX 11 using secondary definitions.
-</p>
-<hr /><a name="hppa_002dhp_002dhpux11"></a><a name="hppa_002a_002dhp_002dhpux11"></a>
-<h3 class="heading">hppa*-hp-hpux11</h3>
-<p>GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
-be used to compile GCC 3.0 and up.
-</p>
-<p>The libffi and libjava libraries haven&rsquo;t been ported to 64-bit HP-UX&nbsp;and don&rsquo;t build.
-</p>
-<p>Refer to <a href="binaries.html">binaries</a> for information about obtaining
-precompiled GCC binaries for HP-UX. Precompiled binaries must be obtained
-to build the Ada language as it can&rsquo;t be bootstrapped using C. Ada is
-only available for the 32-bit PA-RISC runtime.
-</p>
-<p>Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
-bundled compiler supports only traditional C; you will need either HP&rsquo;s
-unbundled compiler, or a binary distribution of GCC.
-</p>
-<p>It is possible to build GCC 3.3 starting with the bundled HP compiler,
-but the process requires several steps. GCC 3.3 can then be used to
-build later versions. The fastjar program contains ISO C code and
-can&rsquo;t be built with the HP bundled compiler. This problem can be
-avoided by not building the Java language. For example, use the
-<samp>--enable-languages=&quot;c,c++,f77,objc&quot;</samp> option in your configure
-command.
-</p>
-<p>There are several possible approaches to building the distribution.
-Binutils can be built first using the HP tools. Then, the GCC
-distribution can be built. The second approach is to build GCC
-first using the HP tools, then build binutils, then rebuild GCC.
-There have been problems with various binary distributions, so it
-is best not to start from a binary distribution.
-</p>
-<p>On 64-bit capable systems, there are two distinct targets. Different
-installation prefixes must be used if both are to be installed on
-the same system. The &lsquo;<samp>hppa[1-2]*-hp-hpux11*</samp>&rsquo; target generates code
-for the 32-bit PA-RISC runtime architecture and uses the HP linker.
-The &lsquo;<samp>hppa64-hp-hpux11*</samp>&rsquo; target generates 64-bit code for the
-PA-RISC 2.0 architecture.
-</p>
-<p>The script config.guess now selects the target type based on the compiler
-detected during configuration. You must define <code>PATH</code> or <code>CC</code> so
-that configure finds an appropriate compiler for the initial bootstrap.
-When <code>CC</code> is used, the definition should contain the options that are
-needed whenever <code>CC</code> is used.
-</p>
-<p>Specifically, options that determine the runtime architecture must be
-in <code>CC</code> to correctly select the target for the build. It is also
-convenient to place many other compiler options in <code>CC</code>. For example,
-<code>CC=&quot;cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE&quot;</code>
-can be used to bootstrap the GCC 3.3 branch with the HP compiler in
-64-bit K&amp;R/bundled mode. The <samp>+DA2.0W</samp> option will result in
-the automatic selection of the &lsquo;<samp>hppa64-hp-hpux11*</samp>&rsquo; target. The
-macro definition table of cpp needs to be increased for a successful
-build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
-be defined when building with the bundled compiler, or when using the
-<samp>-Ac</samp> option. These defines aren&rsquo;t necessary with <samp>-Ae</samp>.
-</p>
-<p>It is best to explicitly configure the &lsquo;<samp>hppa64-hp-hpux11*</samp>&rsquo; target
-with the <samp>--with-ld=&hellip;</samp> option. This overrides the standard
-search for ld. The two linkers supported on this target require different
-commands. The default linker is determined during configuration. As a
-result, it&rsquo;s not possible to switch linkers in the middle of a GCC build.
-This has been reported to sometimes occur in unified builds of binutils
-and GCC.
-</p>
-<p>A recent linker patch must be installed for the correct operation of
-GCC 3.3 and later. <code>PHSS_26559</code> and <code>PHSS_24304</code> are the
-oldest linker patches that are known to work. They are for HP-UX
-11.00 and 11.11, respectively. <code>PHSS_24303</code>, the companion to
-<code>PHSS_24304</code>, might be usable but it hasn&rsquo;t been tested. These
-patches have been superseded. Consult the HP patch database to obtain
-the currently recommended linker patch for your system.
-</p>
-<p>The patches are necessary for the support of weak symbols on the
-32-bit port, and for the running of initializers and finalizers. Weak
-symbols are implemented using SOM secondary definition symbols. Prior
-to HP-UX 11, there are bugs in the linker support for secondary symbols.
-The patches correct a problem of linker core dumps creating shared
-libraries containing secondary symbols, as well as various other
-linking issues involving secondary symbols.
-</p>
-<p>GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
-run initializers and finalizers on the 64-bit port. The 32-bit port
-uses the linker <samp>+init</samp> and <samp>+fini</samp> options for the same
-purpose. The patches correct various problems with the +init/+fini
-options, including program core dumps. Binutils 2.14 corrects a
-problem on the 64-bit port resulting from HP&rsquo;s non-standard use of
-the .init and .fini sections for array initializers and finalizers.
-</p>
-<p>Although the HP and GNU linkers are both supported for the
-&lsquo;<samp>hppa64-hp-hpux11*</samp>&rsquo; target, it is strongly recommended that the
-HP linker be used for link editing on this target.
-</p>
-<p>At this time, the GNU linker does not support the creation of long
-branch stubs. As a result, it can&rsquo;t successfully link binaries
-containing branch offsets larger than 8 megabytes. In addition,
-there are problems linking shared libraries, linking executables
-with <samp>-static</samp>, and with dwarf2 unwind and exception support.
-It also doesn&rsquo;t provide stubs for internal calls to global functions
-in shared libraries, so these calls can&rsquo;t be overloaded.
-</p>
-<p>The HP dynamic loader does not support GNU symbol versioning, so symbol
-versioning is not supported. It may be necessary to disable symbol
-versioning with <samp>--disable-symvers</samp> when using GNU ld.
-</p>
-<p>POSIX threads are the default. The optional DCE thread library is not
-supported, so <samp>--enable-threads=dce</samp> does not work.
-</p>
-<hr /><a name="x_002dx_002dlinux_002dgnu"></a><a name="g_t_002a_002d_002a_002dlinux_002dgnu"></a>
-<h3 class="heading">*-*-linux-gnu</h3>
-<p>Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
-in glibc 2.2.5 and later. More information is available in the
-libstdc++-v3 documentation.
-</p>
-<hr /><a name="ix86_002dx_002dlinux"></a><a name="i_003f86_002d_002a_002dlinux_002a"></a>
-<h3 class="heading">i?86-*-linux*</h3>
-<p>As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
-See <a href="http://gcc.gnu.org/PR10877">bug 10877</a> for more information.
-</p>
-<p>If you receive Signal 11 errors when building on GNU/Linux, then it is
-possible you have a hardware problem. Further information on this can be
-found on <a href="http://www.bitwizard.nl/sig11/">www.bitwizard.nl</a>.
-</p>
-<hr /><a name="ix86_002dx_002dsolaris29"></a><a name="i_003f86_002d_002a_002dsolaris2_002e9"></a>
-<h3 class="heading">i?86-*-solaris2.9</h3>
-<p>The Sun assembler in Solaris 9 has several bugs and limitations.
-While GCC works around them, several features are missing, so it is
-recommended to use the GNU assembler instead. There is no bundled
-version, but the current version, from GNU binutils 2.22, is known to
-work.
-</p>
-<p>Solaris&nbsp;2/x86 doesn&rsquo;t support the execution of SSE/SSE2 instructions
-before Solaris&nbsp;9 4/04, even if the CPU supports them. Programs will
-receive <code>SIGILL</code> if they try. The fix is available both in
-Solaris&nbsp;9 Update&nbsp;6 and kernel patch 112234-12 or newer. To
-avoid this problem,
-<samp>-march</samp> defaults to &lsquo;<samp>pentiumpro</samp>&rsquo; on Solaris 9. If
-you have the patch installed, you can configure GCC with an appropriate
-<samp>--with-arch</samp> option, but need GNU <code>as</code> for SSE2 support.
-</p>
-<hr /><a name="ix86_002dx_002dsolaris210"></a><a name="i_003f86_002d_002a_002dsolaris2_002e10"></a>
-<h3 class="heading">i?86-*-solaris2.10</h3>
-<p>Use this for Solaris 10 or later on x86 and x86-64 systems. Starting
-with GCC 4.7, there is also a 64-bit &lsquo;<samp>amd64-*-solaris2.1[0-9]*</samp>&rsquo; or
-&lsquo;<samp>x86_64-*-solaris2.1[0-9]*</samp>&rsquo; configuration that corresponds to
-&lsquo;<samp>sparcv9-sun-solaris2*</samp>&rsquo;.
-</p>
-<p>It is recommended that you configure GCC to use the GNU assembler, in
-<samp>/usr/sfw/bin/gas</samp>. The versions included in Solaris 10, from GNU
-binutils 2.15, and Solaris 11, from GNU binutils 2.19, work fine,
-although the current version, from GNU binutils
-2.22, is known to work, too. Recent versions of the Sun assembler in
-<samp>/usr/ccs/bin/as</samp> work almost as well, though.
-</p>
-<p>For linking, the Sun linker, is preferred. If you want to use the GNU
-linker instead, which is available in <samp>/usr/sfw/bin/gld</samp>, note that
-due to a packaging bug the version in Solaris 10, from GNU binutils
-2.15, cannot be used, while the version in Solaris 11, from GNU binutils
-2.19, works, as does the latest version, from GNU binutils 2.22.
-</p>
-<p>To use GNU <code>as</code>, configure with the options
-<samp>--with-gnu-as --with-as=/usr/sfw/bin/gas</samp>. It may be necessary
-to configure with <samp>--without-gnu-ld --with-ld=/usr/ccs/bin/ld</samp> to
-guarantee use of Sun <code>ld</code>.
-</p>
-<hr /><a name="ia64_002dx_002dlinux"></a><a name="ia64_002d_002a_002dlinux"></a>
-<h3 class="heading">ia64-*-linux</h3>
-<p>IA-64 processor (also known as IPF, or Itanium Processor Family)
-running GNU/Linux.
-</p>
-<p>If you are using the installed system libunwind library with
-<samp>--with-system-libunwind</samp>, then you must use libunwind 0.98 or
-later.
-</p>
-<p>None of the following versions of GCC has an ABI that is compatible
-with any of the other versions in this list, with the exception that
-Red Hat 2.96 and Trillian 000171 are compatible with each other:
-3.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
-This primarily affects C++ programs and programs that create shared libraries.
-GCC 3.1 or later is recommended for compiling linux, the kernel.
-As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
-more major ABI changes are expected.
-</p>
-<hr /><a name="ia64_002dx_002dhpux"></a><a name="ia64_002d_002a_002dhpux_002a"></a>
-<h3 class="heading">ia64-*-hpux*</h3>
-<p>Building GCC on this target requires the GNU Assembler. The bundled HP
-assembler will not work. To prevent GCC from using the wrong assembler,
-the option <samp>--with-gnu-as</samp> may be necessary.
-</p>
-<p>The GCC libunwind library has not been ported to HPUX. This means that for
-GCC versions 3.2.3 and earlier, <samp>--enable-libunwind-exceptions</samp>
-is required to build GCC. For GCC 3.3 and later, this is the default.
-For gcc 3.4.3 and later, <samp>--enable-libunwind-exceptions</samp> is
-removed and the system libunwind library will always be used.
-</p>
-<hr /><a name="aarch64_002dx_002dx"></a><a name="aarch64_002a_002d_002a_002d_002a"></a>
-<h3 class="heading">aarch64*-*-*</h3>
-<p>Pre 2.24 binutils does not have support for selecting -mabi and does not
-support ILP32. If GCC 4.9 or later is built with pre 2.24, GCC will not
-support option -mabi=ilp32.
-</p>
-<hr />
-<!-- rs6000-ibm-aix*, powerpc-ibm-aix* --><a name="x_002dibm_002daix"></a><a name="g_t_002a_002dibm_002daix_002a"></a>
-<h3 class="heading">*-ibm-aix*</h3>
-<p>Support for AIX version 3 and older was discontinued in GCC 3.4.
-Support for AIX version 4.2 and older was discontinued in GCC 4.5.
-</p>
-<p>&ldquo;out of memory&rdquo; bootstrap failures may indicate a problem with
-process resource limits (ulimit). Hard limits are configured in the
-<samp>/etc/security/limits</samp> system configuration file.
-</p>
-<p>GCC can bootstrap with recent versions of IBM XLC, but bootstrapping
-with an earlier release of GCC is recommended. Bootstrapping with XLC
-requires a larger data segment, which can be enabled through the
-<var>LDR_CNTRL</var> environment variable, e.g.,
-</p>
-<div class="smallexample">
-<pre class="smallexample">% LDR_CNTRL=MAXDATA=0x50000000
-% export LDR_CNTRL
-</pre></div>
-
-<p>One can start with a pre-compiled version of GCC to build from
-sources. One may delete GCC&rsquo;s &ldquo;fixed&rdquo; header files when starting
-with a version of GCC built for an earlier release of AIX.
-</p>
-<p>To speed up the configuration phases of bootstrapping and installing GCC,
-one may use GNU Bash instead of AIX <code>/bin/sh</code>, e.g.,
-</p>
-<div class="smallexample">
-<pre class="smallexample">% CONFIG_SHELL=/opt/freeware/bin/bash
-% export CONFIG_SHELL
-</pre></div>
-
-<p>and then proceed as described in <a href="build.html">the build
-instructions</a>, where we strongly recommend specifying an absolute path
-to invoke <var>srcdir</var>/configure.
-</p>
-<p>Because GCC on AIX is built as a 32-bit executable by default,
-(although it can generate 64-bit programs) the GMP and MPFR libraries
-required by gfortran must be 32-bit libraries. Building GMP and MPFR
-as static archive libraries works better than shared libraries.
-</p>
-<p>Errors involving <code>alloca</code> when building GCC generally are due
-to an incorrect definition of <code>CC</code> in the Makefile or mixing files
-compiled with the native C compiler and GCC. During the stage1 phase of
-the build, the native AIX compiler <strong>must</strong> be invoked as <code>cc</code>
-(not <code>xlc</code>). Once <code>configure</code> has been informed of
-<code>xlc</code>, one needs to use &lsquo;<samp>make distclean</samp>&rsquo; to remove the
-configure cache files and ensure that <code>CC</code> environment variable
-does not provide a definition that will confuse <code>configure</code>.
-If this error occurs during stage2 or later, then the problem most likely
-is the version of Make (see above).
-</p>
-<p>The native <code>as</code> and <code>ld</code> are recommended for
-bootstrapping on AIX. The GNU Assembler, GNU Linker, and GNU
-Binutils version 2.20 is the minimum level that supports bootstrap on
-AIX 5. The GNU Assembler has not been updated to support AIX 6&nbsp;or
-AIX 7. The native AIX tools do interoperate with GCC.
-</p>
-<p>AIX 5.3 TL10, AIX 6.1 TL05 and AIX 7.1 TL00 introduced an AIX
-assembler change that sometimes produces corrupt assembly files
-causing AIX linker errors. The bug breaks GCC bootstrap on AIX and
-can cause compilation failures with existing GCC installations. An
-AIX iFix for AIX 5.3 is available (APAR IZ98385 for AIX 5.3 TL10, APAR
-IZ98477 for AIX 5.3 TL11 and IZ98134 for AIX 5.3 TL12). AIX 5.3 TL11 SP8,
-AIX 5.3 TL12 SP5, AIX 6.1 TL04 SP11, AIX 6.1 TL05 SP7, AIX 6.1 TL06 SP6,
-AIX 6.1 TL07 and AIX 7.1 TL01 should include the fix.
-</p>
-<p>Building <samp>libstdc++.a</samp> requires a fix for an AIX Assembler bug
-APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
-fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
-referenced as APAR IY53606 (AIX 5.2) or as APAR IY54774 (AIX 5.1)
-</p>
-<p>&lsquo;<samp>libstdc++</samp>&rsquo; in GCC 3.4 increments the major version number of the
-shared object and GCC installation places the <samp>libstdc++.a</samp>
-shared library in a common location which will overwrite the and GCC
-3.3 version of the shared library. Applications either need to be
-re-linked against the new shared library or the GCC 3.1 and GCC 3.3
-versions of the &lsquo;<samp>libstdc++</samp>&rsquo; shared object needs to be available
-to the AIX runtime loader. The GCC 3.1 &lsquo;<samp>libstdc++.so.4</samp>&rsquo;, if
-present, and GCC 3.3 &lsquo;<samp>libstdc++.so.5</samp>&rsquo; shared objects can be
-installed for runtime dynamic loading using the following steps to set
-the &lsquo;<samp>F_LOADONLY</samp>&rsquo; flag in the shared object for <em>each</em>
-multilib <samp>libstdc++.a</samp> installed:
-</p>
-<p>Extract the shared objects from the currently installed
-<samp>libstdc++.a</samp> archive:
-</p><div class="smallexample">
-<pre class="smallexample">% ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
-</pre></div>
-
-<p>Enable the &lsquo;<samp>F_LOADONLY</samp>&rsquo; flag so that the shared object will be
-available for runtime dynamic loading, but not linking:
-</p><div class="smallexample">
-<pre class="smallexample">% strip -e libstdc++.so.4 libstdc++.so.5
-</pre></div>
-
-<p>Archive the runtime-only shared object in the GCC 3.4
-<samp>libstdc++.a</samp> archive:
-</p><div class="smallexample">
-<pre class="smallexample">% ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
-</pre></div>
-
-<p>Linking executables and shared libraries may produce warnings of
-duplicate symbols. The assembly files generated by GCC for AIX always
-have included multiple symbol definitions for certain global variable
-and function declarations in the original program. The warnings should
-not prevent the linker from producing a correct library or runnable
-executable.
-</p>
-<p>AIX 4.3 utilizes a &ldquo;large format&rdquo; archive to support both 32-bit and
-64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1
-to parse archive libraries did not handle the new format correctly.
-These routines are used by GCC and result in error messages during
-linking such as &ldquo;not a COFF file&rdquo;. The version of the routines shipped
-with AIX 4.3.1 should work for a 32-bit environment. The <samp>-g</samp>
-option of the archive command may be used to create archives of 32-bit
-objects using the original &ldquo;small format&rdquo;. A correct version of the
-routines is shipped with AIX 4.3.2 and above.
-</p>
-<p>Some versions of the AIX binder (linker) can fail with a relocation
-overflow severe error when the <samp>-bbigtoc</samp> option is used to link
-GCC-produced object files into an executable that overflows the TOC. A fix
-for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is
-available from IBM Customer Support and from its
-<a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
-website as PTF U455193.
-</p>
-<p>The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core
-with a segmentation fault when invoked by any version of GCC. A fix for
-APAR IX87327 is available from IBM Customer Support and from its
-<a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
-website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above.
-</p>
-<p>The initial assembler shipped with AIX 4.3.0 generates incorrect object
-files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS
-TO ASSEMBLE/BIND) is available from IBM Customer Support and from its
-<a href="http://techsupport.services.ibm.com/">techsupport.services.ibm.com</a>
-website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above.
-</p>
-<p>AIX provides National Language Support (NLS). Compilers and assemblers
-use NLS to support locale-specific representations of various data
-formats including floating-point numbers (e.g., &lsquo;<samp>.</samp>&rsquo; vs &lsquo;<samp>,</samp>&rsquo; for
-separating decimal fractions). There have been problems reported where
-GCC does not produce the same floating-point formats that the assembler
-expects. If one encounters this problem, set the <code>LANG</code>
-environment variable to &lsquo;<samp>C</samp>&rsquo; or &lsquo;<samp>En_US</samp>&rsquo;.
-</p>
-<p>A default can be specified with the <samp>-mcpu=<var>cpu_type</var></samp>
-switch and using the configure option <samp>--with-cpu-<var>cpu_type</var></samp>.
-</p>
-<hr /><a name="iq2000_002dx_002delf"></a><a name="iq2000_002d_002a_002delf"></a>
-<h3 class="heading">iq2000-*-elf</h3>
-<p>Vitesse IQ2000 processors. These are used in embedded
-applications. There are no standard Unix configurations.
-</p>
-<hr /><a name="lm32_002dx_002delf"></a><a name="lm32_002d_002a_002delf"></a>
-<h3 class="heading">lm32-*-elf</h3>
-<p>Lattice Mico32 processor.
-This configuration is intended for embedded systems.
-</p>
-<hr /><a name="lm32_002dx_002duclinux"></a><a name="lm32_002d_002a_002duclinux"></a>
-<h3 class="heading">lm32-*-uclinux</h3>
-<p>Lattice Mico32 processor.
-This configuration is intended for embedded systems running uClinux.
-</p>
-<hr /><a name="m32c_002dx_002delf"></a><a name="m32c_002d_002a_002delf"></a>
-<h3 class="heading">m32c-*-elf</h3>
-<p>Renesas M32C processor.
-This configuration is intended for embedded systems.
-</p>
-<hr /><a name="m32r_002dx_002delf"></a><a name="m32r_002d_002a_002delf"></a>
-<h3 class="heading">m32r-*-elf</h3>
-<p>Renesas M32R processor.
-This configuration is intended for embedded systems.
-</p>
-<hr /><a name="m68k_002dx_002dx"></a><a name="m68k_002d_002a_002d_002a"></a>
-<h3 class="heading">m68k-*-*</h3>
-<p>By default,
-&lsquo;<samp>m68k-*-elf*</samp>&rsquo;, &lsquo;<samp>m68k-*-rtems</samp>&rsquo;, &lsquo;<samp>m68k-*-uclinux</samp>&rsquo; and
-&lsquo;<samp>m68k-*-linux</samp>&rsquo;
-build libraries for both M680x0 and ColdFire processors. If you only
-need the M680x0 libraries, you can omit the ColdFire ones by passing
-<samp>--with-arch=m68k</samp> to <code>configure</code>. Alternatively, you
-can omit the M680x0 libraries by passing <samp>--with-arch=cf</samp> to
-<code>configure</code>. These targets default to 5206 or 5475 code as
-appropriate for the target system when
-configured with <samp>--with-arch=cf</samp> and 68020 code otherwise.
-</p>
-<p>The &lsquo;<samp>m68k-*-netbsd</samp>&rsquo; and
-&lsquo;<samp>m68k-*-openbsd</samp>&rsquo; targets also support the <samp>--with-arch</samp>
-option. They will generate ColdFire CFV4e code when configured with
-<samp>--with-arch=cf</samp> and 68020 code otherwise.
-</p>
-<p>You can override the default processors listed above by configuring
-with <samp>--with-cpu=<var>target</var></samp>. This <var>target</var> can either
-be a <samp>-mcpu</samp> argument or one of the following values:
-&lsquo;<samp>m68000</samp>&rsquo;, &lsquo;<samp>m68010</samp>&rsquo;, &lsquo;<samp>m68020</samp>&rsquo;, &lsquo;<samp>m68030</samp>&rsquo;,
-&lsquo;<samp>m68040</samp>&rsquo;, &lsquo;<samp>m68060</samp>&rsquo;, &lsquo;<samp>m68020-40</samp>&rsquo; and &lsquo;<samp>m68020-60</samp>&rsquo;.
-</p>
-<p>GCC requires at least binutils version 2.17 on these targets.
-</p>
-<hr /><a name="m68k_002dx_002duclinux"></a><a name="m68k_002d_002a_002duclinux"></a>
-<h3 class="heading">m68k-*-uclinux</h3>
-<p>GCC 4.3 changed the uClinux configuration so that it uses the
-&lsquo;<samp>m68k-linux-gnu</samp>&rsquo; ABI rather than the &lsquo;<samp>m68k-elf</samp>&rsquo; ABI.
-It also added improved support for C++ and flat shared libraries,
-both of which were ABI changes.
-</p>
-<hr /><a name="mep_002dx_002delf"></a><a name="mep_002d_002a_002delf"></a>
-<h3 class="heading">mep-*-elf</h3>
-<p>Toshiba Media embedded Processor.
-This configuration is intended for embedded systems.
-</p>
-<hr /><a name="microblaze_002dx_002delf"></a><a name="microblaze_002d_002a_002delf"></a>
-<h3 class="heading">microblaze-*-elf</h3>
-<p>Xilinx MicroBlaze processor.
-This configuration is intended for embedded systems.
-</p>
-<hr /><a name="mips_002dx_002dx"></a><a name="mips_002d_002a_002d_002a"></a>
-<h3 class="heading">mips-*-*</h3>
-<p>If on a MIPS system you get an error message saying &ldquo;does not have gp
-sections for all it&rsquo;s [sic] sectons [sic]&rdquo;, don&rsquo;t worry about it. This
-happens whenever you use GAS with the MIPS linker, but there is not
-really anything wrong, and it is okay to use the output file. You can
-stop such warnings by installing the GNU linker.
-</p>
-<p>It would be nice to extend GAS to produce the gp tables, but they are
-optional, and there should not be a warning about their absence.
-</p>
-<p>The libstdc++ atomic locking routines for MIPS targets requires MIPS II
-and later. A patch went in just after the GCC 3.3 release to
-make &lsquo;<samp>mips*-*-*</samp>&rsquo; use the generic implementation instead. You can also
-configure for &lsquo;<samp>mipsel-elf</samp>&rsquo; as a workaround. The
-&lsquo;<samp>mips*-*-linux*</samp>&rsquo; target continues to use the MIPS II routines. More
-work on this is expected in future releases.
-</p>
-
-<p>The built-in <code>__sync_*</code> functions are available on MIPS II and
-later systems and others that support the &lsquo;<samp>ll</samp>&rsquo;, &lsquo;<samp>sc</samp>&rsquo; and
-&lsquo;<samp>sync</samp>&rsquo; instructions. This can be overridden by passing
-<samp>--with-llsc</samp> or <samp>--without-llsc</samp> when configuring GCC.
-Since the Linux kernel emulates these instructions if they are
-missing, the default for &lsquo;<samp>mips*-*-linux*</samp>&rsquo; targets is
-<samp>--with-llsc</samp>. The <samp>--with-llsc</samp> and
-<samp>--without-llsc</samp> configure options may be overridden at compile
-time by passing the <samp>-mllsc</samp> or <samp>-mno-llsc</samp> options to
-the compiler.
-</p>
-<p>MIPS systems check for division by zero (unless
-<samp>-mno-check-zero-division</samp> is passed to the compiler) by
-generating either a conditional trap or a break instruction. Using
-trap results in smaller code, but is only supported on MIPS II and
-later. Also, some versions of the Linux kernel have a bug that
-prevents trap from generating the proper signal (<code>SIGFPE</code>). To enable
-the use of break, use the <samp>--with-divide=breaks</samp>
-<code>configure</code> option when configuring GCC. The default is to
-use traps on systems that support them.
-</p>
-<p>The assembler from GNU binutils 2.17 and earlier has a bug in the way
-it sorts relocations for REL targets (o32, o64, EABI). This can cause
-bad code to be generated for simple C++ programs. Also the linker
-from GNU binutils versions prior to 2.17 has a bug which causes the
-runtime linker stubs in very large programs, like <samp>libgcj.so</samp>, to
-be incorrectly generated. GNU Binutils 2.18 and later (and snapshots
-made after Nov. 9, 2006) should be free from both of these problems.
-</p>
-<hr /><a name="mips_002dsgi_002dirix5"></a><a name="mips_002dsgi_002dirix5-1"></a>
-<h3 class="heading">mips-sgi-irix5</h3>
-<p>Support for IRIX 5 has been removed in GCC 4.6.
-</p>
-<hr /><a name="mips_002dsgi_002dirix6"></a><a name="mips_002dsgi_002dirix6-1"></a>
-<h3 class="heading">mips-sgi-irix6</h3>
-<p>Support for IRIX 6.5 has been removed in GCC 4.8. Support for IRIX 6
-releases before 6.5 has been removed in GCC 4.6, as well as support for
-the O32 ABI.
-</p>
-<hr /><a name="moxie_002dx_002delf"></a><a name="moxie_002d_002a_002delf"></a>
-<h3 class="heading">moxie-*-elf</h3>
-<p>The moxie processor.
-</p>
-<hr /><a name="msp430_002dx_002delf"></a><a name="msp430_002d_002a_002delf"></a>
-<h3 class="heading">msp430-*-elf</h3>
-<p>TI MSP430 processor.
-This configuration is intended for embedded systems.
-</p>
-<hr /><a name="nds32le_002dx_002delf"></a><a name="nds32le_002d_002a_002delf"></a>
-<h3 class="heading">nds32le-*-elf</h3>
-<p>Andes NDS32 target in little endian mode.
-</p>
-<hr /><a name="nds32be_002dx_002delf"></a><a name="nds32be_002d_002a_002delf"></a>
-<h3 class="heading">nds32be-*-elf</h3>
-<p>Andes NDS32 target in big endian mode.
-</p>
-<hr /><a name="powerpc_002dx_002dx"></a><a name="powerpc_002d_002a_002d_002a"></a>
-<h3 class="heading">powerpc-*-*</h3>
-<p>You can specify a default version for the <samp>-mcpu=<var>cpu_type</var></samp>
-switch by using the configure option <samp>--with-cpu-<var>cpu_type</var></samp>.
-</p>
-<p>You will need
-<a href="ftp://ftp.kernel.org/pub/linux/devel/binutils">binutils 2.15</a>
-or newer for a working GCC.
-</p>
-<hr /><a name="powerpc_002dx_002ddarwin"></a><a name="powerpc_002d_002a_002ddarwin_002a"></a>
-<h3 class="heading">powerpc-*-darwin*</h3>
-<p>PowerPC running Darwin (Mac OS X kernel).
-</p>
-<p>Pre-installed versions of Mac OS X may not include any developer tools,
-meaning that you will not be able to build GCC from source. Tool
-binaries are available at
-<a href="http://opensource.apple.com/">http://opensource.apple.com/</a>.
-</p>
-<p>This version of GCC requires at least cctools-590.36. The
-cctools-590.36 package referenced from
-<a href="http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html">http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html</a> will not work
-on systems older than 10.3.9 (aka darwin7.9.0).
-</p>
-<hr /><a name="powerpc_002dx_002delf"></a><a name="powerpc_002d_002a_002delf"></a>
-<h3 class="heading">powerpc-*-elf</h3>
-<p>PowerPC system in big endian mode, running System V.4.
-</p>
-<hr /><a name="powerpc_002dx_002dlinux_002dgnu"></a><a name="powerpc_002a_002d_002a_002dlinux_002dgnu_002a"></a>
-<h3 class="heading">powerpc*-*-linux-gnu*</h3>
-<p>PowerPC system in big endian mode running Linux.
-</p>
-<hr /><a name="powerpc_002dx_002dnetbsd"></a><a name="powerpc_002d_002a_002dnetbsd_002a"></a>
-<h3 class="heading">powerpc-*-netbsd*</h3>
-<p>PowerPC system in big endian mode running NetBSD.
-</p>
-<hr /><a name="powerpc_002dx_002deabisim"></a><a name="powerpc_002d_002a_002deabisim"></a>
-<h3 class="heading">powerpc-*-eabisim</h3>
-<p>Embedded PowerPC system in big endian mode for use in running under the
-PSIM simulator.
-</p>
-<hr /><a name="powerpc_002dx_002deabi"></a><a name="powerpc_002d_002a_002deabi"></a>
-<h3 class="heading">powerpc-*-eabi</h3>
-<p>Embedded PowerPC system in big endian mode.
-</p>
-<hr /><a name="powerpcle_002dx_002delf"></a><a name="powerpcle_002d_002a_002delf"></a>
-<h3 class="heading">powerpcle-*-elf</h3>
-<p>PowerPC system in little endian mode, running System V.4.
-</p>
-<hr /><a name="powerpcle_002dx_002deabisim"></a><a name="powerpcle_002d_002a_002deabisim"></a>
-<h3 class="heading">powerpcle-*-eabisim</h3>
-<p>Embedded PowerPC system in little endian mode for use in running under
-the PSIM simulator.
-</p>
-<hr /><a name="powerpcle_002dx_002deabi"></a><a name="powerpcle_002d_002a_002deabi"></a>
-<h3 class="heading">powerpcle-*-eabi</h3>
-<p>Embedded PowerPC system in little endian mode.
-</p>
-<hr /><a name="rl78_002dx_002delf"></a><a name="rl78_002d_002a_002delf"></a>
-<h3 class="heading">rl78-*-elf</h3>
-<p>The Renesas RL78 processor.
-This configuration is intended for embedded systems.
-</p>
-<hr /><a name="rx_002dx_002delf"></a><a name="rx_002d_002a_002delf"></a>
-<h3 class="heading">rx-*-elf</h3>
-<p>The Renesas RX processor. See
-<a href="http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&amp;fp=/products/mpumcu/rx_family/rx600_series">http://eu.renesas.com/fmwk.jsp?cnt=rx600_series_landing.jsp&amp;fp=/products/mpumcu/rx_family/rx600_series</a>
-for more information about this processor.
-</p>
-<hr /><a name="s390_002dx_002dlinux"></a><a name="s390_002d_002a_002dlinux_002a"></a>
-<h3 class="heading">s390-*-linux*</h3>
-<p>S/390 system running GNU/Linux for S/390.
-</p>
-<hr /><a name="s390x_002dx_002dlinux"></a><a name="s390x_002d_002a_002dlinux_002a"></a>
-<h3 class="heading">s390x-*-linux*</h3>
-<p>zSeries system (64-bit) running GNU/Linux for zSeries.
-</p>
-<hr /><a name="s390x_002dibm_002dtpf"></a><a name="s390x_002dibm_002dtpf_002a"></a>
-<h3 class="heading">s390x-ibm-tpf*</h3>
-<p>zSeries system (64-bit) running TPF. This platform is
-supported as cross-compilation target only.
-</p>
-<hr /><a name="x_002dx_002dsolaris2"></a><a name="g_t_002a_002d_002a_002dsolaris2_002a"></a>
-<h3 class="heading">*-*-solaris2*</h3>
-<p>Support for Solaris 9 has been obsoleted in GCC 4.9, but can still be
-enabled by configuring with <samp>--enable-obsolete</samp>. Support will be
-removed in GCC 4.10. Support for Solaris 8 has removed in GCC 4.8.
-Support for Solaris 7 has been removed in GCC 4.6.
-</p>
-<p>Sun does not ship a C compiler with Solaris 2 before Solaris 10, though
-you can download the Sun Studio compilers for free. In Solaris 10 and
-11, GCC 3.4.3 is available as <code>/usr/sfw/bin/gcc</code>. Solaris 11
-also provides GCC 4.5.2 as <code>/usr/gcc/4.5/bin/gcc</code>. Alternatively,
-you can install a pre-built GCC to bootstrap and install GCC. See the
-<a href="binaries.html">binaries page</a> for details.
-</p>
-<p>The Solaris 2 <code>/bin/sh</code> will often fail to configure
-&lsquo;<samp>libstdc++-v3</samp>&rsquo;, &lsquo;<samp>boehm-gc</samp>&rsquo; or &lsquo;<samp>libjava</samp>&rsquo;. We therefore
-recommend using the following initial sequence of commands
-</p>
-<div class="smallexample">
-<pre class="smallexample">% CONFIG_SHELL=/bin/ksh
-% export CONFIG_SHELL
-</pre></div>
-
-<p>and proceed as described in <a href="configure.html">the configure instructions</a>.
-In addition we strongly recommend specifying an absolute path to invoke
-<code><var>srcdir</var>/configure</code>.
-</p>
-<p>Solaris 2 comes with a number of optional OS packages. Some of these
-are needed to use GCC fully, namely <code>SUNWarc</code>,
-<code>SUNWbtool</code>, <code>SUNWesu</code>, <code>SUNWhea</code>, <code>SUNWlibm</code>,
-<code>SUNWsprot</code>, and <code>SUNWtoo</code>. If you did not install all
-optional packages when installing Solaris 2, you will need to verify that
-the packages that GCC needs are installed.
-</p>
-<p>To check whether an optional package is installed, use
-the <code>pkginfo</code> command. To add an optional package, use the
-<code>pkgadd</code> command. For further details, see the Solaris 2
-documentation.
-</p>
-<p>Trying to use the linker and other tools in
-<samp>/usr/ucb</samp> to install GCC has been observed to cause trouble.
-For example, the linker may hang indefinitely. The fix is to remove
-<samp>/usr/ucb</samp> from your <code>PATH</code>.
-</p>
-<p>The build process works more smoothly with the legacy Sun tools so, if you
-have <samp>/usr/xpg4/bin</samp> in your <code>PATH</code>, we recommend that you place
-<samp>/usr/bin</samp> before <samp>/usr/xpg4/bin</samp> for the duration of the build.
-</p>
-<p>We recommend the use of the Sun assembler or the GNU assembler, in
-conjunction with the Sun linker. The GNU <code>as</code>
-versions included in Solaris 10, from GNU binutils 2.15, and Solaris 11,
-from GNU binutils 2.19, are known to work. They can be found in
-<samp>/usr/sfw/bin/gas</samp>. Current versions of GNU binutils (2.22)
-are known to work as well. Note that your mileage may vary
-if you use a combination of the GNU tools and the Sun tools: while the
-combination GNU <code>as</code> + Sun <code>ld</code> should reasonably work,
-the reverse combination Sun <code>as</code> + GNU <code>ld</code> may fail to
-build or cause memory corruption at runtime in some cases for C++ programs.
-GNU <code>ld</code> usually works as well, although the version included in
-Solaris 10 cannot be used due to several bugs. Again, the current
-version (2.22) is known to work, but generally lacks platform specific
-features, so better stay with Sun <code>ld</code>. To use the LTO linker
-plugin (<samp>-fuse-linker-plugin</samp>) with GNU <code>ld</code>, GNU
-binutils <em>must</em> be configured with <samp>--enable-largefile</samp>.
-</p>
-<p>To enable symbol versioning in &lsquo;<samp>libstdc++</samp>&rsquo; with Sun <code>ld</code>,
-you need to have any version of GNU <code>c++filt</code>, which is part of
-GNU binutils. &lsquo;<samp>libstdc++</samp>&rsquo; symbol versioning will be disabled if no
-appropriate version is found. Sun <code>c++filt</code> from the Sun Studio
-compilers does <em>not</em> work.
-</p>
-<p>Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
-newer: <code>g++</code> will complain that types are missing. These headers
-assume that omitting the type means <code>int</code>; this assumption worked for
-C90 but is wrong for C++, and is now wrong for C99 also.
-</p>
-<p>Sun bug 4927647 sometimes causes random spurious testsuite failures
-related to missing diagnostic output. This bug doesn&rsquo;t affect GCC
-itself, rather it is a kernel bug triggered by the <code>expect</code>
-program which is used only by the GCC testsuite driver. When the bug
-causes the <code>expect</code> program to miss anticipated output, extra
-testsuite failures appear.
-</p>
-<p>There are patches for Solaris 9 (117171-11 or newer for
-SPARC, 117172-11 or newer for Intel) that address this problem.
-</p>
-<p>Thread-local storage (TLS) is supported in Solaris&nbsp;9, but requires
-some patches. The &lsquo;<samp>libthread</samp>&rsquo; patches provide the
-<code>__tls_get_addr</code> (SPARC, 64-bit x86) resp.&nbsp;<code>___tls_get_addr</code>
-(32-bit x86) functions. On Solaris&nbsp;9, the necessary support
-on SPARC is present since FCS, while 114432-05 or newer is required on
-Intel. Additionally, on Solaris&nbsp;9/x86, patch 113986-02 or newer is
-required for the Sun <code>ld</code> and runtime linker (<code>ld.so.1</code>)
-support, while Solaris&nbsp;9/SPARC works since FCS. The linker
-patches must be installed even if GNU <code>ld</code> is used. Sun
-<code>as</code> in Solaris&nbsp;9 doesn&rsquo;t support the necessary
-relocations, so GNU <code>as</code> must be used. The <code>configure</code>
-script checks for those prerequisites and automatically enables TLS
-support if they are met. Although those minimal patch versions should
-work, it is recommended to use the latest patch versions which include
-additional bug fixes.
-</p>
-<hr /><a name="sparc_002dx_002dx"></a><a name="sparc_002a_002d_002a_002d_002a"></a>
-<h3 class="heading">sparc*-*-*</h3>
-<p>This section contains general configuration information for all
-SPARC-based platforms. In addition to reading this section, please
-read all other sections that match your target.
-</p>
-<p>Newer versions of the GNU Multiple Precision Library (GMP), the MPFR
-library and the MPC library are known to be miscompiled by earlier
-versions of GCC on these platforms. We therefore recommend the use
-of the exact versions of these libraries listed as minimal versions
-in <a href="prerequisites.html">the prerequisites</a>.
-</p>
-<hr /><a name="sparc_002dsun_002dsolaris2"></a><a name="sparc_002dsun_002dsolaris2_002a"></a>
-<h3 class="heading">sparc-sun-solaris2*</h3>
-<p>When GCC is configured to use GNU binutils 2.14 or later, the binaries
-produced are smaller than the ones produced using Sun&rsquo;s native tools;
-this difference is quite significant for binaries containing debugging
-information.
-</p>
-<p>Starting with Solaris 7, the operating system is capable of executing
-64-bit SPARC V9 binaries. GCC 3.1 and later properly supports
-this; the <samp>-m64</samp> option enables 64-bit code generation.
-However, if all you want is code tuned for the UltraSPARC CPU, you
-should try the <samp>-mtune=ultrasparc</samp> option instead, which produces
-code that, unlike full 64-bit code, can still run on non-UltraSPARC
-machines.
-</p>
-<p>When configuring on a Solaris 7 or later system that is running a kernel
-that supports only 32-bit binaries, one must configure with
-<samp>--disable-multilib</samp>, since we will not be able to build the
-64-bit target libraries.
-</p>
-<p>GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
-the GNU compiler (especially GCC 3.0.x versions), which lead to the
-miscompilation of the stage1 compiler and the subsequent failure of the
-bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
-stage, i.e. to bootstrap that compiler with the base compiler and then
-use it to bootstrap the final compiler.
-</p>
-<p>GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
-and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
-failure in form of a miscompilation of the stage1 compiler by the Sun
-compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
-</p>
-<p>GCC 3.4 changed the default debugging format from Stabs to DWARF-2 for
-32-bit code on Solaris 7 and later. If you use the Sun assembler, this
-change apparently runs afoul of Sun bug 4910101 (which is referenced as
-an x86-only problem by Sun, probably because they do not use DWARF-2).
-A symptom of the problem is that you cannot compile C++ programs like
-<code>groff</code> 1.19.1 without getting messages similar to the following:
-</p>
-<div class="smallexample">
-<pre class="smallexample">ld: warning: relocation error: R_SPARC_UA32: &hellip;
- external symbolic relocation against non-allocatable section
- .debug_info cannot be processed at runtime: relocation ignored.
-</pre></div>
-
-<p>To work around this problem, compile with <samp>-gstabs+</samp> instead of
-plain <samp>-g</samp>.
-</p>
-<p>When configuring the GNU Multiple Precision Library (GMP), the MPFR
-library or the MPC library on a Solaris 7 or later system, the canonical
-target triplet must be specified as the <code>build</code> parameter on the
-configure line. This target triplet can be obtained by invoking <code>./config.guess</code> in the toplevel source directory of GCC (and
-not that of GMP or MPFR or MPC). For example on a Solaris 9 system:
-</p>
-<div class="smallexample">
-<pre class="smallexample">% ./configure --build=sparc-sun-solaris2.9 --prefix=xxx
-</pre></div>
-
-<hr /><a name="sparc_002dsun_002dsolaris210"></a><a name="sparc_002dsun_002dsolaris2_002e10"></a>
-<h3 class="heading">sparc-sun-solaris2.10</h3>
-<p>There is a bug in older versions of the Sun assembler which breaks
-thread-local storage (TLS). A typical error message is
-</p>
-<div class="smallexample">
-<pre class="smallexample">ld: fatal: relocation error: R_SPARC_TLS_LE_HIX22: file /var/tmp//ccamPA1v.o:
- symbol &lt;unknown&gt;: bad symbol type SECT: symbol type must be TLS
-</pre></div>
-
-<p>This bug is fixed in Sun patch 118683-03 or later.
-</p>
-<hr /><a name="sparc_002dx_002dlinux"></a><a name="sparc_002d_002a_002dlinux_002a"></a>
-<h3 class="heading">sparc-*-linux*</h3>
-
-<p>GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4
-or newer on this platform. All earlier binutils and glibc
-releases mishandled unaligned relocations on <code>sparc-*-*</code> targets.
-</p>
-
-<hr /><a name="sparc64_002dx_002dsolaris2"></a><a name="sparc64_002d_002a_002dsolaris2_002a"></a>
-<h3 class="heading">sparc64-*-solaris2*</h3>
-<p>When configuring the GNU Multiple Precision Library (GMP), the MPFR
-library or the MPC library, the canonical target triplet must be specified
-as the <code>build</code> parameter on the configure line. For example
-on a Solaris 9 system:
-</p>
-<div class="smallexample">
-<pre class="smallexample">% ./configure --build=sparc64-sun-solaris2.9 --prefix=xxx
-</pre></div>
-
-<p>The following compiler flags must be specified in the configure
-step in order to bootstrap this target with the Sun compiler:
-</p>
-<div class="smallexample">
-<pre class="smallexample">% CC=&quot;cc -xarch=v9 -xildoff&quot; <var>srcdir</var>/configure [<var>options</var>] [<var>target</var>]
-</pre></div>
-
-<p><samp>-xarch=v9</samp> specifies the SPARC-V9 architecture to the Sun toolchain
-and <samp>-xildoff</samp> turns off the incremental linker.
-</p>
-<hr /><a name="sparcv9_002dx_002dsolaris2"></a><a name="sparcv9_002d_002a_002dsolaris2_002a"></a>
-<h3 class="heading">sparcv9-*-solaris2*</h3>
-<p>This is a synonym for &lsquo;<samp>sparc64-*-solaris2*</samp>&rsquo;.
-</p>
-<hr /><a name="c6x_002dx_002dx"></a><a name="c6x_002d_002a_002d_002a"></a>
-<h3 class="heading">c6x-*-*</h3>
-<p>The C6X family of processors. This port requires binutils-2.22 or newer.
-</p>
-<hr /><a name="tilegx_002d_002a_002dlinux"></a><a name="tilegx_002d_002a_002dlinux_002a"></a>
-<h3 class="heading">tilegx-*-linux*</h3>
-<p>The TILE-Gx processor in little endian mode, running GNU/Linux. This
-port requires binutils-2.22 or newer.
-</p>
-<hr /><a name="tilegxbe_002d_002a_002dlinux"></a><a name="tilegxbe_002d_002a_002dlinux_002a"></a>
-<h3 class="heading">tilegxbe-*-linux*</h3>
-<p>The TILE-Gx processor in big endian mode, running GNU/Linux. This
-port requires binutils-2.23 or newer.
-</p>
-<hr /><a name="tilepro_002d_002a_002dlinux"></a><a name="tilepro_002d_002a_002dlinux_002a"></a>
-<h3 class="heading">tilepro-*-linux*</h3>
-<p>The TILEPro processor running GNU/Linux. This port requires
-binutils-2.22 or newer.
-</p>
-<hr /><a name="x_002dx_002dvxworks"></a><a name="g_t_002a_002d_002a_002dvxworks_002a"></a>
-<h3 class="heading">*-*-vxworks*</h3>
-<p>Support for VxWorks is in flux. At present GCC supports <em>only</em> the
-very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC.
-We welcome patches for other architectures supported by VxWorks 5.5.
-Support for VxWorks AE would also be welcome; we believe this is merely
-a matter of writing an appropriate &ldquo;configlette&rdquo; (see below). We are
-not interested in supporting older, a.out or COFF-based, versions of
-VxWorks in GCC 3.
-</p>
-<p>VxWorks comes with an older version of GCC installed in
-<samp><var>$WIND_BASE</var>/host</samp>; we recommend you do not overwrite it.
-Choose an installation <var>prefix</var> entirely outside <var>$WIND_BASE</var>.
-Before running <code>configure</code>, create the directories <samp><var>prefix</var></samp>
-and <samp><var>prefix</var>/bin</samp>. Link or copy the appropriate assembler,
-linker, etc. into <samp><var>prefix</var>/bin</samp>, and set your <var>PATH</var> to
-include that directory while running both <code>configure</code> and
-<code>make</code>.
-</p>
-<p>You must give <code>configure</code> the
-<samp>--with-headers=<var>$WIND_BASE</var>/target/h</samp> switch so that it can
-find the VxWorks system headers. Since VxWorks is a cross compilation
-target only, you must also specify <samp>--target=<var>target</var></samp>.
-<code>configure</code> will attempt to create the directory
-<samp><var>prefix</var>/<var>target</var>/sys-include</samp> and copy files into it;
-make sure the user running <code>configure</code> has sufficient privilege
-to do so.
-</p>
-<p>GCC&rsquo;s exception handling runtime requires a special &ldquo;configlette&rdquo;
-module, <samp>contrib/gthr_supp_vxw_5x.c</samp>. Follow the instructions in
-that file to add the module to your kernel build. (Future versions of
-VxWorks will incorporate this module.)
-</p>
-<hr /><a name="x86_002d64_002dx_002dx"></a><a name="x86_005f64_002d_002a_002d_002a_002c-amd64_002d_002a_002d_002a"></a>
-<h3 class="heading">x86_64-*-*, amd64-*-*</h3>
-<p>GCC supports the x86-64 architecture implemented by the AMD64 processor
-(amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD.
-On GNU/Linux the default is a bi-arch compiler which is able to generate
-both 64-bit x86-64 and 32-bit x86 code (via the <samp>-m32</samp> switch).
-</p>
-<hr /><a name="x86_002d64_002dx_002dsolaris210"></a><a name="x86_005f64_002d_002a_002dsolaris2_002e1_005b0_002d9_005d_002a"></a>
-<h3 class="heading">x86_64-*-solaris2.1[0-9]*</h3>
-<p>GCC also supports the x86-64 architecture implemented by the AMD64
-processor (&lsquo;<samp>amd64-*-*</samp>&rsquo; is an alias for &lsquo;<samp>x86_64-*-*</samp>&rsquo;) on
-Solaris 10 or later. Unlike other systems, without special options a
-bi-arch compiler is built which generates 32-bit code by default, but
-can generate 64-bit x86-64 code with the <samp>-m64</samp> switch. Since
-GCC 4.7, there is also configuration that defaults to 64-bit code, but
-can generate 32-bit code with <samp>-m32</samp>. To configure and build
-this way, you have to provide all support libraries like <samp>libgmp</samp>
-as 64-bit code, configure with <samp>--target=x86_64-pc-solaris2.1x</samp>
-and &lsquo;<samp>CC=gcc -m64</samp>&rsquo;.
-</p>
-<hr /><a name="xtensa_002dx_002delf"></a><a name="xtensa_002a_002d_002a_002delf"></a>
-<h3 class="heading">xtensa*-*-elf</h3>
-<p>This target is intended for embedded Xtensa systems using the
-&lsquo;<samp>newlib</samp>&rsquo; C library. It uses ELF but does not support shared
-objects. Designed-defined instructions specified via the
-Tensilica Instruction Extension (TIE) language are only supported
-through inline assembly.
-</p>
-<p>The Xtensa configuration information must be specified prior to
-building GCC. The <samp>include/xtensa-config.h</samp> header
-file contains the configuration information. If you created your
-own Xtensa configuration with the Xtensa Processor Generator, the
-downloaded files include a customized copy of this header file,
-which you can use to replace the default header file.
-</p>
-<hr /><a name="xtensa_002dx_002dlinux"></a><a name="xtensa_002a_002d_002a_002dlinux_002a"></a>
-<h3 class="heading">xtensa*-*-linux*</h3>
-<p>This target is for Xtensa systems running GNU/Linux. It supports ELF
-shared objects and the GNU C library (glibc). It also generates
-position-independent code (PIC) regardless of whether the
-<samp>-fpic</samp> or <samp>-fPIC</samp> options are used. In other
-respects, this target is the same as the
-<a href="#xtensa*-*-elf">&lsquo;<samp>xtensa*-*-elf</samp>&rsquo;</a> target.
-</p>
-<hr /><a name="windows"></a><a name="Microsoft-Windows"></a>
-<h3 class="heading">Microsoft Windows</h3>
-
-<a name="Intel-16_002dbit-versions"></a>
-<h4 class="subheading">Intel 16-bit versions</h4>
-<p>The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
-supported.
-</p>
-<p>However, the 32-bit port has limited support for Microsoft
-Windows 3.11 in the Win32s environment, as a target only. See below.
-</p>
-<a name="Intel-32_002dbit-versions"></a>
-<h4 class="subheading">Intel 32-bit versions</h4>
-<p>The 32-bit versions of Windows, including Windows 95, Windows NT, Windows
-XP, and Windows Vista, are supported by several different target
-platforms. These targets differ in which Windows subsystem they target
-and which C libraries are used.
-</p>
-<ul>
-<li> Cygwin <a href="#x-x-cygwin">*-*-cygwin</a>: Cygwin provides a user-space
-Linux API emulation layer in the Win32 subsystem.
-</li><li> Interix <a href="#x-x-interix">*-*-interix</a>: The Interix subsystem
-provides native support for POSIX.
-</li><li> MinGW <a href="#x-x-mingw32">*-*-mingw32</a>: MinGW is a native GCC port for
-the Win32 subsystem that provides a subset of POSIX.
-</li><li> MKS i386-pc-mks: NuTCracker from MKS. See
-<a href="http://www.mkssoftware.com/">http://www.mkssoftware.com/</a> for more information.
-</li></ul>
-
-<a name="Intel-64_002dbit-versions"></a>
-<h4 class="subheading">Intel 64-bit versions</h4>
-<p>GCC contains support for x86-64 using the mingw-w64
-runtime library, available from <a href="http://mingw-w64.sourceforge.net/">http://mingw-w64.sourceforge.net/</a>.
-This library should be used with the target triple x86_64-pc-mingw32.
-</p>
-<p>Presently Windows for Itanium is not supported.
-</p>
-<a name="Windows-CE"></a>
-<h4 class="subheading">Windows CE</h4>
-<p>Windows CE is supported as a target only on Hitachi
-SuperH (sh-wince-pe), and MIPS (mips-wince-pe).
-</p>
-<a name="Other-Windows-Platforms"></a>
-<h4 class="subheading">Other Windows Platforms</h4>
-<p>GCC no longer supports Windows NT on the Alpha or PowerPC.
-</p>
-<p>GCC no longer supports the Windows POSIX subsystem. However, it does
-support the Interix subsystem. See above.
-</p>
-<p>Old target names including *-*-winnt and *-*-windowsnt are no longer used.
-</p>
-<p>PW32 (i386-pc-pw32) support was never completed, and the project seems to
-be inactive. See <a href="http://pw32.sourceforge.net/">http://pw32.sourceforge.net/</a> for more information.
-</p>
-<p>UWIN support has been removed due to a lack of maintenance.
-</p>
-<hr /><a name="x_002dx_002dcygwin"></a><a name="g_t_002a_002d_002a_002dcygwin"></a>
-<h3 class="heading">*-*-cygwin</h3>
-<p>Ports of GCC are included with the
-<a href="http://www.cygwin.com/">Cygwin environment</a>.
-</p>
-<p>GCC will build under Cygwin without modification; it does not build
-with Microsoft&rsquo;s C++ compiler and there are no plans to make it do so.
-</p>
-<p>The Cygwin native compiler can be configured to target any 32-bit x86
-cpu architecture desired; the default is i686-pc-cygwin. It should be
-used with as up-to-date a version of binutils as possible; use either
-the latest official GNU binutils release in the Cygwin distribution,
-or version 2.20 or above if building your own.
-</p>
-<hr /><a name="x_002dx_002dinterix"></a><a name="g_t_002a_002d_002a_002dinterix"></a>
-<h3 class="heading">*-*-interix</h3>
-<p>The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
-and Subsystem for UNIX-based Applications (SUA). Applications compiled
-with this target run in the Interix subsystem, which is separate from
-the Win32 subsystem. This target was last known to work in GCC 3.3.
-</p>
-<hr /><a name="x_002dx_002dmingw32"></a><a name="g_t_002a_002d_002a_002dmingw32"></a>
-<h3 class="heading">*-*-mingw32</h3>
-<p>GCC will build with and support only MinGW runtime 3.12 and later.
-Earlier versions of headers are incompatible with the new default semantics
-of <code>extern inline</code> in <code>-std=c99</code> and <code>-std=gnu99</code> modes.
-</p>
-<hr /><a name="older"></a><a name="Older-systems"></a>
-<h3 class="heading">Older systems</h3>
-<p>GCC contains support files for many older (1980s and early
-1990s) Unix variants. For the most part, support for these systems
-has not been deliberately removed, but it has not been maintained for
-several years and may suffer from bitrot.
-</p>
-<p>Starting with GCC 3.1, each release has a list of &ldquo;obsoleted&rdquo; systems.
-Support for these systems is still present in that release, but
-<code>configure</code> will fail unless the <samp>--enable-obsolete</samp>
-option is given. Unless a maintainer steps forward, support for these
-systems will be removed from the next release of GCC.
-</p>
-<p>Support for old systems as hosts for GCC can cause problems if the
-workarounds for compiler, library and operating system bugs affect the
-cleanliness or maintainability of the rest of GCC. In some cases, to
-bring GCC up on such a system, if still possible with current GCC, may
-require first installing an old version of GCC which did work on that
-system, and using it to compile a more recent GCC, to avoid bugs in the
-vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
-<samp>old-releases</samp> directory on the <a href="../mirrors.html">GCC mirror
-sites</a>. Header bugs may generally be avoided using
-<code>fixincludes</code>, but bugs or deficiencies in libraries and the
-operating system may still cause problems.
-</p>
-<p>Support for older systems as targets for cross-compilation is less
-problematic than support for them as hosts for GCC; if an enthusiast
-wishes to make such a target work again (including resurrecting any of
-the targets that never worked with GCC 2, starting from the last
-version before they were removed), patches
-<a href="../contribute.html">following the usual requirements</a> would be
-likely to be accepted, since they should not affect the support for more
-modern targets.
-</p>
-<p>For some systems, old versions of GNU binutils may also be useful,
-and are available from <samp>pub/binutils/old-releases</samp> on
-<a href="http://sourceware.org/mirrors.html">sourceware.org mirror sites</a>.
-</p>
-<p>Some of the information on specific systems above relates to
-such older systems, but much of the information
-about GCC on such systems (which may no longer be applicable to
-current GCC) is to be found in the GCC texinfo manual.
-</p>
-<hr /><a name="elf"></a><a name="all-ELF-targets-_0028SVR4_002c-Solaris-2_002c-etc_002e_0029"></a>
-<h3 class="heading">all ELF targets (SVR4, Solaris 2, etc.)</h3>
-<p>C++ support is significantly better on ELF targets if you use the
-<a href="./configure.html#with-gnu-ld">GNU linker</a>; duplicate copies of
-inlines, vtables and template instantiations will be discarded
-automatically.
-</p>
-
-<hr />
-<p><p><a href="./index.html">Return to the GCC Installation page</a>
-</p>
-
-
-
-
-
-
-</body>
-</html>
diff --git a/gcc-4.9/INSTALL/test.html b/gcc-4.9/INSTALL/test.html
deleted file mode 100644
index 5815090..0000000
--- a/gcc-4.9/INSTALL/test.html
+++ /dev/null
@@ -1,315 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<!-- Copyright (C) 1988-2014 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.3 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. -->
-<!-- Created by GNU Texinfo 5.1, http://www.gnu.org/software/texinfo/ -->
-<head>
-<title>Installing GCC</title>
-
-<meta name="description" content="Installing GCC">
-<meta name="keywords" content="Installing GCC">
-<meta name="resource-type" content="document">
-<meta name="distribution" content="global">
-<meta name="Generator" content="makeinfo">
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<style type="text/css">
-<!--
-a.summary-letter {text-decoration: none}
-blockquote.smallquotation {font-size: smaller}
-div.display {margin-left: 3.2em}
-div.example {margin-left: 3.2em}
-div.indentedblock {margin-left: 3.2em}
-div.lisp {margin-left: 3.2em}
-div.smalldisplay {margin-left: 3.2em}
-div.smallexample {margin-left: 3.2em}
-div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
-div.smalllisp {margin-left: 3.2em}
-kbd {font-style:oblique}
-pre.display {font-family: inherit}
-pre.format {font-family: inherit}
-pre.menu-comment {font-family: serif}
-pre.menu-preformatted {font-family: serif}
-pre.smalldisplay {font-family: inherit; font-size: smaller}
-pre.smallexample {font-size: smaller}
-pre.smallformat {font-family: inherit; font-size: smaller}
-pre.smalllisp {font-size: smaller}
-span.nocodebreak {white-space:nowrap}
-span.nolinebreak {white-space:nowrap}
-span.roman {font-family:serif; font-weight:normal}
-span.sansserif {font-family:sans-serif; font-weight:normal}
-ul.no-bullet {list-style: none}
--->
-</style>
-
-
-</head>
-
-<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
-<h1 class="settitle" align="center">Installing GCC</h1>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<a name="index-Testing"></a>
-<a name="index-Installing-GCC_003a-Testing"></a>
-<a name="index-Testsuite"></a>
-
-<p>Before you install GCC, we encourage you to run the testsuites and to
-compare your results with results from a similar configuration that have
-been submitted to the
-<a href="http://gcc.gnu.org/ml/gcc-testresults/">gcc-testresults mailing list</a>.
-Some of these archived results are linked from the build status lists
-at <a href="http://gcc.gnu.org/buildstat.html">http://gcc.gnu.org/buildstat.html</a>, although not everyone who
-reports a successful build runs the testsuites and submits the results.
-This step is optional and may require you to download additional software,
-but it can give you confidence in your new GCC installation or point out
-problems before you install and start using your new GCC.
-</p>
-<p>First, you must have <a href="download.html">downloaded the testsuites</a>.
-These are part of the full distribution, but if you downloaded the
-&ldquo;core&rdquo; compiler plus any front ends, you must download the testsuites
-separately.
-</p>
-<p>Second, you must have the testing tools installed. This includes
-<a href="http://www.gnu.org/software/dejagnu/">DejaGnu</a>, Tcl, and Expect;
-the DejaGnu site has links to these.
-</p>
-<p>If the directories where <code>runtest</code> and <code>expect</code> were
-installed are not in the <code>PATH</code>, you may need to set the following
-environment variables appropriately, as in the following example (which
-assumes that DejaGnu has been installed under <samp>/usr/local</samp>):
-</p>
-<div class="smallexample">
-<pre class="smallexample">TCL_LIBRARY = /usr/local/share/tcl8.0
-DEJAGNULIBS = /usr/local/share/dejagnu
-</pre></div>
-
-<p>(On systems such as Cygwin, these paths are required to be actual
-paths, not mounts or links; presumably this is due to some lack of
-portability in the DejaGnu code.)
-</p>
-
-<p>Finally, you can run the testsuite (which may take a long time):
-</p><div class="smallexample">
-<pre class="smallexample">cd <var>objdir</var>; make -k check
-</pre></div>
-
-<p>This will test various components of GCC, such as compiler
-front ends and runtime libraries. While running the testsuite, DejaGnu
-might emit some harmless messages resembling
-&lsquo;<samp>WARNING: Couldn't find the global config file.</samp>&rsquo; or
-&lsquo;<samp>WARNING: Couldn't find tool init file</samp>&rsquo; that can be ignored.
-</p>
-<p>If you are testing a cross-compiler, you may want to run the testsuite
-on a simulator as described at <a href="http://gcc.gnu.org/simtest-howto.html">http://gcc.gnu.org/simtest-howto.html</a>.
-</p>
-<a name="How-can-you-run-the-testsuite-on-selected-tests_003f"></a>
-<h3 class="section">How can you run the testsuite on selected tests?</h3>
-
-<p>In order to run sets of tests selectively, there are targets
-&lsquo;<samp>make check-gcc</samp>&rsquo; and language specific &lsquo;<samp>make check-c</samp>&rsquo;,
-&lsquo;<samp>make check-c++</samp>&rsquo;, &lsquo;<samp>make check-fortran</samp>&rsquo;, &lsquo;<samp>make check-java</samp>&rsquo;,
-&lsquo;<samp>make check-ada</samp>&rsquo;, &lsquo;<samp>make check-objc</samp>&rsquo;, &lsquo;<samp>make check-obj-c++</samp>&rsquo;,
-&lsquo;<samp>make check-lto</samp>&rsquo;
-in the <samp>gcc</samp> subdirectory of the object directory. You can also
-just run &lsquo;<samp>make check</samp>&rsquo; in a subdirectory of the object directory.
-</p>
-
-<p>A more selective way to just run all <code>gcc</code> execute tests in the
-testsuite is to use
-</p>
-<div class="smallexample">
-<pre class="smallexample">make check-gcc RUNTESTFLAGS=&quot;execute.exp <var>other-options</var>&quot;
-</pre></div>
-
-<p>Likewise, in order to run only the <code>g++</code> &ldquo;old-deja&rdquo; tests in
-the testsuite with filenames matching &lsquo;<samp>9805*</samp>&rsquo;, you would use
-</p>
-<div class="smallexample">
-<pre class="smallexample">make check-g++ RUNTESTFLAGS=&quot;old-deja.exp=9805* <var>other-options</var>&quot;
-</pre></div>
-
-<p>The <samp>*.exp</samp> files are located in the testsuite directories of the GCC
-source, the most important ones being <samp>compile.exp<