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 052DC386F81D; Thu,  4 Jan 2024 22:31:00 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 052DC386F81D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1704407461;
	bh=jWsY7IWQGPmnGDo+gi5szoTLidx9gmdgTKs175u9/TI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=mU3K/W38nQcpFprT971cfVQ2IszwCl6b6qYwscoRjGg5qs02GnKDgUFT88X0Oq51N
	 rDq2QWpTMplh8FXjAgTgZw+xj1JOstTsBWnUkTLFBvTKvhuwJSLXQtydQy47163kK5
	 Mi6C3jbcYUq7LlvgBYTqsfLL9VDfzj3nLvyvDmes=
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: Thu, 04 Jan 2024 22:31:00 +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-t4VL3spD9D@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 #28 from JuzheZhong <juzhe.zhong at rivai dot ai> ---
(In reply to Patrick O'Neill from comment #27)
> Linking the discussion/plan here since more interested people are CCd her=
e.
>=20
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113206#c9
> Using 4a0a8dc1b88408222b88e10278017189f6144602, the spec run failed on:
> zvl128b (All runtime fails):
> 527.cam4 (Runtime)
> 531.deepsjeng (Runtime)
> 521.wrf (Runtime)
> 523.xalancbmk (Runtime)
>=20
> zvl256b:
> 507.cactuBSSN (Runtime)
> 521.wrf (Build)
> 527.cam4 (Runtime)
> 531.deepsjeng (Runtime)
> 549.fotonik3d (Runtime)
>=20
> With that info I think the next steps are:
> 1. Triage the zvl256b 521.wrf build failure
> 2. Bisect the newly-failing testcases
> 3. Finish triaging the remaining testcases the fuzzer found
> 4. Attempt to manually reduce cam4 for zvl128b (since it seems to have the
> fastest build+runtime)
> 5. Attempt to manually reduce other fails.

Plz reduce cam4 for zvl128b first. No need to care about build fail of wrf.
We already know the reason, it's middle-end issue which takes some time.=