public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sbence92 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94771] g++.dg/concepts/diagnostic10.C fails on mingw Date: Tue, 28 Apr 2020 08:07:10 +0000 [thread overview] Message-ID: <bug-94771-4-iIlI4ukLd2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94771-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94771 --- Comment #4 from Bence Szabó <sbence92 at gmail dot com> --- Interesting, the t.f syntax is not allowed anymore even with MSVC: https://godbolt.org/z/YCK-mv msvc also doesn't list under extensions_ https://docs.microsoft.com/en-us/cpp/build/reference/microsoft-extensions-to-c-and-cpp?view=vs-2015 and some recent overview on ms extensions: https://stackoverflow.com/questions/56554567/what-does-the-ms-extensions-flag-do-exactly-with-gcc Is this a dinosaur that forgot to die?
prev parent reply other threads:[~2020-04-28 8:07 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-26 9:59 [Bug c++/94771] New: " sbence92 at gmail dot com 2020-04-27 7:32 ` [Bug c++/94771] " iains at gcc dot gnu.org 2020-04-27 8:30 ` redi at gcc dot gnu.org 2020-04-27 8:56 ` redi at gcc dot gnu.org 2020-04-28 8:07 ` sbence92 at gmail dot com [this message]
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-94771-4-iIlI4ukLd2@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).