public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aacid at kde dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100384] New: Compiling in c++17 mode breaks compilation of functions named visit() Date: Sun, 02 May 2021 15:38:39 +0000 [thread overview] Message-ID: <bug-100384-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100384 Bug ID: 100384 Summary: Compiling in c++17 mode breaks compilation of functions named visit() Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: aacid at kde dot org Target Milestone: --- Created attachment 50733 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50733&action=edit main.cpp The attached code fails to compile with g++ --std=c++17 main.cpp I've tried with gcc 11.1 too and it fails too. To me it seems a bug in the implementation in which std::visit is leaking into the non std:: namespace, but maybe it's a bug in C++ specification?
next reply other threads:[~2021-05-02 15:38 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-02 15:38 aacid at kde dot org [this message] 2021-05-02 15:38 ` [Bug c++/100384] " aacid at kde dot org 2021-05-03 12:59 ` [Bug libstdc++/100384] " aacid at kde dot org 2021-05-03 14:08 ` redi at gcc dot gnu.org 2021-05-03 14:44 ` ppalka at gcc dot gnu.org 2021-05-03 19:51 ` redi at gcc dot gnu.org 2021-05-03 20:02 ` redi at gcc dot gnu.org 2021-05-04 11:19 ` cvs-commit at gcc dot gnu.org 2021-05-06 13:06 ` cvs-commit at gcc dot gnu.org 2021-06-18 12:56 ` cvs-commit at gcc dot gnu.org 2021-06-18 14:43 ` cvs-commit at gcc dot gnu.org 2021-06-18 14:46 ` redi at gcc dot gnu.org
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-100384-4@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).