--with-llsc--with-llsc--disable-bootstrap--disable-bootstrap--enable-version-specific-runtime-libs--enable-languages=lang1,lang2,...grep language= */config-lang.in !
Currently, you can use any of the following:
all, ada, c, c++, fortran, java,
objc, obj-c++, treelang.
--- 574,592 ----
--enable-version-specific-runtime-libs--enable-languages=lang1,lang2,...grep language= */config-lang.in !
Currently, you can use any of the following:
key defaults to GCC version number, and can be overridden by the
--enable-win32-registry=key option. Vendors and distributors
who use custom installers are encouraged to provide a different key,
--- 644,650 ----
to look up installations paths in the registry using the following key:
key defaults to GCC version number, and can be overridden by the
--enable-win32-registry=key option. Vendors and distributors
who use custom installers are encouraged to provide a different key,
*************** by default, and can be disabled by The `valgrind' check requires the external valgrind
simulator, available from http://valgrind.org/. The
! `df', `rtl', `gcac' and `valgrind' checks are very expensive.
! To disable all checking, `--disable-checking' or
! `--enable-checking=none' must be explicitly requested. Disabling
assertions will make the compiler and runtime slightly faster but
increase the risk of undetected internal errors causing wrong code to be
generated.
--- 668,689 ----
consistency checks of the requested complexity. This does not change the
generated code, but adds error checking within the compiler. This will
slow down the compiler and may only work properly if you are building
! the compiler with GCC. This is ‘yes’ by default when building
! from SVN or snapshots, but ‘release’ for releases. More control
over the checks may be had by specifying list. The categories of
! checks available are ‘yes’ (most common checks
! ‘assert,misc,tree,gc,rtlflag,runtime’), ‘no’ (no checks at
! all), ‘all’ (all but ‘valgrind’), ‘release’ (cheapest
! checks ‘assert,runtime’) or ‘none’ (same as ‘no’).
! Individual checks can be enabled with these flags ‘assert’,
! ‘df’, ‘fold’, ‘gc’, ‘gcac’ ‘misc’, ‘rtl’,
! ‘rtlflag’, ‘runtime’, ‘tree’, and ‘valgrind’.
! The ‘valgrind’ check requires the external valgrind
simulator, available from http://valgrind.org/. The
! ‘df’, ‘rtl’, ‘gcac’ and ‘valgrind’ checks are very expensive.
! To disable all checking, ‘--disable-checking’ or
! ‘--enable-checking=none’ must be explicitly requested. Disabling
assertions will make the compiler and runtime slightly faster but
increase the risk of undetected internal errors causing wrong code to be
generated.
*************** generated.
*** 692,698 ****
information, every time it is run. This is for internal development
purposes, and only works when the compiler is being built with gcc. The
level argument controls whether the compiler is built optimized or
! not, values are `opt' and `noopt'. For coverage analysis you
want to disable optimization, for performance analysis you want to
enable optimization. When coverage is enabled, the default level is
without optimization.
--- 692,698 ----
information, every time it is run. This is for internal development
purposes, and only works when the compiler is being built with gcc. The
level argument controls whether the compiler is built optimized or
! not, values are ‘opt’ and ‘noopt’. For coverage analysis you
want to disable optimization, for performance analysis you want to
enable optimization. When coverage is enabled, the default level is
without optimization.
*************** allocation is gathered. This informatio
*** 703,709 ****
The following options apply to building `libgcj'.
If this option is not given, but an ecj.jar file is found in
! the topmost source tree at configure time, then the `libgcj'
build will create and install ecj1, and will also install the
discovered ecj.jar into a suitable place in the install tree.
--- 853,893 ----
separately, or it just happens not to build on your particular
machine. In general, if the Java front end is enabled, the GCJ
libraries will be enabled too, unless they're known to not work on
! the target platform. If GCJ is enabled but ‘libgcj’ isn't built, you
may need to port it; in this case, before modifying the top-level
! configure.in so that ‘libgcj’ is enabled by default on this platform,
you may use --enable-libgcj to override the default.
The following options apply to building ‘libgcj’.
If this option is not given, but an ecj.jar file is found in
! the topmost source tree at configure time, then the ‘libgcj’
build will create and install ecj1, and will also install the
discovered ecj.jar into a suitable place in the install tree.
*************** source files. A suitable jar is availab
*** 899,905 ****
Return to the GCC Installation page
--- 453,459 ----
! Return to the GCC Installation page
diff -Nrcpad gcc-4.3.2/INSTALL/index.html gcc-4.3.3/INSTALL/index.html
*** gcc-4.3.2/INSTALL/index.html Wed Aug 27 18:09:38 2008
--- gcc-4.3.3/INSTALL/index.html Sat Jan 24 10:32:31 2009
***************
*** 3,9 ****
The company name is meaningful only to disambiguate when the rest of
the information supplied is insufficient. You can omit it, writing
! just `cpu-system', if it is not needed. For example,
! `vax-ultrix4.2' is equivalent to `vax-dec-ultrix4.2'.
Here is a list of system types:
--- 133,140 ----
The company name is meaningful only to disambiguate when the rest of
the information supplied is insufficient. You can omit it, writing
! just ‘cpu-system’, if it is not needed. For example,
! ‘vax-ultrix4.2’ is equivalent to ‘vax-dec-ultrix4.2’.
Here is a list of system types:
*************** vxworks, winnt, xenix.
*** 151,168 ****
operating system from the CPU and company.
You can add a version number to the system type; this may or may not
! make a difference. For example, you can write `bsd4.3' or
! `bsd4.4' to distinguish versions of BSD. In practice, the version
! number is most needed for `sysv3' and `sysv4', which are often
treated differently.
! `linux-gnu' is the canonical name for the GNU/Linux target; however
! GCC will also accept `linux'. The version of the kernel in use is
! not relevant on these systems. A suffix such as `libc1' or `aout'
distinguishes major versions of the C library; all of the suffixed versions
are obsolete.
! If you specify an impossible combination such as `i860-dg-vms',
then you may get an error message from configure, or it may
ignore part of the information and do the best it can with the rest.
configure always prints the canonical name for the alternative
--- 151,168 ----
operating system from the CPU and company.
You can add a version number to the system type; this may or may not
! make a difference. For example, you can write ‘bsd4.3’ or
! ‘bsd4.4’ to distinguish versions of BSD. In practice, the version
! number is most needed for ‘sysv3’ and ‘sysv4’, which are often
treated differently.
! ‘linux-gnu’ is the canonical name for the GNU/Linux target; however
! GCC will also accept ‘linux’. The version of the kernel in use is
! not relevant on these systems. A suffix such as ‘libc1’ or ‘aout’
distinguishes major versions of the C library; all of the suffixed versions
are obsolete.
! If you specify an impossible combination such as ‘i860-dg-vms’,
then you may get an error message from configure, or it may
ignore part of the information and do the best it can with the rest.
configure always prints the canonical name for the alternative
*************** that it used. GCC does not support all
*** 170,176 ****
Often a particular model of machine has a name. Many machine names are
recognized as aliases for CPU/company combinations. Thus, the machine
! name `sun3', mentioned above, is an alias for `m68k-sun'.
Sometimes we accept a company name as a machine name, when the name is
popularly used for a particular machine. Here is a table of the known
machine names:
--- 170,176 ----
Often a particular model of machine has a name. Many machine names are
recognized as aliases for CPU/company combinations. Thus, the machine
! name ‘sun3’, mentioned above, is an alias for ‘m68k-sun’.
Sometimes we accept a company name as a machine name, when the name is
popularly used for a particular machine. Here is a table of the known
machine names:
*************** sun4, symmetry, tower-32, tower.
*** 193,204 ****
Remember that a machine name specifies both the cpu type and the company
name.
If you want to install your own homemade configuration files, you can
! use `local' as the company name to access them. If you use
! configuration `cpu-local', the configuration name
without the cpu prefix
is used to form the configuration file names.
! Thus, if you specify `m68k-local', configuration uses
files m68k.md, local.h, m68k.c,
xm-local.h, t-local, and x-local, all in the
directory config/m68k.
--- 193,204 ----
Remember that a machine name specifies both the cpu type and the company
name.
If you want to install your own homemade configuration files, you can
! use ‘local’ as the company name to access them. If you use
! configuration ‘cpu-local’, the configuration name
without the cpu prefix
is used to form the configuration file names.
! Thus, if you specify ‘m68k-local’, configuration uses
files m68k.md, local.h, m68k.c,
xm-local.h, t-local, and x-local, all in the
directory config/m68k.
diff -Nrcpad gcc-4.3.2/INSTALL/prerequisites.html gcc-4.3.3/INSTALL/prerequisites.html
*** gcc-4.3.2/INSTALL/prerequisites.html Wed Aug 27 18:09:38 2008
--- gcc-4.3.3/INSTALL/prerequisites.html Sat Jan 24 10:32:31 2009
***************
*** 3,9 ****
The built-in The libstdc++ atomic locking routines for MIPS targets requires MIPS II
and later. A patch went in just after the GCC 3.3 release to
! make ‘mips*-*-*’ use the generic implementation instead. You can also
! configure for ‘mipsel-elf’ as a workaround. The
! ‘mips*-*-linux*’ target continues to use the MIPS II routines. More
work on this is expected in future releases.
! The built-in In order to compile GCC on an SGI running IRIX 5, the `compiler_dev.hdr'
subsystem must be installed from the IDO CD-ROM supplied by SGI.
It is also available for download from
ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist.
--- 1076,1082 ----
In order to compile GCC on an SGI running IRIX 5, the ‘compiler_dev.hdr’
subsystem must be installed from the IDO CD-ROM supplied by SGI.
It is also available for download from
ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist.
*************** resulting object file. The output shoul
*** 1127,1142 ****
then your version of cc uses the O32 or N64 ABI by default. You
! should set the environment variable CC to `cc -n32'
before configuring GCC.
If you want the resulting gcc to run on old 32-bit systems
! with the MIPS R4400 CPU, you need to ensure that only code for the `mips3'
instruction set architecture (ISA) is generated. While GCC 3.x does
this correctly, both GCC 2.95 and SGI's MIPSpro cc may change
the ISA depending on the machine where GCC is built. Using one of them
! as the bootstrap compiler may result in `mips4' code, which won't run at
! all on `mips3'-only systems. For the test program above, you should see:
then your version of cc uses the O32 or N64 ABI by default. You
! should set the environment variable CC to ‘cc -n32’
before configuring GCC.
If you want the resulting gcc to run on old 32-bit systems
! with the MIPS R4400 CPU, you need to ensure that only code for the ‘mips3’
instruction set architecture (ISA) is generated. While GCC 3.x does
this correctly, both GCC 2.95 and SGI's MIPSpro cc may change
the ISA depending on the machine where GCC is built. Using one of them
! as the bootstrap compiler may result in ‘mips4’ code, which won't run at
! all on ‘mips3’-only systems. For the test program above, you should see:
instead, you should set the environment variable CC to `cc
! -n32 -mips3' or `gcc -mips3' respectively before configuring GCC.
MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
instead, you should set the environment variable CC to ‘cc
! -n32 -mips3’ or ‘gcc -mips3’ respectively before configuring GCC.
MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
The --enable-libgcj
option is disabled by default: IRIX 6 uses a very low default limit
(20480) for the command line length. Although libtool contains a
! workaround for this problem, at least the N64 `libgcj' is known not
to build despite this, running into an internal error of the native
! ld. A sure fix is to increase this limit (`ncargs') to
its maximum of 262144 bytes. If you have root access, you can use the
systune command to do this.
! The --enable-libgcj
option is disabled by default: IRIX 6 uses a very low default limit
(20480) for the command line length. Although libtool contains a
! workaround for this problem, at least the N64 ‘libgcj’ is known not
to build despite this, running into an internal error of the native
! ld. A sure fix is to increase this limit (‘ncargs’) to
its maximum of 262144 bytes. If you have root access, you can use the
systune command to do this.
! This target is intended for embedded Xtensa systems using the
! `newlib' C library. It uses ELF but does not support shared
objects. Designed-defined instructions specified via the
Tensilica Instruction Extension (TIE) language are only supported
through inline assembly.
--- 1600,1606 ----
This target is intended for embedded Xtensa systems using the
! ‘newlib’ C library. It uses ELF but does not support shared
objects. Designed-defined instructions specified via the
Tensilica Instruction Extension (TIE) language are only supported
through inline assembly.
*************** shared objects and the GNU C library (gl
*** 1629,1635 ****
position-independent code (PIC) regardless of whether the
-fpic or -fPIC options are used. In other
respects, this target is the same as the
! `xtensa-*-elf' target.
all, ada, c, c++, fortran, java,
objc, obj-c++, treelang.
*************** Building the Ada compiler has special re
*** 594,600 ****
If you do not pass this flag, or specify the option all, then all
default languages available in the gcc sub-tree will be configured.
Ada, Objective-C++, and treelang are not default languages; the rest are.
! Re-defining LANGUAGES when calling `make' does not
work anymore, as those language sub-directories might not have been
configured!
--- 594,600 ----
If you do not pass this flag, or specify the option all, then all
default languages available in the gcc sub-tree will be configured.
Ada, Objective-C++, and treelang are not default languages; the rest are.
! Re-defining LANGUAGES when calling ‘make’ does not
work anymore, as those language sub-directories might not have been
configured!
*************** for the specified languages using
*** 615,621 ****
--disable-libada--disable-libssp--disable-libada--disable-libssp
HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\key
!
HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\key
! --nfp--enable-werror--disable-werror--enable-werror=yes--enable-werror=no--nfp--enable-werror--disable-werror--enable-werror=yes--enable-werror=no--with-gc--with-gc=choice--enable-nls--disable-nls--with-gc--with-gc=choice--enable-nls--disable-nls--enable-fixed-point--disable-fixed-point--enable-fixed-point--disable-fixed-point--with-gmp=pathname--with-gmp-include=pathname--with-gmp-lib=pathname--with-mpfr=pathname--with-mpfr-include=pathname--with-mpfr-lib=pathname--with-gmp=pathname--with-gmp-include=pathname--with-gmp-lib=pathname--with-mpfr=pathname--with-mpfr-include=pathname--with-mpfr-lib=pathname--with-debug-prefix-map=map--with-debug-prefix-map=map--with-newlib__eprintf to be
omitted from libgcc.a on the assumption that it will be provided by
! `newlib'.
--with-build-time-tools=dir--with-newlib__eprintf to be
omitted from libgcc.a on the assumption that it will be provided by
! ‘newlib’.
--with-build-time-tools=dirGeneral Options
!
! --enable-java-maintainer-mode--with-java-home=dirname--with-ecj-jar=filenameGeneral Options
!
--enable-java-maintainer-mode--with-java-home=dirname--with-ecj-jar=filename--disable-getenv-properties--enable-hash-synchronization--disable-getenv-properties--enable-hash-synchronization--with-ecos--without-libffi--enable-libgcj-debug--enable-libgcj-multifile--with-libiconv-prefix=DIR--enable-sjlj-exceptionssetjmp/longjmp-based scheme for exceptions.
! `configure' ordinarily picks the correct value based on the platform.
Only use this option if you are sure you need a different setting.
! --with-system-zlib--with-win32-nlsapi=ansi, unicows or unicode
ansichar and the Win32 A functions natively,
--- 925,951 ----
--with-ecos--without-libffi--enable-libgcj-debug--enable-libgcj-multifile--with-libiconv-prefix=DIR--enable-sjlj-exceptionssetjmp/longjmp-based scheme for exceptions.
! ‘configure’ ordinarily picks the correct value based on the platform.
Only use this option if you are sure you need a different setting.
! --with-system-zlib--with-win32-nlsapi=ansi, unicows or unicode
ansichar and the Win32 A functions natively,
*************** translating to and from UNICODE when usi
*** 953,959 ****
unspecified, this is the default.
unicowsWCHAR and Win32 W functions natively. Adds
! -lunicows to libgcj.spec to link with `libunicows'.
unicows.dll needs to be deployed on Microsoft Windows 9X machines
running built executables. libunicows.a, an open-source
import library around Microsoft's unicows.dll, is obtained from
--- 953,959 ----
unspecified, this is the default.
unicowsWCHAR and Win32 W functions natively. Adds
! -lunicows to libgcj.spec to link with ‘libunicows’.
unicows.dll needs to be deployed on Microsoft Windows 9X machines
running built executables. libunicows.a, an open-source
import library around Microsoft's unicows.dll, is obtained from
*************** only run on Microsoft Windows NT and abo
*** 972,978 ****
--with-x--enable-java-awt=PEER(S)--with-x--enable-java-awt=PEER(S)
acorn, alliant, altos, apollo, apple, att, bull,
cbm, convergent, convex, crds, dec, dg, dolphin,
elxsi, encore, harris, hitachi, hp, ibm, intergraph, isi,
--- 123,129 ----
abbreviations are used rather than the longer official names.
!
acorn, alliant, altos, apollo, apple, att, bull,
cbm, convergent, convex, crds, dec, dg, dolphin,
elxsi, encore, harris, hitachi, hp, ibm, intergraph, isi,
*************** sequent, sgi, sony, sun, tti, unicom, wr
*** 133,140 ****
__sync_* functions are available on MIPS II and
! later systems and others that support the `ll', `sc' and
! `sync' instructions. This can be overridden by passing
--with-llsc or --without-llsc when configuring GCC.
Since the Linux kernel emulates these instructions if they are
! missing, the default for `mips*-*-linux*' targets is
--with-llsc. The --with-llsc and
--without-llsc configure options may be overridden at compile
time by passing the -mllsc or -mno-llsc options to
--- 1030,1048 ----
__sync_* functions are available on MIPS II and
! later systems and others that support the ‘ll’, ‘sc’ and
! ‘sync’ instructions. This can be overridden by passing
--with-llsc or --without-llsc when configuring GCC.
Since the Linux kernel emulates these instructions if they are
! missing, the default for ‘mips*-*-linux*’ targets is
--with-llsc. The --with-llsc and
--without-llsc configure options may be overridden at compile
time by passing the -mllsc or -mno-llsc options to
*************** made after Nov. 9, 2006) should be free
*** 1084,1090 ****
mips-sgi-irix5
! mips-sgi-irix5
! test.o: ELF 64-bit MSB ...
test.o: ELF N32 MSB mips-3 ...
--- 1119,1134 ----
test.o: ELF 64-bit MSB ...
test.o: ELF N32 MSB mips-3 ...
*************** all on `mips3 test.o: ELF N32 MSB mips-4 ...
! memcmp. Either add -U__INLINE_INTRINSICS to the CC
--- 1136,1143 ----
test.o: ELF N32 MSB mips-4 ...
! memcmp. Either add -U__INLINE_INTRINSICS to the CC
*************** this is not required and currently cause
*** 1166,1178 ****
wchar_t support in `libstdc++' is not available for old
IRIX 6.5.x releases, x < 19. The problem cannot be autodetected
and in order to build GCC for such targets you need to configure with
--disable-wchar_t.
--- 1158,1170 ----
wchar_t support in ‘libstdc++’ is not available for old
IRIX 6.5.x releases, x < 19. The problem cannot be autodetected
and in order to build GCC for such targets you need to configure with
--disable-wchar_t.
*************** both 64-bit x86-64 and 32-bit x86 code (
*** 1608,1614 ****
xtensa-*-elf
xtensa-*-elf
--- 1621,1627 ----
position-independent code (PIC) regardless of whether the
-fpic or -fPIC options are used. In other
respects, this target is the same as the
! ‘xtensa-*-elf’ target.
diff -Nrcpad gcc-4.3.2/INSTALL/test.html gcc-4.3.3/INSTALL/test.html
*** gcc-4.3.2/INSTALL/test.html Wed Aug 27 18:09:38 2008
--- gcc-4.3.3/INSTALL/test.html Sat Jan 24 10:32:31 2009
***************
*** 3,9 ****