From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A97083858CDA; Thu, 22 Jun 2023 05:23:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A97083858CDA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1687411397; bh=NSKg1TMnNOzG5z9g5JoY12/TGSwag8ctH9FOPQrSUW8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=XsDMJb28dfEhivmrfLLDuNZoRT8/YiNGUql3GdpdZo0oV3k/94NivFbFjLKviTWeP 4o0tzD3QR4+443RO/9ubVRVZd3X1PUoMDplhJcJm0mVjthm0cHAHT3XYXvbrGaKSlC Xz4wzW1VWWwg0DnU2wy0oLcE4XlkVUwqEsqEhpNI= From: "stsp at users dot sourceforge.net" To: glibc-bugs@sourceware.org Subject: [Bug libc/30558] SIGEV_THREAD is badly implemented Date: Thu, 22 Jun 2023 05:23:17 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.37 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: stsp at users dot sourceforge.net X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30558 --- Comment #29 from Stas Sergeev --- Just for the record, I changed my mind and agreed with Adhemerval's reading of this: [quote] the threads created in response to a timer expiration are created detached [/quote] This only says *how* the threads, created in response to a timer expiration, are created. It doesn't say they should be created, just *iff* they are created, they are created detached. --=20 You are receiving this mail because: You are on the CC list for the bug.=