From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 8CA9E38A90A1; Mon, 14 Nov 2022 13:57:02 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8CA9E38A90A1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1668434222;
	bh=rn3RX+LIwhVwQ14B5k5CURzb2V4vaQo9UPxuKM4ll98=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=p224cPTg90y2XjxAyvItDr7Nl2xyo1yDiwNWM2CnYyya5i4nvGPRWJGqq8qa9pfcy
	 lVHng9sZBshEr1bSu95n0ebl2b44YbPs0nesnlHDHdwF4Ee7hfKNu6A+ePkv0gX+4O
	 KUSv0X8GRRr+lbmm/xbPmmbIJ7YpcnLjlKPB8hlM=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107676] Nonsensical docs for -mrelax-cmpxchg-loop
Date: Mon, 14 Nov 2022 13:57:02 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 12.2.1
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
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: <bug-107676-4-XJaglhFbfu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107676-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107676-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107676

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Is it really better to do a load and check rather than just hoist the first
cmpxchg out of the loop, and add the pause in the loop if retrying?=