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 45DD4385828B; Mon,  4 Dec 2023 13:09:37 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 45DD4385828B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1701695377;
	bh=n8HnpXOTku95BfXAlechxMlRoxKxuSrDkRdUVco2ZyA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=mkhOQxgvfIjUCuVMzRrcF0kPu08iWK7AZr7m+pfWDi61Z2+jxKfli+dYNxpbmGmr/
	 UZv3N+kHGOl4VzcjEYb/NzHQlB43Nhtw3Vw4YAFCe17GVwb70WPTocve4PmvfQZ7q8
	 UgTOFbZgWcVQIuEGNy8vfCV2knIxp0Ki58EGJin0=
From: "rdapp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112583] RISC-V regression testsuite errors with
 rv64gcv_zvl128b
Date: Mon, 04 Dec 2023 13:09: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: testsuite-fail
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rdapp at gcc dot gnu.org
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-112583-4-3wCp1ZPbBa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-112583-4@http.gcc.gnu.org/bugzilla/>
References: <bug-112583-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=3D112583

--- Comment #12 from Robin Dapp <rdapp at gcc dot gnu.org> ---
Ok, on my server the difference is that I didn't add vext_spec=3Dv1.0 to th=
e qemu
options.  This caused the qemu diagnostic which would of course not match t=
he
expected output.=