diff options
| author | Alan Modra <amodra@gmail.com> | 2024-04-08 08:16:20 +0930 |
|---|---|---|
| committer | Alan Modra <amodra@gmail.com> | 2024-04-08 11:27:42 +0930 |
| commit | 248b6326a49ed49e2f627d3bddbac514a074bac0 (patch) | |
| tree | 806188887cde0ebd7fcf9cabfec4a5558d4c3ee6 /opcodes | |
| parent | 261d6a6776b6d0652eab37552450e94cb9eec780 (diff) | |
| download | gdb-248b6326a49ed49e2f627d3bddbac514a074bac0.zip gdb-248b6326a49ed49e2f627d3bddbac514a074bac0.tar.gz gdb-248b6326a49ed49e2f627d3bddbac514a074bac0.tar.bz2 | |
Re: PR26978, Inconsistency for strong foo@v1 and weak foo@@v1
Commit 726d7d1ecf opened a hole that allowed a u.i.link loop to be
created, resulting in _bfd_generic_link_add_one_symbol never
returning. Fix that. Note that the MIND case handles two types of
redefinition. For a new indirect symbol we'll have string non-NULL.
For a new def, string will be NULL. So moving the string comparison
earlier would work. However, we've already looked up inh in the first
case so can dispense with name comparisons. Either way, for a new def
we'll get to the defweak test and possibly cycle. Which is what we
want here.
PR 31615
PR 26978
* linker.c (_bfd_generic_link_add_one_symbol <MIND>): Test for
exactly matching indirect symbols before cycling on a defweak.
Diffstat (limited to 'opcodes')
0 files changed, 0 insertions, 0 deletions