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 9C1403858423; Wed, 15 Feb 2023 16:07:47 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9C1403858423
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1676477267;
	bh=43H0GhygNhgUMR6ey7JaMXpL9MY6CdroKHMQNHHnc8g=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=ZJMfFJDSDL9y5RIvtPSJY/g4SMgrPbMd42jev93aw2lKV6Qp/sfBoS1dHgQwIxqW6
	 flC0CZrMbgUxnRYFYyltOWKGLTU923nuDsQyytNKN5pRbGBhDVYVlJ66SSpzz53hQF
	 cMKlpS136mVFGe/VlFqhiHucEf/C8bSxu1qcSdjM=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.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 16:07:46 +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: pinskia 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: <bug-104688-4-xgQpsF35jv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-104688-4@http.gcc.gnu.org/bugzilla/>
References: <bug-104688-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=3D104688

--- Comment #32 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Segher Boessenkool from comment #31)
> Yes, there was a user who incorrectly used memcpy on non-memory memory.
>From what I remember (it was also reported about aarch64 at one point too),=
 one
of the graphics libraries would call memcpy from normal memory to GPU Memory
(over PCIe) and memcpy will sometimes use unaligned accesses which causes a
fault to the GPU memory.=