From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B9A883858D37; Tue, 20 Sep 2022 07:47:42 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B9A883858D37 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1663660062; bh=Jl37Wt6m2KxLP/7SvZucJ7gUxGUsVcqVxUtiaJqQM3M=; h=From:To:Subject:Date:In-Reply-To:References:From; b=AYaowdf8KPJOXmqKcHLsIYVbhb3TDaDQGVuy+L5KwCIOKTSAryCUqqjhn+0vhDmnX 1Ob2LwgrxxgAogu9Uwy37O1o+A4CT8qwIxY3q26rsd4qhmsadpg5t9eTr8+/LaYhik fwHEFVTP5racN7eFRGd1Z/KG6nKafAgipuXlWMNI= From: "valera.mironow at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/106772] atomic::wait shouldn't touch waiter pool if used platform wait Date: Tue, 20 Sep 2022 07:47:42 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: valera.mironow at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.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://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106772 --- Comment #5 from Mkkt Bkkt --- Single reason why I want to use atomic::wait/notify is cross platform api f= or futex, wait/wake on address, ulock, etc Not because I need YOU decide instead of me how many spins, or other optimization I need. boost::atomic already do this. Why do you cannot make same?=