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 4B2A33858CDB; Wed, 24 Jan 2024 07:48:02 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4B2A33858CDB
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1706082482;
	bh=NHre9E/EoPgul6VBI+zs4N4BaBEox6PXksSGkrEz+pc=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=BX9sam7siNgh7tZvcDLTl24nL4Udgt0TSb0A6CwngNr3HOy84xzoJDkwuOAe0qpZI
	 I9G/eGOPQ3CDpPLaqguhRixULq+gQaMuoG5WJmEhc3mmMl9UF5qHunax/YsCesVPsi
	 ChBYtBKglQb0gdHkmFd7OYFZQDlnKoyKx1vij244=
From: "patrick at rivosinc dot com" <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, 24 Jan 2024 07:48:01 +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: patrick at rivosinc dot com
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-zlVBhWFvUY@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 #42 from Patrick O'Neill <patrick at rivosinc dot com> ---
(In reply to JuzheZhong from comment #41)
> Hi, Patrick.
>=20
> Could you trigger test again base on latest trunk GCC?
>=20
> We have recent memory-hog fix patch:
> https://gcc.gnu.org/git/?p=3Dgcc.git;a=3Dcommit;
> h=3D3132d2d36b4705bb762e61b1c8ca4da7c78a8321
>=20
> I want to make sure it doesn't cause a regression on SPEC.
>=20
> I have tested it with full coverage GCC testsuite, no regression.
>=20
> But I want to know about SPEC 2017

I kicked off a run roughly 10 hours ago with your memory-hog fix patch appl=
ied
to a1b2953924c451ce90a3fdce6841b63bf05f335f. I'll post the results here when
the runs complete. Thanks!=