From: Tom N <nospam@codesniffer.com>
To: Iain Sandoe <idsandoe@googlemail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>, Jonathan Wakely <jwakely.gcc@gmail.com>
Subject: Re: Building on Mac with --enable-tls
Date: Thu, 19 Mar 2020 09:54:54 -0400 (EDT) [thread overview]
Message-ID: <94274860.169386.1584626094837@email.ionos.com> (raw)
In-Reply-To: <96CBB48D-EACC-4D56-A827-CFAD8D9785ED@googlemail.com>
> On March 18, 2020 at 7:53 PM Iain Sandoe <idsandoe@googlemail.com> wrote:
>
> Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> >
> > I would expect the default to be correct for the target i.e.--disable-tls. If enabling it worked correctly, it would be the default.
> > That makes no sense, neither std::mutex nor std::unique_lock uses TLS.
>
> Darwin uses emulated TLS on all versions (powerpc, i686, x86_64) the correct default (to use emulatedTLS) is selected without requiring any additional configure options. Selecting --enable-tls will undoubtedly produce an invalid configuration.
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52268 is an enhancement PR to add native TLS for 10.7+ (but that would still not work on earlier versions, of course).
Thank you both for the quick responses! Knowing that lack of --enable-tls is normal on Mac set me in the right direction. The synchronization problem was due to an equally bad assumption. All working as expected now.
Thanks again!
next prev parent reply other threads:[~2020-03-19 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 19:14 Tom N
2020-03-18 23:05 ` Jonathan Wakely
2020-03-18 23:53 ` Iain Sandoe
2020-03-19 13:54 ` Tom N [this message]
2020-03-19 14:07 ` Jonathan Wakely
2020-03-21 17:26 ` Tom N
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=94274860.169386.1584626094837@email.ionos.com \
--to=nospam@codesniffer.com \
--cc=gcc-help@gcc.gnu.org \
--cc=idsandoe@googlemail.com \
--cc=jwakely.gcc@gmail.com \
/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).