public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fw at gcc dot gnu.org" <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 10:46:27 +0000 [thread overview] Message-ID: <bug-113874-4-DgQXK7VnbR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113874-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113874 --- Comment #11 from Florian Weimer <fw at gcc dot gnu.org> --- (In reply to Richard Biener from comment #10) > I think a glibc fix would be very much preferred. It's a bit of a maintenance nightmare because we have to update the code slightly each time new registers are added, and there isn't a good way for applications to detect whether they run on a compatible glibc. > Is -mtls-dialect=gnu2 > supposed to work on a per-TU base or are all parts of an executable + loaded > shlibs required to have the same setting? It's possible to link various TLS variants together, and they should interoperate.
next prev parent reply other threads:[~2024-02-12 10:46 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-11 13:59 [Bug target/113874] New: " fw at gcc dot gnu.org 2024-02-11 14:03 ` [Bug target/113874] " fw at gcc dot gnu.org 2024-02-11 14:56 ` jakub at gcc dot gnu.org 2024-02-11 15:05 ` hjl.tools at gmail dot com 2024-02-11 17:57 ` hjl.tools at gmail dot com 2024-02-11 18:00 ` jakub at gcc dot gnu.org 2024-02-11 18:37 ` fw at gcc dot gnu.org 2024-02-11 19:47 ` hjl.tools at gmail dot com 2024-02-11 21:05 ` jakub at gcc dot gnu.org 2024-02-12 7:01 ` fw at gcc dot gnu.org 2024-02-12 8:53 ` rguenth at gcc dot gnu.org 2024-02-12 10:46 ` fw at gcc dot gnu.org [this message] 2024-02-12 10:53 ` jakub at gcc dot gnu.org 2024-02-12 10:53 ` jakub at gcc dot gnu.org 2024-02-12 10:56 ` rguenth at gcc dot gnu.org 2024-02-12 11:01 ` jakub at gcc dot gnu.org 2024-02-12 11:30 ` rguenth at gcc dot gnu.org 2024-02-12 11:41 ` rguenth at gcc dot gnu.org 2024-02-12 12:17 ` fw at gcc dot gnu.org 2024-02-12 12:24 ` hjl.tools at gmail dot com 2024-02-12 12:32 ` fw at gcc dot gnu.org 2024-02-12 12:37 ` hjl.tools at gmail dot com 2024-02-12 14:27 ` jakub at gcc dot gnu.org 2024-02-12 14:41 ` hjl.tools at gmail dot com 2024-02-12 14:42 ` hjl.tools at gmail dot com 2024-02-12 14:45 ` jakub at gcc dot gnu.org 2024-02-12 16:53 ` hjl.tools at gmail dot com 2024-02-12 16:59 ` jakub at gcc dot gnu.org 2024-02-12 17:02 ` hjl.tools at gmail dot com 2024-02-12 17:03 ` matz at gcc dot gnu.org 2024-02-12 17:08 ` hjl.tools at gmail dot com 2024-02-12 17:13 ` matz at gcc dot gnu.org 2024-02-12 17:15 ` hjl.tools at gmail dot com 2024-02-12 17:16 ` hjl.tools at gmail dot com 2024-02-12 17:17 ` hjl.tools at gmail dot com 2024-02-12 17:21 ` schwab@linux-m68k.org 2024-02-12 17:30 ` hjl.tools at gmail dot com 2024-02-12 17:38 ` schwab@linux-m68k.org 2024-02-13 4:19 ` hjl.tools at gmail dot com 2024-02-13 8:34 ` rguenth at gcc dot gnu.org 2024-02-13 9:00 ` nsz at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-113874-4-DgQXK7VnbR@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).