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 849AE3857B83; Thu, 11 Jan 2024 01:13:23 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 849AE3857B83
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1704935603;
	bh=YHCJN8zJ6Gx1PfVMC2Jz51MkoJAsU9Me7v1XGmreMdE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=jl/SyBzpQhNzN86cMZzTt7cwT5RACOSG6Yp1GuiNelwtH14UghpP2+9CkVqGVJWe8
	 8wmWWEHvadQxNir5orCl4WvSVxiRmaYY9qV+Wi3qIlXsHJrwgioHyNwUEZXilN+bKQ
	 QtIhNCxGaY3QDei2sb7BpKp18upcQj+l4UwKixX8=
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, 11 Jan 2024 01:13: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: <bug-113087-4-YfFB01JjbS@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 #34 from JuzheZhong <juzhe.zhong at rivai dot ai> ---
(In reply to Patrick O'Neill from comment #32)
> (In reply to JuzheZhong from comment #31)
> > You are using -Ofast which will have precision issue on floating-point.
> >=20
> > You can reference it:
> >=20
> > https://godbolt.org/z/zzG8xbx95
> >=20
> > O3 result: 50002896.000000
> > Ofast result: 50005000.000000
> >=20
> > They are different and not correctness issue.
> >=20
> > GCC is same behavior as LLVM.
> >=20
> > More details:
> > https://github.com/llvm/llvm-project/issues/77044
> >=20
> > So, to elide the potential floating-point precision confusion,
> > I suggest you first use -O3 -ftrapping-math to test SPEC.
> >=20
> > Otherwise, it's really hard to locate the real issue.
>=20
> The cam4 failure still appears with:
> "-O3"
> "-ftrapping-math"
> "-mtune=3Dgeneric-ooo"
> "-march=3Drv64imafdcv_zba_zbb_zbs_zicond_zfa"
> "-fno-lto"
> "-ftree-vectorize"
> "--param=3Driscv-autovec-preference=3Dscalable"
>=20
> I'll keep digging through the harness and finding the remaining flags.

CAM4 is likely VSETVLI bug that Robin told me.

I mean the other failures.
Could you trigger a full run of SPEC with -O3 -ftrapping-math ?

To see how many bugs in SPEC actually.

I think we don't need to care about the failures which caused by floating-p=
oint
precision.=