https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121078
Bug ID: 121078
Summary: [16 regression] gcc.dg/aru-2.c etc. FAIL
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: hjl.tools at gmail dot com
Target Milestone: ---
Target: i386-pc-solaris2.11
Between 20250711 (3e7dd06860bf0589bc743e458b16bd1d33d73835) and 20250714
(0eee2dd2865faf61d9d74425510421e20434ec03),
a couple of tests regressed on 64-bit Solaris/x86:
+FAIL: gcc.dg/aru-2.c (test for excess errors)
+UNRESOLVED: gcc.dg/aru-2.c compilation failed to produce executable
+FAIL: gcc.dg/nest.c (test for excess errors)
+UNRESOLVED: gcc.dg/nest.c compilation failed to produce executable
+FAIL: gcc.dg/pr32450.c (test for excess errors)
+UNRESOLVED: gcc.dg/pr32450.c compilation failed to produce executable
+FAIL: gcc.dg/pr43643.c (test for excess errors)
+UNRESOLVED: gcc.dg/pr43643.c compilation failed to produce executable
All of them FAIL in the same way:
Excess errors:
Undefined first referenced
symbol in file
__fentry__ /var/tmp//ccuy.gYc.o
ld: fatal: symbol referencing errors
which is no wonder, given that
commit 07d8de9174c421d719649639a1452b8b9f2eee32
Author: H.J. Lu <[email protected]>
Date: Wed Jul 2 08:58:23 2025 +0800
x86-64: Add --enable-x86-64-mfentry
already states that __fentry__ is a glibc-only addition, while the tests add
-mfentry on all x86 targets.
