Necessary for creating some of the generated source files for GCC@.
If in doubt, use a recent GNU awk version.
-@item GNU binutils
+@item GNU Binutils
Necessary in some circumstances, optional in others. See the
host/target specific instructions for your platform for the exact
@item --with-mips-plt
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
+SVR4-based MIPS ABIs and require support from GNU Binutils
and the runtime C library.
@item --with-stack-clash-protection-guard-size=@var{size}
Note that if an error occurs in any step the make process will exit.
-If you are not building GNU binutils in the same source tree as GCC,
+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
@file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
@heading *-*-freebsd*
FreeBSD using the ELF file format with DWARF 2 debugging.
-We recommend bootstrapping against the latest GNU binutils or the
+We recommend bootstrapping against the latest GNU Binutils or the
version found in the @file{devel/binutils} port. This also has been
known to enable additional features and improve overall testsuite
results.
@heading nvptx-*-none
Nvidia PTX target.
-Instead of GNU binutils, you will need to install
+Instead of GNU Binutils, you will need to install
@uref{https://github.com/SourceryTools/nvptx-tools,,nvptx-tools}.
Tell GCC where to find it:
@option{--with-build-time-tools=[install-nvptx-tools]/nvptx-none/bin}.
You can specify a default version for the @option{-mcpu=@var{cpu_type}}
switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
-You will need GNU binutils 2.20 or newer.
+You will need GNU Binutils 2.20 or newer.
@html
<hr />
--with-as=@//usr/@/gnu/@/bin/@/as}.
For linking, the Solaris linker is preferred. If you want to use the
-GNU linker instead, the version in Solaris 11.4, from GNU binutils
+GNU linker instead, the version in Solaris 11.4, from GNU Binutils
2.30.1 or newer (in @file{/usr/gnu/bin/ld} and @file{/usr/bin/gld}),
works. However, it
generally lacks platform specific features, so better stay with Solaris
-@command{ld}. When using the version from GNU binutils 2.44, there's
+@command{ld}. When using the version from GNU Binutils 2.44, there's
an important caveat: binutils @emph{must} be configured with
@code{CONFIG_SHELL=/bin/bash}, otherwise the linker's built-in linker
scripts get corrupted on x86. To use the LTO linker plugin
-(@option{-fuse-linker-plugin}) with GNU @command{ld}, GNU binutils
+(@option{-fuse-linker-plugin}) with GNU @command{ld}, GNU Binutils
@emph{must} be configured with @option{--enable-largefile}. To use
Solaris @command{ld}, we recommend to configure with
@option{--without-gnu-ld --with-ld=@//usr/@/bin/@/ld} to guarantee the
To enable symbol versioning in @samp{libstdc++} and other runtime
libraries with the Solaris linker, you need to have any version of GNU
-@command{c++filt}, which is part of GNU binutils. Symbol versioning
+@command{c++filt}, which is part of GNU Binutils. Symbol versioning
will be disabled if no appropriate version is found. Solaris
@command{c++filt} from the Solaris Studio compilers does @emph{not}
work.
@end html
@anchor{sparc-sun-solaris2}
@heading sparc-sun-solaris2*
-When GCC is configured to use GNU binutils 2.14 or later, the binaries
+When GCC is configured to use GNU Binutils 2.14 or later, the binaries
produced are smaller than the ones produced using Solaris native tools;
this difference is quite significant for binaries containing debugging
information.
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,
+the latest official GNU Binutils release in the Cygwin distribution,
or version 2.20 or above if building your own.
@html