From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7DCC03858428; Fri, 24 Mar 2023 16:51:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7DCC03858428 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1679676708; bh=48BWqIPJULvf7lY9GKjBnOFgw5eB/mztl93jA5aaCMg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=CTS1tllzDKQXRd2UtlC1XG0tkb9gyVbi7zQFttPcS94uBzHpcM1KV6jLhoETh892N FS49d1XMPkx3wuOP5udE20xlj8PLODbRcV/BSmCUASkYYtyiMtU8Cbl4uKLo9j6Pci v7OmwYifsPDz37/9Jk+cQwes5RgEiPQ47HRSI03Y= From: "cvs-commit at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/108891] libatomic: AArch64 SEQ_CST 16-byte load missing barrier Date: Fri, 24 Mar 2023 16:51:48 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libgcc X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: wilco 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=3D108891 --- Comment #1 from CVS Commits --- The master branch has been updated by Wilco Dijkstra : https://gcc.gnu.org/g:1f641d6aba284e0c277e6684cd6b2c73591cd14d commit r13-6855-g1f641d6aba284e0c277e6684cd6b2c73591cd14d Author: Wilco Dijkstra Date: Fri Feb 10 17:41:05 2023 +0000 libatomic: Fix SEQ_CST 128-bit atomic load [PR108891] The LSE2 ifunc for 16-byte atomic load requires a barrier before the LD= P - without it, it effectively has Load-AcquirePC semantics similar to LDAP= R, which is less restrictive than what __ATOMIC_SEQ_CST requires. This pa= tch fixes this and adds comments to make it easier to see which sequence is used for each case. Use a load/store exclusive loop for store to simpl= ify testing memory ordering is correct (it is slightly faster too). libatomic/ PR libgcc/108891 * config/linux/aarch64/atomic_16.S: Fix libat_load_16_i1. Add comments describing the memory order.=