From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id AD5FC3858C74; Tue, 20 Sep 2022 14:40:29 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AD5FC3858C74 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1663684829; bh=vXJTMLoRuGLFEI6K1mey6YsKX/8vgu8mHxlYmZU0Y1E=; h=From:To:Subject:Date:In-Reply-To:References:From; b=SWeZIaUo6BRT0X01RZPZo/YKO+6ox4a3oUqJQ06DrnYQib3nU9Zl+FluM7HTkrEOv 7EZ7YypBrw8BHZgURBQc1bMwU0WSc055k37GRlkU6pSHBcKGZ+EgRS4cvVZP5mg8xs 7CwV9CTYLcRCWP9Q0N7u5PtxYVD0CA2e5rnMpbBM= From: "rodgertq at gcc dot gnu.org" 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 14:40:29 +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: rodgertq at gcc dot gnu.org 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 #11 from Thomas Rodgers --- (In reply to Mkkt Bkkt from comment #9) > Why do you think you smarter than msvc stl, libc++, boost::atomic develop= ers? >=20 > Maybe it's about your "I"? I should ignore this (see jwakely's response), but - I very much don't think I am smarter than the person (ogiroux@apple.com) who implemented libc++'s implementation. There are minor difference between libstc++'s details and libc++'s but in this regard,in particular, they beha= ve the same.=