public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94336] template keyword accepted before destructor names Date: Thu, 26 Mar 2020 09:50:51 +0000 [thread overview] Message-ID: <bug-94336-4-OszkOxWrKP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94336-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94336 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2020-03-26 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- EDG also accepts it, and clang 9.0.1 segfaults! clang 11 rejects it: d.cc:1:50: error: unknown type name 'X' template<typename T> void f(T *p) { p->template ~X(); } ^ 1 error generated.
next prev parent reply other threads:[~2020-03-26 9:50 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-26 1:26 [Bug c++/94336] New: " mpolacek at gcc dot gnu.org 2020-03-26 9:50 ` redi at gcc dot gnu.org [this message] 2020-03-26 12:58 ` [Bug c++/94336] " mpolacek at gcc dot gnu.org 2020-03-26 22:51 ` mpolacek at gcc dot gnu.org 2020-03-27 2:08 ` cvs-commit at gcc dot gnu.org 2020-03-27 2:09 ` mpolacek 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-94336-4-OszkOxWrKP@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).