| commit | 8fa7162be556f60fdbd146d2a38c1c7e776ead36 | [log] [tgz] |
|---|---|---|
| author | Jan Beulich <jbeulich@suse.com> | Mon Apr 14 14:23:53 2025 +0200 |
| committer | Jan Beulich <jbeulich@suse.com> | Mon Apr 14 14:23:53 2025 +0200 |
| tree | 7ea87fdc385dca977142355fa294be901ce782a2 | |
| parent | 7c96ca457993267db20d31d239e3d84c2c48f1ec [diff] |
bfd/ELF/x86: avoid layering violation in link hash table entry init There's no reason not to do as the comment says, just like all other architectures do when they need custom field: Call the allocation method of the "superclass". Which is the ELF one, of which in turn the BFD one is the "superclass", dealt with accordingly by _bfd_elf_link_hash_newfunc().