From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 6197D3858D35; Wed, 21 Jun 2023 15:07:35 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6197D3858D35
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1687360055;
	bh=Pr2kJiI/ailPUBxET9NxCew97ZVYIzN6DkoEZ4MfLBo=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=yuCkxRvN2aoARTP3cdlj15ZLQuvZ3A5oYnLs0YbE6RyYSmQe3gXnKbkq6BBjlJPMF
	 bQm6oUNBxqvd8EvfwWVKKefXzE3WzUrYkI8huOAcU2exxW9X6H6n3AAjTYc3aA8rJN
	 DtssKwqOsoAL8QrfZrZrPVQXsw1ZPG+e+9mpUw7w=
From: "adhemerval.zanella at linaro dot org"
 <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/30558] SIGEV_THREAD is badly implemented
Date: Wed, 21 Jun 2023 15:07:35 +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: adhemerval.zanella at linaro dot org
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: <bug-30558-131-sSB1z72Xfy@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30558-131@http.sourceware.org/bugzilla/>
References: <bug-30558-131@http.sourceware.org/bugzilla/>
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: <glibc-bugs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D30558

--- Comment #27 from Adhemerval Zanella <adhemerval.zanella at linaro dot o=
rg> ---
(In reply to Stas Sergeev from comment #26)
> But if you don't provide any checking
> method, then I won't be able to select
> between your code and timerfd impl, so
> I will have to keep using the timerfd
> code instead of yours.

Usually, if the semantic changes, a new symbol is provided to avoid
compatibility issues (I am not sure if it were the case). But for
implementation detail that changes over the release, glibc does not provide
additional user-visible defines that are not defined by standards (such any=
 C
TS/extension). Bleeding out implementation details has added a lo of
maintainability burden.

You can always check the release to tie, but non-visible user changes might=
 be
backported.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=