From: Arthur Norman <acn1@cam.ac.uk>
To: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Cc: cygwin@cygwin.com
Subject: Re: linker fails with multiple definitions after inline thread_local var within class
Date: Fri, 15 Nov 2019 08:14:00 -0000 [thread overview]
Message-ID: <alpine.WNT.2.00.1911150742490.125704@panamint> (raw)
In-Reply-To: <f5b26568-67dc-1dfe-a35b-248f1644aed9@SystematicSw.ab.ca>
> You appear to be running into a conflict with Cygwin managing Windows TLS, as
> Cygwin does its own messing around to support Unix/Linux/POSIX/g++ semantics for
> TLS and everything else under Windows. You should either use the supplied API,
> or write a Windows program that allows you to control TLS within Windows rules
> on what you can do with it. Otherwise you will have to get deep into the
> changeable and not directly supported underbelly of the Cygwin implementation.
Than you for the prompt response, but while the motivation for my example
involved the Windows native TLS API the sample code that fails to link for
me does not touch that at all and tried to be generic C++ code. Where it
superficially appears that the cygwin TLS initialization code fails to
pick up the "inline" attribute that I believe it should inherit from the
fact that the TLS fields and methods that I use are inline and hence
allowed to be defined/declared multiple times. So does my sample code that
fails breach the C++ standard or is this a Cygwin limitation please?
Arthur
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-11-15 7:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 18:41 Arthur Norman
2019-11-14 23:45 ` Brian Inglis
2019-11-15 8:14 ` Arthur Norman [this message]
2019-11-15 22:07 ` Brian Inglis
2019-11-16 3:35 ` Arthur Norman
2019-11-16 3:54 ` Brian Inglis
2019-11-16 10:48 ` Brian Inglis
2019-11-17 21:05 ` Arthur Norman
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=alpine.WNT.2.00.1911150742490.125704@panamint \
--to=acn1@cam.ac.uk \
--cc=Brian.Inglis@SystematicSw.ab.ca \
--cc=cygwin@cygwin.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).