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 7010A3858C53; Fri,  1 Mar 2024 03:19:22 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7010A3858C53
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1709263162;
	bh=prTcJCpJ3XrveO0GOs/NqfiECHCUgZk08ox0UA8N/Ew=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=fIDyXcavNmR4p54A4sHR9fEthtd87OsxfYS0cBpTTNM9TLWdOgDL8ngFm1wZCkNOq
	 pKV3tsgqNF2Ln/ICJz7NY+rmaNHMr1JEQ9LbXsotebTYH96lUV1b//8D9yjHkU5mKr
	 MiTzKZhJ/W+MMaQLuV7xCBk+cXdChMC/iCg3+RQM=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/114181] issubnormal is a macro
Date: Fri, 01 Mar 2024 03:19:21 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
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: resolution
Message-ID: <bug-114181-4-oODgrb2UsD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114181-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114181-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=3D114181

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |INVALID

--- Comment #13 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to g.peterhoff from comment #12)=20
> Are there already plans how to deal with the
> https://en.cppreference.com/w/c/experimental/fpext1
> https://en.cppreference.com/w/c/experimental/fpext4
> regarding C++?

Well dfp is supported, or kinda of supported already for GCC, see PR 51364
also.

as far as fpext4 is concern, I suspect it might be better to take it up with
the C++ standards committee ...=