From owner-sc22wg14+sc22wg14-domo2=www.open-std.org@open-std.org  Fri Mar 14 10:38:31 2025
Return-Path: <owner-sc22wg14+sc22wg14-domo2=www.open-std.org@open-std.org>
X-Original-To: sc22wg14-domo2
Delivered-To: sc22wg14-domo2@www.open-std.org
Received: by www.open-std.org (Postfix, from userid 521)
	id 57C8B356898; Fri, 14 Mar 2025 10:38:31 +0100 (CET)
Delivered-To: sc22wg14@open-std.org
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104])
	by www.open-std.org (Postfix) with ESMTP id 07663356642
	for <sc22wg14@open-std.org>; Fri, 14 Mar 2025 10:38:29 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
  d=inria.fr; s=dc;
  h=date:from:to:cc:subject:message-id:in-reply-to:
   references:mime-version:content-transfer-encoding;
  bh=HVG8Sz1I7VlSj4E9mmQHE/KvIlNr0kZ3rIvYzMMFIlI=;
  b=OOPGbmmty+xAJX95H7bs3Q9W3g+1h3IcMUfjNcnMFIuq/rn8ceqV+NZm
   m7+QClhWFFAN7H7Euja3uDIEz5xoY4ZEvWxpNu+s0I3kBgU22XE9FLi2g
   +OD1235Lx/03xgrDiVeQCvF7xPTmkxqwceLZc7l0ZAsSfMk5MCHh23ZxP
   w=;
Authentication-Results: mail3-relais-sop.national.inria.fr; dkim=none (message not signed) header.i=none; spf=SoftFail smtp.mailfrom=jens.gustedt@inria.fr; dmarc=fail (p=none dis=none) d=inria.fr
X-IronPort-AV: E=Sophos;i="6.14,246,1736809200"; 
   d="scan'208";a="111552526"
Received: from unknown (HELO inria.fr) ([130.79.192.235])
  by mail3-relais-sop.national.inria.fr with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Mar 2025 10:38:29 +0100
Date: Fri, 14 Mar 2025 10:38:28 +0100
From: =?UTF-8?B?SuKCkeKCmeKCmw==?= Gustedt <jens.gustedt@inria.fr>
To: Joseph Myers <josmyers@redhat.com>
Cc: sc22wg14@open-std.org
Subject: Re: [SC22WG14.29698] New issue #1010: Termination of the execution
 with threads
Message-ID: <20250314103828.20eca3bd@inria.fr>
In-Reply-To: <20250313170725.419253567FC@www.open-std.org>
References: <20250313170725.419253567FC@www.open-std.org>
Organization: inria.fr
X-Mailer: Claws Mail 4.2.0 (GTK 3.24.41; x86_64-pc-linux-gnu)
X-Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAAXNSR0IArs4c6QAAACRQTFRFERslNjAsLTE9Ok9wUk9TaUs8iWhSrYZkj42Rz6aD3sGZ
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Sender: owner-sc22wg14@open-std.org
Precedence: bulk

Hi,
after thinking about this a bit more, I found that the change that I
suggested is not even sufficient. This is because the concept of a
"last thread" is not even well defined.

on Thu, 13 Mar 2025 17:07:17 +0000 you (Joseph Myers
<josmyers@redhat.com>) wrote:

> > The program terminates normally after the last thread has been
> > terminated. The behavior is as if the <del>program</del> <ins>end of
> > the call to `thrd_exit` of this last thread synchronized with all
> > terminations of other threads of the execution and thereafter
> > is</ins> called the `exit` function with the status `EXIT_SUCCESS`
> > <del>at thread termination time</del>. =20

My new suggestion would be

  The program <ins>execution</ins> terminates <del>normally</del>
  <ins>eventually</ins> after the <del>last thread has</del> <ins>all
  of its threads have</ins> been terminated. The behavior is as if the
  <del>program</del> <ins>end of a call to `thrd_exit` of a designated
  last thread synchronized with all terminations of other threads of
  the execution and thereafter is</ins> called the `exit` function
  with the status `EXIT_SUCCESS` <del>at thread termination
  time</del>.

Thanks
J=E2=82=91=E2=82=99=E2=82=9B

--=20
:: ICube :::::::::::::::::::::::::::::: deputy director ::
:: Universit=C3=A9 de Strasbourg :::::::::::::::::::::: ICPS ::
:: INRIA antenne de Strasbourg :::::::::::::::::: Camus ::
:: INRIA PIQ program Strasbourg :::::::::: piq.inria.fr ::
:: :::::::::::::::::::::::::::::::::::: =E2=98=8E +33 368854536 ::
:: https://icube-icps.unistra.fr/index.php/Jens_Gustedt ::