aboutsummaryrefslogtreecommitdiff
path: root/bfd/elf32-d10v.c
diff options
context:
space:
mode:
authorNick Alcock <nick.alcock@oracle.com>2025-07-17 17:45:02 +0100
committerNick Alcock <nick.alcock@oracle.com>2025-07-23 13:06:16 +0100
commit4983bb052d3a57fe1b43334071ba61a8443bb5aa (patch)
treed23c5020b17d1d11893a511ce38d3c18ee62733f /bfd/elf32-d10v.c
parent4214ca9036c8f5d01025d0505ff1167700af5f98 (diff)
downloadbinutils-master.zip
binutils-master.tar.gz
binutils-master.tar.bz2
libctf: don't run tests requiring deduplicating linker unless one is in useHEADmaster
Before now, we were relying on gcc -B to repoint GCC at our freshly-built linker, and assuming we could use this to run tests that do linker dedup. This is, alas, not reliable (building --with-ld=/an/absolute/path bypasses -B searches for the linker), and we would like the libctf tests in particular to not fail if the compiler uses a linker that cannot deduplicate (simply skipping such tests). Add a new testsuite function that tries to link one of the lookup tests' testcases (which is known to produce conflicting types, i.e. a dict with per-translation-unit children) and then does an objdump and greps it for signs of the per-translation-unit children. If there are none, the linker probably just concatenated the sections: i.e., it is not a linker that can deduplicate CTF. libctf/ PR libctf/33162 * testsuite/config/default.exp (objdump): Introduce. (OBJDUMPFLAGS): Likewise. * testsuite/lib/ctf-lib.exp (check_ctf_linker_dedup): New. * testsuite/libctf-lookup/lookup.exp: Use it. * testsuite/libctf-regression/libctf-repeat-cu.exp: Likewise. * testsuite/libctf-regression/regression.exp: Likewise.
Diffstat (limited to 'bfd/elf32-d10v.c')
0 files changed, 0 insertions, 0 deletions