https://gcc.gnu.org/bugzilla/show_bug.cgi?id=126100
Bug ID: 126100
Summary: [17 Regression] aarch64 libsanitizer/tsan build fail
after r17-2093
Product: gcc
Version: 17.0
Status: UNCONFIRMED
Keywords: build, wrong-code
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: iains at gcc dot gnu.org
CC: pinskia at gcc dot gnu.org, srinath.parvathaneni at arm dot
com
Target Milestone: ---
Target: aarch64-linux
Created attachment 64925
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=64925&action=edit
good assembler (bz2) from a -save-temps invocation
After r17-2093-g97d9016b230cca98a I see a bootstrap fail in libsanitizer/tsan
on cfarm425 - aarcg64-linux.
Of course this could be just exposing an existing issue ...
Unfortunately, the problem disappears if I build with -save-temps and so I'm
stuck with attaching the working and non-working assembly.
There are a lot of differences which makes one think that there's perhaps a
GT(()) issue somewhere.
anyway, fortunately the failed case gets left in tmp.
$ as -v --gdwarf-5 -EL -mabi=lp64 -o t.o tsan_interceptors_posix-bad.s
GNU assembler version 2.46.50 (aarch64-linux-gnu) using BFD version (GNU
Binutils for Debian) 2.46.50.20260617
tsan_interceptors_posix-bad.s: Assembler messages:
tsan_interceptors_posix-bad.s:290177: Error: internal error: fixup not
contained within frag
====
Perhaps a red herring - but I also see a large number of
../../../src/libgomp/team.c:1115:1: note: non-delegitimized UNSPEC UNSPEC_TLS
(94) found in variable location
(also present before the patch)
but one of these is also seen in the tsan_interceptors_posix build (in case
it's relevant)
