aboutsummaryrefslogtreecommitdiff
path: root/gcc
diff options
context:
space:
mode:
authorSam James <sam@gentoo.org>2025-09-04 23:48:38 +0100
committerSam James <sam@gentoo.org>2025-09-06 19:41:03 +0100
commita2a4a6c05713afe17d8e66c3903c0da750e7aec5 (patch)
treed338195193424382db80f6427f3a23b5cf154398 /gcc
parente9a7140993b350e3dcf36a74394d7d16cb794203 (diff)
downloadgcc-a2a4a6c05713afe17d8e66c3903c0da750e7aec5.zip
gcc-a2a4a6c05713afe17d8e66c3903c0da750e7aec5.tar.gz
gcc-a2a4a6c05713afe17d8e66c3903c0da750e7aec5.tar.bz2
doc: update incremental link vs binutils information
GNU Binutils now supports linking LTO and non-LTO objects into a single mixed object file as of 2.44. Update the text to reflect this and fix some minor grammar issues while at it. gcc/ChangeLog: PR ipa/116410 * doc/invoke.texi (Link Options): Update -flinker-output= text to reflect GNU Binutils changes. Fix grammar.
Diffstat (limited to 'gcc')
-rw-r--r--gcc/doc/invoke.texi13
1 files changed, 6 insertions, 7 deletions
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index c0b7aab..9712398 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -19450,13 +19450,12 @@ link-time optimizations disabled (for example, cross-module inlining
happens), but most of benefits of whole program optimizations are lost.
During the incremental link (by @option{-r}) the linker plugin defaults to
-@option{rel}. With current interfaces to GNU Binutils it is however not
-possible to incrementally link LTO objects and non-LTO objects into a single
-mixed object file. If any of object files in incremental link cannot
-be used for link-time optimization, the linker plugin issues a warning and
-uses @samp{nolto-rel}. To maintain whole program optimization, it is
-recommended to link such objects into static library instead. Alternatively it
-is possible to use H.J. Lu's binutils with support for mixed objects.
+@option{rel}. GNU Binutils 2.44 or later is needed to incrementally link
+LTO objects and non-LTO objects into a single mixed object file. If any
+of the object files in an incremental link cannot be used for link-time
+optimization, the linker plugin issues a warning and uses @samp{nolto-rel}.
+To maintain whole program optimization, link such objects into a static
+library instead.
@opindex fuse-ld=bfd
@item -fuse-ld=bfd