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 4AACC3858D33; Tue, 28 Feb 2023 11:02:48 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4AACC3858D33
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1677582168;
	bh=fk6GpQlJBqsKH8BeBq65+brRY41T+2G/liit6C+i9y0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=KyeHsJHW/mti+C3e/HxyEvVkpQ2Bcw9F08/jo/3y1mBfj/zdJPZtLZMMRQOaX3YM0
	 ggqzA+LvZLsMCS4Hqy6YZMZSoFNbhgrRQEbi7A/KLyCvfx5dJA9fQ0AsWJNbNjz4TW
	 OxTkJgG/3HX6KZCE2YFcWag5uSvasllapuKDMymU=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108965] g++: unable to parse c11 _Generics
Date: Tue, 28 Feb 2023 11:02: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: 11.3.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: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108965-4-P0NqzNvs8g@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108965-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=3D108965

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Christopher Friedt from comment #3)
> All you need to do is look at the example above pulled directly from
> cppreference.com, but please simply gaslight the user if that's an easier
> path to resolution for you.

There is no gaslighting going on. In fact now you just being abusive for wh=
at
end?

The facts are:
The _Generic is only part of the C standard and not part of the C++ standar=
d.
They are two different things.

Gcc's C++ frontend has never implemented _Generic support. GCC's C frontend
does though.=20
The C and C++ frontends in gcc do share some code but the parser has never =
been
shared.=