* Fw: [isocpp-parallel] WG14 n3917 - Program termination in the presence of multiple threads
@ 2026-07-14 17:58 Paul E. McKenney
2026-07-14 20:16 ` Florian Weimer
0 siblings, 1 reply; 2+ messages in thread
From: Paul E. McKenney @ 2026-07-14 17:58 UTC (permalink / raw)
To: linux-toolchains
Just FYI. Unless I am missing something, this would not affect the
Linux kernel. But I could be missing something...
This proposal defines orphaned threads as those persisting past
program termination, for a Linux-kernel example of termination, a call
to panic(). It also includes some advice, which might be criticized
as being incomplete, but on the other hand, all of this was previously
undefined. ;-)
Thanx, Paul
----- Forwarded message from David Goldblatt via Parallel <parallel@lists.isocpp.org> -----
Date: Tue, 14 Jul 2026 10:42:34 -0700
From: David Goldblatt via Parallel <parallel@lists.isocpp.org>
To: SG1 concurrency and parallelism <parallel@lists.isocpp.org>
Reply-To: parallel@lists.isocpp.org
Cc: David Goldblatt <davidtgoldblatt@gmail.com>
Subject: [isocpp-parallel] WG14 n3917 - Program termination in the presence of
multiple threads
Link <https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3917.htm>
WG14 will likely discuss this in Ottawa. I don't have a ton of time for
WG14 stuff these days, but some people on this reflector might have
opinions.
- David
_______________________________________________
Parallel mailing list
Parallel@lists.isocpp.org
Subscription: https://lists.isocpp.org/mailman/listinfo.cgi/parallel
Searchable archives: http://lists.isocpp.org/parallel/2026/07/index.php
----- End forwarded message -----
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Fw: [isocpp-parallel] WG14 n3917 - Program termination in the presence of multiple threads
2026-07-14 17:58 Fw: [isocpp-parallel] WG14 n3917 - Program termination in the presence of multiple threads Paul E. McKenney
@ 2026-07-14 20:16 ` Florian Weimer
0 siblings, 0 replies; 2+ messages in thread
From: Florian Weimer @ 2026-07-14 20:16 UTC (permalink / raw)
To: Paul E. McKenney; +Cc: linux-toolchains
* Paul E. McKenney:
> Just FYI. Unless I am missing something, this would not affect the
> Linux kernel. But I could be missing something...
This seems to require new behavior?
* SYS_tkill and SYS_tgkill with signal SIGABRT terminate the current
thread or a group of threads abnormally
The proposal is a bit weird to me. It seems to discourage using an
atexit handler to shut down a service thread (by synchronizing with it).
Thanks,
Florian
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-07-14 20:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-14 17:58 Fw: [isocpp-parallel] WG14 n3917 - Program termination in the presence of multiple threads Paul E. McKenney
2026-07-14 20:16 ` Florian Weimer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox