From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4913D3858C53; Thu, 4 Jan 2024 03:46:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4913D3858C53 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1704339984; bh=Tbfh+K3fnnfs6qG8MDqYkkNVq4e7zhoKuaBSPBNZTGE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=jRsH8wVauG8dwLa4nsZs5am1gD9Jj/xpCGLPGRCx6KAj4ZhqYppH3oxgZC/eIa8HF johnk2EYsEeJ0M0tJNN6KzbCvZJyHyLpOJ/I4wo4/ZJwozUYXg3pSCLgXtYhPdydpZ TYyBDN1Ws9wktagKNkThHyLImKEgnZVp7+Yhu73Q= From: "juzhe.zhong at rivai dot ai" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113206] [14] RISC-V rv64gcv vector: Runtime mismatch with rv64gc Date: Thu, 04 Jan 2024 03:46:22 +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=3D113206 --- Comment #8 from JuzheZhong --- It seems that we still didn't locate the real problem of failed SPEC you ra= n. Do you have any other ideas to locale the real problem ? Li Pan didn't locate the problem neither.=