From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 89D3D385B180; Tue, 29 Nov 2022 08:11:37 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 89D3D385B180 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1669709497; bh=s3ZhQvEMoOYO8IktkaujAihit2IRLs+qlyirEAlMPmk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=PHlhYm3AprP8wG8YCAZbD+orf41EGnlEBkJJpFfDtrs7ApiRF4a64NNVHSYe+pHDp 3wxgzuVwkNeTb5Icsdh26PYDlzS7ISO0NCjV/YtMYDd2XSmdyL+cjqRH65z61WLoRZ NSKHRRSxxh7b1ihaKPAK/UkV9JcAe2jVTJOIp+vo= From: "fw at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104688] gcc and libatomic can use SSE for 128-bit atomic loads on Intel and AMD CPUs with AVX Date: Tue, 29 Nov 2022 08:11:25 +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.0 X-Bugzilla-Keywords: missed-optimization, patch X-Bugzilla-Severity: normal X-Bugzilla-Who: fw at gcc dot gnu.org X-Bugzilla-Status: NEW 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: 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=3D104688 --- Comment #28 from Florian Weimer --- (In reply to Peter Cordes from comment #27) > (In reply to Alexander Monakov from comment #26) > > Sure, the right course of action seems to be to simply document that at= omic > > types and built-ins are meant to be used on "common" (writeback) memory >=20 > Agreed. Where in the manual should this go? Maybe a new subsection of t= he > chapter about __atomic builtins where we document per-ISA requirements for > them to actually work? Maybe this belongs in the ABI manual? For example, the POWER ABI says that memcpy needs to work on device memory. Documenting the required memory types for automics seems along the same lines. The rules are also potentially different for different targets sharing the = same processor architecture.=