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 2119F3858289; Fri, 26 May 2023 15:38:27 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2119F3858289
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1685115507;
	bh=tiqNL6rEgz/gHKejHgdlPjenHJrW71MBMcnbbDay7Tg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=gXtJ83gBhid+wtbyvKzuHm5tLvetriXw5oHWoxnuhyFBfsrA+3iW/rIzDMJQTwJx/
	 Bn6cN+tnfikV+wmN3LlfiYYm3YJKOhafRIj+AqYvIVgf/wtG0aZkiMLILRqtTJr25D
	 SH/IIHfyv/3sfGAwqRfBr51gkLNH0CERvW6jFVHk=
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109982] csmith: x86_64: znver1 issues
Date: Fri, 26 May 2023 15:38:26 +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: unknown
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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-109982-4-R57G3w8IT8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109982-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109982-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=3D109982

--- Comment #3 from Uro=C5=A1 Bizjak <ubizjak at gmail dot com> ---
(In reply to Uro=C5=A1 Bizjak from comment #1)
> Also fails with "-mtune=3Dznver1 -mavx":
>=20
> Program received signal SIGSEGV, Segmentation fault.
> 0x00000000004048ef in func_21 (p_22=3D0x41b330 <g_277>, p_23=3D0, p_24=3D=
8) at
> runData/keep/in.11.c:597
> 597     in runData/keep/in.11.c
> (gdb) disass $pc-10, $pc+10
> Dump of assembler code from 0x4048e5 to 0x4048f9:
>    0x00000000004048e5 <func_21+8160>:   mov    (%rax),%rdx
>    0x00000000004048e8 <func_21+8163>:   mov    -0x1378(%rbp),%rax
> =3D> 0x00000000004048ef <func_21+8170>:   vmovdqa (%rdx),%ymm0
>    0x00000000004048f3 <func_21+8174>:   vmovdqa %ymm0,(%rax)
>    0x00000000004048f7 <func_21+8178>:   vmovdqa 0x20(%rdx),%ymm0
> End of assembler dump.
> (gdb) p/x $rdx
> $3 =3D 0x41a824
>=20
> Unaligned access.

After some more analysis, the above *IS* unaligned access. At the end of
func_21, we have:

=3D> 0x00000000004048ef <+8170>:  vmovdqa (%rdx),%ymm0
   0x00000000004048f3 <+8174>:  vmovdqa %ymm0,(%rax)
   0x00000000004048f7 <+8178>:  vmovdqa 0x20(%rdx),%ymm0
   0x00000000004048fc <+8183>:  vmovdqa %ymm0,0x20(%rax)
   0x0000000000404901 <+8188>:  vmovdqa 0x40(%rdx),%ymm0
   0x0000000000404906 <+8193>:  vmovdqa %ymm0,0x40(%rax)
   0x000000000040490b <+8198>:  vmovdqa 0x60(%rdx),%ymm0
   0x0000000000404910 <+8203>:  vmovdqa %ymm0,0x60(%rax)

which looks like a memory copy to me. Unfortunately, the address is unalign=
ed:

(gdb) p/x $rdx
$2 =3D 0x41a824

Changing the above vmovdqa insns to vmovdqu results in a successful run.=