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 780273858C53; Tue, 28 Feb 2023 12:40:00 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 780273858C53
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1677588000;
	bh=Yrw9PJRJpIjqfj06Nn+ZU2B14dAsm0TK6wPB9L1OmJc=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=q/PHTsAuZ7yj3Sx2cyneqT/6PWnG4LLtxuN1UUgzgkih49RzMx339s/anSkfFZsqu
	 HbMb/EZ/Rc/Opg7miVGkj3Rf9ET1P5HMMp66kLh5sVNeWBC3FEenKwc5D0Qus3ckTh
	 Bdkt5qBw9Bdno/RPD3K8cycOtnnCkCYKJH003Qs8=
From: "chrisfriedt at gmail dot com" <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 12:40:00 +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: chrisfriedt at gmail dot com
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-KqUhVmOp2h@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 #8 from Christopher Friedt <chrisfriedt at gmail dot com> ---
My code is clearly valid C++ according to g++ :-)

Thanks for your help in any case.

On Tue, Feb 28, 2023, 7:38 AM redi at gcc dot gnu.org <
gcc-bugzilla@gcc.gnu.org> wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108965
>
> --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
> (In reply to Christopher Friedt from comment #6)
> > It's supported OOTB in `clang++` but fails in `g++`.
>
> Nobody is disputing that, but Clang supports lots of things that aren't
> valid
> in C++ and aren't supported by G++, and G++ supports things that aren't
> valid
> in C++ and aren't supported by Clang. That's not a bug.
>
> > The example above is the simplest example that illustrates the issue.
>
> Yes, and it's not valid C++.
>
> > I am not being abusive, but it certainly did feel like gaslighting to
> read
> > "you're doing it wrong" / close invalid without any consideration.
>
> I commented explaining that it's not in the C++ standard, and followed up
> in
> the github issue where the real bug is. That's hardly "without
> consideration".
> I've shown how to fix your C++ code to make it valid in C++11, and pointed
> out
> a problem in your C code using _Generic. I didn't have to do any of that,
> and I
> certainly won't bother doing so again.
>
> --
> You are receiving this mail because:
> You reported the bug.=