public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
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 10:54:57 +0000 [thread overview] Message-ID: <bug-108965-4-4JcoFzRf4A@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108965-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108965 --- Comment #3 from Christopher Friedt <chrisfriedt at gmail dot com> --- 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.
next prev parent reply other threads:[~2023-02-28 10:54 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-28 10:03 [Bug c++/108965] New: " chrisfriedt at gmail dot com 2023-02-28 10:20 ` [Bug c++/108965] " redi at gcc dot gnu.org 2023-02-28 10:35 ` redi at gcc dot gnu.org 2023-02-28 10:54 ` chrisfriedt at gmail dot com [this message] 2023-02-28 11:02 ` pinskia at gcc dot gnu.org 2023-02-28 11:50 ` redi at gcc dot gnu.org 2023-02-28 12:28 ` chrisfriedt at gmail dot com 2023-02-28 12:37 ` redi at gcc dot gnu.org 2023-02-28 12:40 ` chrisfriedt at gmail dot com 2023-02-28 12:48 ` redi at gcc dot gnu.org 2023-02-28 12:58 ` chrisfriedt at gmail dot com 2023-02-28 13:34 ` chrisfriedt at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-108965-4-4JcoFzRf4A@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).