From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 356853858404; Mon, 12 Feb 2024 17:15:19 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 356853858404
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1707758119;
	bh=o1uZZsr+a7spNn1dsdtsiIhqqBDAACNbMrdGPcCKARQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Mqlw/Q/RdNLv+TZkg9LWZv6XSKgWXfm/y5pOf9prKbVebLPil31D0gG/nKUKJ0gA+
	 TAVETX9t9Q7K0z68/g/oG7SDnJWUN2Z6O0cVUGfuDqnFLGK9+4PnUs4z8j/Ki6TqMb
	 vPoRVCcjOWQFf3mVwumu+tQV4PB6XRyNcAIC84ic=
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113874] GNU2 TLS descriptor calls do not follow psABI on
 x86_64-linux-gnu
Date: Mon, 12 Feb 2024 17:15:18 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 13.2.1
X-Bugzilla-Keywords: ABI, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: MOVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-113874-4-mXZS2WJUsK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113874-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113874-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113874

--- Comment #32 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Michael Matz from comment #31)
> (In reply to H.J. Lu from comment #30)
> > (In reply to Michael Matz from comment #29)
> > > It not only can call malloc.  As the backtrace of H.J. shows, it quite
> > > clearly _does_ so :-)
> >=20
> > ld.so can only call the malloc implementation internal to ld.so.
>=20
> (And string functions for initializing that memory)  If that's ensured
> already
> everywhere: super.  Because I agree, that this is the best thing to do he=
re.
> From my perspective this is pure internal implementation details and hence
> setting up thread-local areas should not be expected to be interposable by
> users.
> (a custom allocator that isn't malloc or doesn't interact with it also wo=
uld
> work)

Since ia32 ld.so in glibc is compiled with:

Makefile:rtld-CFLAGS +=3D -mno-sse -mno-mmx -mfpmath=3D387

ia32 _dl_tlsdesc_dynamic is OK.=