From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 2EAD93858C2F; Thu,  3 Nov 2022 11:44:51 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2EAD93858C2F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1667475891;
	bh=P3c4rlDu2r8r7vWPZapI4Xh/jBRNyMLt2uKRF3lBY88=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Ow47Cirsnu632OwY+N+DCulcpIhChabiUNDBvy+Ls5D4/2solUKpb1nlGHfq36qYS
	 VcPbjgONWNn3S46nqPQXKLjDHzPrUVSGKArLnVsA9CKk7FTqUr8tf2EbCWw5ffXoEn
	 zq6/6NLlluvYuDE5qMT0kSugc2i1jMFStFOkCeqc=
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29249] csu/libc-tls.c:202: undefined reference to
 `_startup_fatal_not_constant'
Date: Thu, 03 Nov 2022 11:44:50 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Version: 2.35
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fweimer at redhat dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: fweimer at redhat dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-29249-131-0FX90qAQgB@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29249-131@http.sourceware.org/bugzilla/>
References: <bug-29249-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <glibc-bugs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D29249

--- Comment #16 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Szabolcs Nagy from comment #15)
> we hit this on arm with gcc-trunk and -O2 after a recent change.
>=20
> i think TLS_INIT_TP should just indicate failure and then the caller can
> print a generic message. i don't think arch specific message is very
> important for this.

Yeah, that's reasonable, I'll to come up with a patch.

Failure is also less likely here because of the mmap fallback we introduced.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=