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 80E803858C2C; Wed, 20 Dec 2023 02:12:36 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 80E803858C2C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1703038356;
	bh=badZqX5cFp3MrX0XsUCaHIQffy9uEFn2M3iz1SxY/f4=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Jbc4t14QiwRjtPN1f+kF7nE64DvojtxCGiKtqVSCcU5BmqcGRk8/79gR68GaXVHEU
	 n7TIIhlYJp3Ig3Rpv7NDb+UD/Knor7ykpvTztBXclr1T+pig4djZao+5vMROjKbxcY
	 X9NP9ZBWdkFdhT9TVfXhvOOEXg7f5O9nKdc2/3Ps=
From: "juzhe.zhong at rivai dot ai" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113087] [14] RISC-V rv64gcv vector: Runtime mismatch
 with rv64gc
Date: Wed, 20 Dec 2023 02:12:36 +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: 14.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juzhe.zhong at rivai dot ai
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-113087-4-JoJIqQayaN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113087-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113087-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=3D113087

--- Comment #5 from JuzheZhong <juzhe.zhong at rivai dot ai> ---
(In reply to Patrick O'Neill from comment #4)
> I can attempt to reduce them however running an iteration of 549 takes
> multiple hours so it might be challenging using my current setup (creduce=
).
> Hopefully the random generator stumbles across the same issue and it can =
get
> fixed that way since it's worked for other spec fails previously.

I confirmed it is vsetvl bugs. But I wonder whether you have open source the
random generator ?

If yes, may be we can dedicate some resources to run random tests too.=