From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 370B63858CD1; Thu, 4 Jan 2024 17:12:36 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 370B63858CD1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1704388356; bh=R3GEpJ12X+0qwOT5k6bWXPd5leiDp5NxQBD9tOqf1Xw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=hVbvqzwyud6hPeduok0lqbHDWlgMzJHC0taauR51bIOKIIOxXEg1BhBAbhjK3Yp7b Lsf0xmFh4OXdEImaq3OMr5+Qo/D7AJgkrgXW9l50roY+DOzPONDsE1SC8P4fv3WY6C fGDlEIEfwNrIXb3MX2gTkhUZy7o7vmN2SMWB2HZE= From: "patrick at rivosinc dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113087] [14] RISC-V rv64gcv vector: Runtime mismatch with rv64gc Date: Thu, 04 Jan 2024 17:12:28 +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: 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 #27 from Patrick O'Neill --- Linking the discussion/plan here since more interested people are CCd here. 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) zvl256b: 507.cactuBSSN (Runtime) 521.wrf (Build) 527.cam4 (Runtime) 531.deepsjeng (Runtime) 549.fotonik3d (Runtime) 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.=