From: "H.J. Lu" <hjl.tools@gmail.com>
To: Nathan Sidwell <nathan@acm.org>
Cc: Jan Hubicka <hubicka@ucw.cz>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: tls-dialect gnu2
Date: Thu, 27 Jul 2017 22:30:00 -0000 [thread overview]
Message-ID: <CAMe9rOp_68qpdLz25PoHa1ewB6pGQuVv_+H5bXGFhU05MH9+Vg@mail.gmail.com> (raw)
In-Reply-To: <5bfee52c-11ff-67cb-139d-9fdaffb49bb8@acm.org>
On Thu, Jul 27, 2017 at 3:07 PM, Nathan Sidwell <nathan@acm.org> wrote:
> Jan,
> I notice the x86 default -mtls-dialect is GNU not GNU2. The latter was
> added in 2006. Is there a reason not to default to it now? (perhaps
> because of the ldso dependency?)
You may have noticed. There is zero test for -mtls-dialect=gnu2 on x86
in GCC and I only added one -mtls-dialect-gnu2 in glibc last year when
I fixed GNU2 TLS bug in glibc:
https://sourceware.org/bugzilla/show_bug.cgi?id=20309
So effectively, there is very little test for -mtls-dialect-gnu2 on x86.
--
H.J.
prev parent reply other threads:[~2017-07-27 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 22:07 Nathan Sidwell
2017-07-27 22:30 ` H.J. Lu [this message]
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=CAMe9rOp_68qpdLz25PoHa1ewB6pGQuVv_+H5bXGFhU05MH9+Vg@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=nathan@acm.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).