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 5B66D3858D38; Wed, 24 Jan 2024 13:21:58 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5B66D3858D38
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1706102518;
	bh=Ct4HnA4HhwnI4S2rckozcTKhSn9EGhs6y4FHII1hHuw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=RbnTtvlYyzldjt86ocNWg23yDi9e73BhDRjfhvJ/wt9M3bFMvFXDDk6XEf2DhQd/E
	 I3z6vfEGVmqjSfwqCNypTuZ5SppEhYR9SAw2JcLt9/9OVcj9yHhcpN22yVHqSxkFxp
	 Xyyajo+W1BBSkP8OkN9oAVlgbSgd2GtCXN47XBhw=
From: "vital.had at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107590] __atomic_test_and_set broken on PowerPC
Date: Wed, 24 Jan 2024 13:21:55 +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: 11.3.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vital.had at gmail dot com
X-Bugzilla-Status: WAITING
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-107590-4-xRsf9CQkOx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107590-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107590-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=3D107590

--- Comment #16 from Sergey Fedorov <vital.had at gmail dot com> ---
(In reply to Andrew Pinski from comment #13)
> Oh yes there could be a bug here when the byte (lbarx/stbcx.) and half-wo=
rd
> (lharx/sthcx.) instruction support was added (which was for Power8;
> r0-123873-g4b02c96265fb52).

Any update on this by the way? It could be that we keep getting obscure
failures due to this issue being unfixed.=