Hi.
I'm sending couple of documentation tweaks that touch LTO, binutils auto-load
plugin
support and valid options of -march (on x86-64).
Martin
gcc/ChangeLog:
2018-03-29 Martin Liska <mli...@suse.cz>
PR lto/84995.
* doc/invoke.texi: Document how LTO works with debug info.
Describe auto-load support of binutils. Mention 'x86-64'
as valid option value of -march option.
---
gcc/doc/invoke.texi | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index feacd569ef3..424e426a390 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -9482,6 +9482,9 @@ types of hosts. The bytecode files are versioned and there is a
strict version check, so bytecode files generated in one version of
GCC do not work with an older or newer version of GCC.
+Link-time optimization on ELF/DWARF systems works with generation of debugging
+information. Other systems are currently not supported.
+
Link-time optimization does not work well with generation of debugging
information. Combining @option{-flto} with
@option{-g} is currently experimental and expected to produce unexpected
@@ -9565,6 +9568,11 @@ need to support linker plugins to allow a full-featured build environment
@command{gcc-nm}, @command{gcc-ranlib} wrappers to pass the right options
to these tools. With non fat LTO makefiles need to be modified to use them.
+Note that modern binutils provide plugin auto-load mechanism.
+Installing the linker plugin into @file{$libdir/bfd-plugins} has the same
+effect as usage of the command wrappers (@command{gcc-ar}, @command{gcc-nm} and
+@command{gcc-ranlib}).
+
The default is @option{-fno-fat-lto-objects} on targets with linker plugin
support.
@@ -26440,6 +26448,9 @@ the result might not run on different machines). Using @option{-mtune=native}
produces code optimized for the local machine under the constraints
of the selected instruction set.
+@item x86-64
+A generic CPU with 64-bit extensions.
+
@item i386
Original Intel i386 CPU@.
