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 BEC363858CDB; Wed, 25 Oct 2023 17:36:19 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BEC363858CDB
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1698255379;
	bh=CuQrdg2pcDPzxH2DdG1GxB0BELtctzKKclHyRGTZ2pw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=byFrdc/XRZW6IelB6/c8hPpCov+Ut+gnNIaEStiQuwxl7e5OXnhIn+yGBqK2XPjkg
	 fxGRbnXj/qAmfB2/eaGFWlYew/oovEVJ3qXzI3JnU4Pu6JsZ2AKSqd/5BxTCFa5TGj
	 QpWtMa1MP+t2CmFNXA+fyqVdEdw6C7aB/x2nLpYI=
From: "patrick at rivosinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/111969] RISC-V rv32gcv: 12 grouped flaky failures
Date: Wed, 25 Oct 2023 17:36:19 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: testsuite-fail
X-Bugzilla-Severity: normal
X-Bugzilla-Who: patrick at rivosinc dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
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-111969-4-dXXQ3XAfeD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-111969-4@http.gcc.gnu.org/bugzilla/>
References: <bug-111969-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=3D111969

--- Comment #3 from Patrick O'Neill <patrick at rivosinc dot com> ---
These may be real failures that manifest in QEMU depending on the GCC used =
to
compile it.

I built qemu with r14-4098-gbdb7d85dde5 which caused the failures.
> QEMU_CPU=3Drv32,vlen=3D128,v=3Dtrue,vext_spec=3Dv1.0,Zve32f=3Dtrue,Zve64f=
=3Dtrue ../build-3/bin/qemu-riscv32 large_2.exe
>   0.333333333333333333333333333333333317         2.2427199859366781911250=
0193394291495E+1644
> STOP 1

Building again with r14-4875-g9cf2e7441ee, I can execute both the new=20
> QEMU_CPU=3Drv32,vlen=3D128,v=3Dtrue,vext_spec=3Dv1.0,Zve32f=3Dtrue,Zve64f=
=3Dtrue ./bin/qemu-riscv32 ./large_2.exe
_and_ the old exe:
> QEMU_CPU=3Drv32,vlen=3D128,v=3Dtrue,vext_spec=3Dv1.0,Zve32f=3Dtrue,Zve64f=
=3Dtrue ./bin/qemu-riscv32 ../../tc-oct-24-baseline-flaky/build/large_2.exe
with no issues/failures.

When I run r14-4875-g9cf2e7441ee large_2.exe on r14-4098-gbdb7d85dde5 QEMU,=
 I
get the same failure:
> QEMU_CPU=3Drv32,vlen=3D128,v=3Dtrue,vext_spec=3Dv1.0,Zve32f=3Dtrue,Zve64f=
=3Dtrue ../build-3/bin/qemu-riscv32 ../../tc-oct-24-baseline-flaky/build/la=
rge_2.exe
>   0.333333333333333333333333333333333317         2.2427199859366781911250=
0193394291495E+1644
> STOP 1

So it seems to be a QEMU issue that is caused by GCC?=