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 4A7D13858C5E; Fri, 22 Dec 2023 23:10:37 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4A7D13858C5E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1703286637;
	bh=WpJCeI2i7bUOmk7GIwS9uNzrApyEVVoPXvrk+WUjIbk=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=i7OxbONXIrYg5l1dTqXX2Jc0G4KrS7mOx3g59hAG+LKfx6Vjfnm0ABQ3VacTlCYH4
	 rgGahhJLnMW2B/TSzwWco2FXxnFnYVmsd4Mj2tKOKUvpdZsSC7VxEcOV585vM8NcYi
	 2YUKMpLeHloD2xxwU+ZDee7ng+yZPiIlt7JXoJsE=
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: Fri, 22 Dec 2023 23:10: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: RESOLVED
X-Bugzilla-Resolution: FIXED
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-SHtizgSZCT@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 #17 from JuzheZhong <juzhe.zhong at rivai dot ai> ---
PLCT told me they passed with zvl256b.

I always run SPEC with FIXED-VLMAX since we always care about peak performa=
nce
on our board.=