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 D886E3858C2F; Mon,  5 Feb 2024 16:54:48 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D886E3858C2F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1707152088;
	bh=cZpn9u91peCymsFjjxoYCBNvlNWunZKq3fXWcY0JAOM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=ijLz9qemIOGGKPWaIbStopVURARaTI/ilnce3+he8gtpWzQWBSvUkeML1P0mxesWZ
	 k3bwF8VAYCCpFzpVBoccplpjRRvlLewDIz4E3yp8Cphu8Xw2sCuYPqMurMyEdWIFfl
	 Sy/bKmMkZp0eaBYBFu1I7N7VMfK9EB5gF4kNxejI=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113770] _Float64x support on g++ 13.2.0
Date: Mon, 05 Feb 2024 16:54:48 +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: 13.2.0
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 bug_status
Message-ID: <bug-113770-4-JO97lSoeNv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113770-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113770-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=3D113770

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
As described, this is not a bug.=