From: Rasmus Villemoes <rv@rasmusvillemoes.dk>
To: gcc-patches@gcc.gnu.org
Cc: Jerome Lambourg <lambourg@adacore.com>,
Olivier Hainque <hainque@adacore.com>,
Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Subject: [PATCH] libstdc++: only define _GLIBCXX_HAVE_TLS for VxWorks >= 6.6
Date: Mon, 8 Nov 2021 10:56:13 +0100 [thread overview]
Message-ID: <20211108095613.1214963-1-rasmus.villemoes@prevas.dk> (raw)
According to
https://gcc.gnu.org/legacy-ml/gcc-patches/2008-03/msg01698.html, the
TLS support, including the __tls_lookup function, was added to VxWorks
in 6.6.
It certainly doesn't exist on our VxWorks 5 platform, but the fallback
code in eh_globals.cc using __gthread_key_create() etc. used to work
just fine.
libstdc++-v3/ChangeLog:
* config/os/vxworks/os_defines.h (_GLIBCXX_HAVE_TLS): Only
define for VxWorks >= 6.6.
---
libstdc++-v3/config/os/vxworks/os_defines.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/libstdc++-v3/config/os/vxworks/os_defines.h b/libstdc++-v3/config/os/vxworks/os_defines.h
index c881b2b4b9e..75a68bc605b 100644
--- a/libstdc++-v3/config/os/vxworks/os_defines.h
+++ b/libstdc++-v3/config/os/vxworks/os_defines.h
@@ -45,8 +45,10 @@
#define _GLIBCXX_USE_WEAK_REF 0
#endif
-// We support TLS on VxWorks (either directly or with emutls)
+// We support TLS on VxWorks >= 6.6 (either directly or with emutls)
+#if !_VXWORKS_PRE(6, 6)
#define _GLIBCXX_HAVE_TLS 1
+#endif
// VxWorks7 comes with a DinkumWare library and the system headers which we
// are going to include for libstdc++ have a few related intrinsic
--
2.31.1
next reply other threads:[~2021-11-08 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 9:56 Rasmus Villemoes [this message]
2021-11-08 16:59 ` Olivier Hainque
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=20211108095613.1214963-1-rasmus.villemoes@prevas.dk \
--to=rv@rasmusvillemoes.dk \
--cc=gcc-patches@gcc.gnu.org \
--cc=hainque@adacore.com \
--cc=lambourg@adacore.com \
--cc=rasmus.villemoes@prevas.dk \
/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).