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++/95989] Segmentation fault compiling with static libraries and using jthread::request_stop
Date: Fri, 03 Mar 2023 19:10:31 +0000 [thread overview]
Message-ID: <bug-95989-4-sJPqpa5z2u@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95989-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95989
--- Comment #23 from CVS 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:21edd841611a97442a6b95e8ec7e91ff8fd3a451
commit r13-6461-g21edd841611a97442a6b95e8ec7e91ff8fd3a451
Author: Alexandre Oliva <oliva@adacore.com>
Date: Fri Mar 3 15:59:36 2023 -0300
link pthread_join from std::thread ctor
Like pthread_create, pthread_join may fail to be statically linked in
absent strong uses, so add to user code strong references to both when
std::thread objects are created.
for libstdc++-v3/ChangeLog
PR libstdc++/104852
PR libstdc++/95989
PR libstdc++/52590
* include/bits/std_thread.h (thread::_M_thread_deps): New
static implicitly-inline member function.
(std::thread template ctor): Pass it to _M_start_thread.
* src/c++11/thread.cc (thread::_M_start_thread): Name depend
parameter, force it live on entry.
next prev parent reply other threads:[~2023-03-03 19:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 20:25 [Bug libstdc++/95989] New: " webrown.cpp at gmail dot com
2020-06-30 22:35 ` [Bug libstdc++/95989] " redi at gcc dot gnu.org
2020-06-30 22:59 ` antal.buss at ualberta dot ca
2020-06-30 23:21 ` redi at gcc dot gnu.org
2020-06-30 23:30 ` redi at gcc dot gnu.org
2020-06-30 23:39 ` redi at gcc dot gnu.org
2020-07-01 10:15 ` redi at gcc dot gnu.org
2020-07-01 13:28 ` fw at gcc dot gnu.org
2020-07-01 13:53 ` redi at gcc dot gnu.org
2020-07-06 12:38 ` fw at gcc dot gnu.org
2020-07-08 14:39 ` redi at gcc dot gnu.org
2020-07-08 15:36 ` redi at gcc dot gnu.org
2020-07-09 9:58 ` redi at gcc dot gnu.org
2020-11-11 17:26 ` redi at gcc dot gnu.org
2020-11-19 21:07 ` cvs-commit at gcc dot gnu.org
2020-11-20 13:49 ` cvs-commit at gcc dot gnu.org
2020-11-20 13:52 ` redi at gcc dot gnu.org
2021-09-21 13:42 ` ebotcazou at gcc dot gnu.org
2022-03-04 4:08 ` lightningdzeyenr at gmail dot com
2022-03-04 9:25 ` redi at gcc dot gnu.org
2022-03-09 4:27 ` lightningdzeyenr at gmail dot com
2023-03-03 19:10 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-10 12:56 ` redi at gcc dot gnu.org
2024-04-10 17:32 ` pinskia 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-95989-4-sJPqpa5z2u@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: 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).