ld: correct description of behavior for symbols redefined by script

Prior to 89753bbf8102 ("Warn when a script redefines a symbol") there
was no diagnostic at all. As of that commit, it's a warning, not an
error.

diff --git a/ld/ChangeLog b/ld/ChangeLog
index 2339a4014cdfe932c177f3e1553ac923701e6466..a94be7526b4ac5ed3f4e2db686d098b729402d5c 100644 (file)
--- a/ld/ChangeLog
+++ b/ld/ChangeLog
@@ -1,3 +1,7 @@
+2021-02-25  Jan Beulich  <jbeulich@suse.com>
+
+       * ld.texi (PROVIDE): Downgrade "error" to "diagnostic".
+
 2021-02-21  Alan Modra  <amodra@gmail.com>
 
        * ldexp.c (exp_fold_tree_1): Warn on script defining a symbol

diff --git a/ld/ld.texi b/ld/ld.texi
index bfe6c5994a1b238af79a425c5487567a97956543..9643818e3ed3a745d085549cc0a4b873cce90ecf 100644 (file)
--- a/ld/ld.texi
+++ b/ld/ld.texi
@@ -4447,8 +4447,8 @@ SECTIONS
 @end smallexample
 
 In this example, if the program defines @samp{_etext} (with a leading
-underscore), the linker will give a multiple definition error.  If, on
-the other hand, the program defines @samp{etext} (with no leading
+underscore), the linker will give a multiple definition diagnostic.  If,
+on the other hand, the program defines @samp{etext} (with no leading
 underscore), the linker will silently use the definition in the program.
 If the program references @samp{etext} but does not define it, the
 linker will use the definition in the linker script.