public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/112858] [14 Regression] nvptx: 'unresolved symbol __cxa_thread_atexit_impl' Date: Thu, 07 Dec 2023 03:56:13 +0000 [thread overview] Message-ID: <bug-112858-4-6FwD7k9pYR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112858-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112858 --- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Alexandre Oliva <aoliva@gcc.gnu.org>: https://gcc.gnu.org/g:3d0f3382fa7b5677f35a9becf75ac436cd7eda7b commit r14-6261-g3d0f3382fa7b5677f35a9becf75ac436cd7eda7b Author: Alexandre Oliva <oliva@adacore.com> Date: Thu Dec 7 00:38:14 2023 -0300 libsupc++: try cxa_thread_atexit_impl at runtime g++.dg/tls/thread_local-order2.C fails when the toolchain is built for a platform that lacks __cxa_thread_atexit_impl, even if the program is built and run using that toolchain on a (later) platform that offers __cxa_thread_atexit_impl. This patch adds runtime testing for __cxa_thread_atexit_impl on select platforms (GNU variants, for starters) that support weak symbols. for libstdc++-v3/ChangeLog PR libstdc++/112858 * config/os/gnu-linux/os_defines.h (_GLIBCXX_MAY_HAVE___CXA_THREAD_ATEXIT_IMPL): Define. * libsupc++/atexit_thread.cc [__GXX_WEAK__ && _GLIBCXX_MAY_HAVE___CXA_THREAD_ATEXIT_IMPL] (__cxa_thread_atexit): Add dynamic detection of __cxa_thread_atexit_impl.
next prev parent reply other threads:[~2023-12-07 3:56 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-05 7:49 [Bug target/112858] New: " tschwinge at gcc dot gnu.org 2023-12-05 8:07 ` [Bug target/112858] " tschwinge at gcc dot gnu.org 2023-12-05 8:18 ` tschwinge at gcc dot gnu.org 2023-12-05 19:09 ` [Bug libstdc++/112858] [14 Regression] " pinskia at gcc dot gnu.org 2023-12-05 23:23 ` dje at gcc dot gnu.org 2023-12-06 12:05 ` tschwinge at gcc dot gnu.org 2023-12-06 21:36 ` aoliva at gcc dot gnu.org 2023-12-07 3:56 ` cvs-commit at gcc dot gnu.org [this message] 2024-02-06 10:56 ` redi at gcc dot gnu.org 2024-03-27 13:48 ` [Bug libstdc++/112858] " rguenth at gcc dot gnu.org
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-112858-4-6FwD7k9pYR@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).