public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at zx2c4 dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/28595] glibc-2.34 build fails with linker error (TLS transition from R_386_TLS_GOTIE to R_386_TLS_LE_32 against `__libc_tsd_CTYPE_B' at 0xf4 in section `.text' failed) Date: Mon, 15 Nov 2021 14:24:46 +0000 [thread overview] Message-ID: <bug-28595-131-UrrfEo9lUe@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28595-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28595 --- Comment #10 from Jason A. Donenfeld <jason at zx2c4 dot com> --- Gcc seems to emit the same sort of reference. On -march=skylake that same snippet is: mov eax, ecx mov ecx, ds:(__libc_tsd_CTYPE_B_tpoff - _GLOBAL_OFFSET_TABLE_)[ebx] mov ecx, gs:[ecx] test byte ptr [ecx+eax*2+1], 20h jz short loc_80000B0 So I wonder if we're exposing a binutils bug here rather than a glibc or gcc one? Still not super certain what's up, though. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-11-15 14:24 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-15 5:25 [Bug libc/28595] New: " sam at gentoo dot org 2021-11-15 5:29 ` [Bug libc/28595] " sam at gentoo dot org 2021-11-15 5:30 ` sam at gentoo dot org 2021-11-15 5:35 ` [Bug build/28595] " sam at gentoo dot org 2021-11-15 5:36 ` sam at gentoo dot org 2021-11-15 9:09 ` schwab@linux-m68k.org 2021-11-15 13:38 ` jason at zx2c4 dot com 2021-11-15 13:53 ` jason at zx2c4 dot com 2021-11-15 13:59 ` jason at zx2c4 dot com 2021-11-15 14:02 ` jakub at redhat dot com 2021-11-15 14:14 ` jason at zx2c4 dot com 2021-11-15 14:24 ` jason at zx2c4 dot com [this message] 2021-11-15 14:28 ` jason at zx2c4 dot com 2021-11-15 19:29 ` fweimer at redhat dot com 2021-11-16 11:56 ` jason at zx2c4 dot com 2021-11-16 11:57 ` jason at zx2c4 dot com 2021-11-16 12:00 ` jason at zx2c4 dot com 2021-11-16 12:12 ` jason at zx2c4 dot com 2021-11-16 12:24 ` jason at zx2c4 dot com 2021-11-16 12:34 ` jakub at redhat dot com 2021-11-16 12:35 ` jakub at redhat dot com 2021-11-16 12:38 ` jakub at redhat dot com 2021-11-16 13:02 ` jason at zx2c4 dot com
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-28595-131-UrrfEo9lUe@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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).