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 34B283858C33; Fri,  2 Sep 2022 10:48:35 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 34B283858C33
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1662115715;
	bh=GaT/O62qsXQ1dVCI6OFgPE3Wh+GPv2s8WKdXQZfblcw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=htnKS/S+5f9eFwXzYlaVsn55xQp0m/WpjBebfShDU/zAMn5Ag6/EZYF3MONpNCK8G
	 wbKLmTjYX6j9IVkP4O1acLqP6V2/d0Jmu/5rOEAqvuDTvyjhnsR7QJPY+tkY+kqr6o
	 AV0HF8yi6eWnUJ2hcIQ/k9CoTGpiOJN+NzwvexIY=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/71579] type_traits miss checks for type completeness
 in some traits
Date: Fri, 02 Sep 2022 10:48:33 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.1.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
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-71579-4-bqFeRbahyI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-71579-4@http.gcc.gnu.org/bugzilla/>
References: <bug-71579-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=3D71579

--- Comment #23 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Yes, that's my reading of it. I need to check what other compilers do for
__has_virtual_destructor and check the docs. Maybe libstdc++ should only us=
e it
for class types.=