invoke.texi (-static-libgcc): Explicitly mention non-GNU linkers.

	* doc/invoke.texi (-static-libgcc): Explicitly mention
	non-GNU linkers.

From-SVN: r82529

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index afd82a891f6ba08ca0ce90a6f3078e7e7e6cf919..8d3b14975773343dbb5aec6b670d10e232432876 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2004-06-01  Eric Botcazou  <ebotcazou@libertysurf.fr>
+
+       * doc/invoke.texi (-static-libgcc): Explicitly mention
+       non-GNU linkers.
+
 2004-06-01  Bernardo Innocenti  <bernie@develer.com>
 
        PR target/12968

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 41c474f8df80fb5b0d50c221343d9f431a6213c9..70656da195082dc36f6189dfe03983de1cffcf6b 100644 (file)
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -5488,14 +5488,14 @@ this is the right thing to do.
 
 If, instead, you use the GCC driver to create shared libraries, you may
 find that they will not always be linked with the shared @file{libgcc}.
-If GCC finds, at its configuration time, that you have a GNU linker that
-does not support option @option{--eh-frame-hdr}, it will link the shared
-version of @file{libgcc} into shared libraries by default.  Otherwise,
-it will take advantage of the linker and optimize away the linking with
-the shared version of @file{libgcc}, linking with the static version of
-libgcc by default.  This allows exceptions to propagate through such
-shared libraries, without incurring relocation costs at library load
-time.
+If GCC finds, at its configuration time, that you have a non-GNU linker
+or a GNU linker that does not support option @option{--eh-frame-hdr},
+it will link the shared version of @file{libgcc} into shared libraries
+by default.  Otherwise, it will take advantage of the linker and optimize
+away the linking with the shared version of @file{libgcc}, linking with
+the static version of libgcc by default.  This allows exceptions to
+propagate through such shared libraries, without incurring relocation
+costs at library load time.
 
 However, if a library or main executable is supposed to throw or catch
 exceptions, you must link it using the G++ or GCJ driver, as appropriate