Gerald Pfeifer <[email protected]> writes:
> Sam noticed that we had GNU Binutils capitalized inconsistently in
> doc/invoke.texi which motivated me to check other parts of our docs.
>
> This patch addresses the majority of remaining occurrences in our docs.
>
> Pushed.
>
> Gerald
Thanks for doing that, I should've thought to look around too, but was
focused on invoke.texi at the time.
>
>
> gcc:
> PR target/69374
> * doc/install.texi (Prerequisites): Properly capitalize
> GNU Binutils.
> (Configuration): Ditto.
> (Building): Ditto.
> (Specific): Ditto.
> ---
> gcc/doc/install.texi | 24 ++++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
> index c399b1f2055..fc771448274 100644
> --- a/gcc/doc/install.texi
> +++ b/gcc/doc/install.texi
> @@ -383,7 +383,7 @@ Necessary to build the lexical analysis module.
> 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
> @@ -1867,7 +1867,7 @@ On MIPS targets, make @option{-mno-msa} the default
> when no
> @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}
> @@ -3302,7 +3302,7 @@ Build runtime libraries using the compiler from the
> previous step.
>
> Note that if an error occurs in any step the make process will exit.
>
> -If you are not building GNU binutils in the same source tree as GCC,
> +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
> @@ -4229,7 +4229,7 @@ This configuration is intended for embedded systems.
> @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.
> @@ -4706,7 +4706,7 @@ Andes NDS32 target in big endian mode.
> @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}.
> @@ -4759,7 +4759,7 @@ The OpenRISC 1000 32-bit processor with delay slots.
> 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 />
> @@ -4945,15 +4945,15 @@ assembler in @file{/usr/bin/as} work almost as well,
> though. To use GNU
> --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
> @@ -4968,7 +4968,7 @@ corruption at runtime in some cases for C++ programs.
>
> 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.
> @@ -5007,7 +5007,7 @@ in @uref{prerequisites.html,,the prerequisites}.
> @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.
> @@ -5219,7 +5219,7 @@ with Microsoft's C++ compiler and there are no plans to
> make it do so.
> 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
