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 1137F3858D3C; Fri, 10 Mar 2023 17:20:10 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1137F3858D3C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1678468810;
	bh=B9DuNlyjpdYSCrqeR57AqUtyBTjAh9bIsUgJVX5msJI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=L26gCtTgBsfHOwbrjg/R13/LBLrrmI6TGLXd7EYhumKOfa2o96qdbWQp9lyROAMdu
	 OHObMX5ushFILI1hPjEKMfNwgTg9iQeiwWVDK2nf5CLY9+wbfFoPg76O/HzutEAcsC
	 dfIWA78YNCt37CZ9kNbv5hbvLkhK8MRPWNHwD25A=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109087] [13 Regression] csmith: end of year runtime bug
 since r13-4839-geef81eefcdc2a581
Date: Fri, 10 Mar 2023 17:20:09 +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: 13.0
X-Bugzilla-Keywords: wrong-code
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: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109087-4-ubxjUMlIh2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109087-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109087-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=3D109087

--- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to David Binderman from comment #9)
> (In reply to Richard Biener from comment #6)
> > Try -fno-tree-vectorize?
>=20
> I tried that, and it made no difference at all.
>=20
> I also tried dropping the -march=3D setting back to znver1 and
> that also made no difference.

The change added znver1/2/3 to X86_TUNE_AVX256_MOVE_BY_PIECES,
X86_TUNE_AVX256_STORE_BY_PIECES also so must be related to that ...

Most likely a latent bug too ...

you might get a similar failure on alderlake or core_avx2 too.=