ld: correct description of behavior for symbols redefined by script
Prior to 89753bbf81
("Warn when a script redefines a symbol") there
was no diagnostic at all. As of that commit, it's a warning, not an
error.
This commit is contained in:
parent
68337b8be3
commit
3c27360bc4
@ -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
|
||||
|
@ -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.
|
||||
|
Loading…
Reference in New Issue
Block a user