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 24A9E385AF92; Tue, 25 Jul 2023 17:17:23 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 24A9E385AF92
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1690305443;
	bh=O47NY9XUssJ3uDqnSTVByeNCAYjAMXFwXEqpCwT/TWA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=QERtnzDzA32+pdMnIRjlNY5Xism56GofyuECMGXyqtnrw8Z9FVQImtBXyqzRCW/W5
	 y+iHuMpq8wWwatQNDyK8U305HHngK3beVGz/lMozLrblmo1U9Xb2CDWhSiVEBAcYlC
	 +GGB/HKizFJmK7iGsidMTTAQCuZu8dfQP/sVIxvI=
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/110796] builtin_iseqsig fails some tests in
 armv8l-linux-gnueabihf
Date: Tue, 25 Jul 2023 17:17: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: fxcoudert at gcc dot gnu.org
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-110796-4-neXqFNEVTC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110796-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=3D110796

--- Comment #8 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> =
---
(In reply to Richard Earnshaw from comment #6)
> Is the exception status supposed to be in a defined state when the test
> runs?  Shouldn't there be a call to feclearexcept (FE_ALL_EXCEPT) at the
> start of the test?

Isn't the exception status guaranteed to be defined (and not signaling) when
the program starts?

But adding feclearexcept (FE_ALL_EXCEPT); at the beginning of main() could =
not
hurt, for sure.=