public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/27004] ld.so is miscompiled by GCC 11
Date: Thu, 03 Dec 2020 12:51:36 +0000 [thread overview]
Message-ID: <bug-27004-131-X2QfJ9h4G8@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27004-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27004
--- Comment #6 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Florian Weimer from comment #4)
> __builtin_thread_pointer is potentially trapping (which is the root of the
> problem). Does GCC know about that? It also results in a load followed by an
> add, instead of a single load, I think. Using the __segfs or __seggs
> namespaces looks preferable to me.
OK. Shouldn't all %fs references be replaced by __seg_fs?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-12-03 12:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 23:06 [Bug dynamic-link/27004] New: " hjl.tools at gmail dot com
2020-12-02 23:51 ` [Bug dynamic-link/27004] " hjl.tools at gmail dot com
2020-12-03 3:47 ` carlos at redhat dot com
2020-12-03 10:16 ` fweimer at redhat dot com
2020-12-03 11:24 ` jakub at redhat dot com
2020-12-03 12:37 ` hjl.tools at gmail dot com
2020-12-03 12:43 ` fweimer at redhat dot com
2020-12-03 12:51 ` jakub at redhat dot com
2020-12-03 12:51 ` hjl.tools at gmail dot com [this message]
2020-12-03 12:52 ` fweimer at redhat dot com
2020-12-03 12:53 ` fweimer at redhat dot com
2020-12-08 0:46 ` hjl.tools at gmail 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-27004-131-X2QfJ9h4G8@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: link
Be 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).