From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 76EEE3858D38; Wed, 24 Jan 2024 07:24:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 76EEE3858D38 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1706081099; bh=qBWTkit/sTGA935lKyuOM9iBGu4zAjfLuTJyaxPi6qM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=PPcItO/Abs58cR3w2AZFFZ5epEMcTzkyPyotjzN/mEVRvi04xY+vPdTNn1+xjHZDM rixxRlxvAm/uGoS4w/sWz+yJxVN7h3WYWOxKgQ7OKzkVLw8Iodg6ZQxL9VJ/t7IieX 8ew8t7Ftmy7C+aDVCSqJk1yGEzE29J0piy4Zbwc0= From: "juzhe.zhong at rivai dot ai" 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:24:58 +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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113087 --- Comment #41 from JuzheZhong --- Hi, Patrick. Could you trigger test again base on latest trunk GCC? We have recent memory-hog fix patch: https://gcc.gnu.org/git/?p=3Dgcc.git;a=3Dcommit;h=3D3132d2d36b4705bb762e61b= 1c8ca4da7c78a8321 I want to make sure it doesn't cause a regression on SPEC. I have tested it with full coverage GCC testsuite, no regression. But I want to know about SPEC 2017=