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 C977E3857C44; Thu, 10 Nov 2022 18:16:47 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C977E3857C44
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1668104207;
	bh=pZvnqNQOxsQyXqXlIWwOEbYhaxtGGrlgnx3CQDbDe9g=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=i8mhWWQUZhh6shHRsmuGT4tPKzIo+yPNHxQbrBUcFmhkSEvSygGazwQdQiwevlXoP
	 nHY/WkRqR/n4NZvDTTnQgxfatH9AGDCKIejl2RG2/X72FFl58VvTtKimqgoHax/6JL
	 G+N8oL+vxavWzfwDqIGxyiJ3ejIzNdnIwLAHxs/w=
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: Thu, 10 Nov 2022 18:16:47 +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-U0gTioBmhA@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 #11 from Sergey Fedorov <vital.had at gmail dot com> ---
(In reply to Andrew Pinski from comment #8)
> No preprocessed source of the code going wrong.
> Not even register state or instructions where the segfault is happening
> (this is would be very useful but not required).

I am on 10.6 PPC (10A190) now and cannot reboot into 10.5.8, so attaching .=
ii
file from there, but the failure happens on Leopard just as well.=