From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5366A3858C2F; Wed, 15 Feb 2023 12:27:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5366A3858C2F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1676464029; bh=uxw76Rcy/DVcBr8V8JBqjm87lNAeWi7yYuNjMW0TXl0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=KOK+z/bUygyB/FfkbeZB41IfX+SKoHTp8dGBEvveh4YhQfBA2dNRt75PAqHizYWVL usfml2F9HVdp71oGIy14tas8iPmgJiKEWv2c8VpMoWYe3dnVLEZjz81LF/XsHlpSbI CuK1HsfeHWUoCrBabsdXR8vmK2ia9ua7WNcD+u8o= From: "segher 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: Wed, 15 Feb 2023 12:27:06 +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: segher 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 #29 from Segher Boessenkool --- (In reply to Florian Weimer from comment #28) > Maybe this belongs in the ABI manual? For example, the POWER ABI says that > memcpy needs to work on device memory. Huh?! Where do you see this? The way you state it it is trivially impossible to implement, so if we really say that it needs fixing asap.=