From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D59CB3858C35; Mon, 12 Feb 2024 17:03:27 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D59CB3858C35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1707757407; bh=GSQ6wnWC7UCa7b/exEGNIMoK6lndkQVH+uuOoGA7FpI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=XDrvDQm+vTh8xSbm9ceglFZtKK/5anqML5yHZr1qfBl9gEFx5Xlhy88pSKfx0ar8U 2aupvEmbvSYfW4yPN0XCgv/gpn+GH1PLhLANwh8pSfI+LfaLhmXRd91h/g5qpnoC9p 8MjSHDUI46lPZJD5Y0RtEqb7fmbNvpYjTy9pfLv4= From: "matz at gcc dot 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:03:27 +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: matz at gcc dot gnu.org 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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113874 --- Comment #29 from Michael Matz --- It not only can call malloc. As the backtrace of H.J. shows, it quite clea= rly _does_ so :-) That's why there is talk earlier in this report about potentially not using malloc as one-time allocator for thread-local areas at all, or allocate the memory at a different time that from __tls_get_addr.=