public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pacoarjonilla at yahoo dot es" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94592] ICE in non-type template parameter with constexpr constructor Date: Tue, 14 Apr 2020 11:41:07 +0000 [thread overview] Message-ID: <bug-94592-4-8Tsnab8UN2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94592-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94592 Paco Arjonilla <pacoarjonilla at yahoo dot es> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|ice-on-invalid-code |ice-on-valid-code --- Comment #3 from Paco Arjonilla <pacoarjonilla at yahoo dot es> --- It should be valid code. https://wg21.link/P0732R2 The reason why other compilers reject it is because they have not implemented it yet. https://en.cppreference.com/w/cpp/compiler_support Class types in non-type template parameters (Around halfway of C++20 language features)
next prev parent reply other threads:[~2020-04-14 11:41 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-14 10:44 [Bug c++/94592] New: " pacoarjonilla at yahoo dot es 2020-04-14 10:49 ` [Bug c++/94592] " rguenth at gcc dot gnu.org 2020-04-14 11:16 ` marxin at gcc dot gnu.org 2020-04-14 11:41 ` pacoarjonilla at yahoo dot es [this message] 2020-04-14 14:32 ` mpolacek at gcc dot gnu.org 2020-04-14 16:29 ` mpolacek at gcc dot gnu.org 2020-04-14 16:38 ` pacoarjonilla at yahoo dot es 2020-04-15 17:57 ` [Bug c++/94592] [10 Regression] " mpolacek at gcc dot gnu.org 2020-04-18 3:43 ` mpolacek at gcc dot gnu.org 2020-04-20 13:57 ` rguenth at gcc dot gnu.org 2020-04-20 23:55 ` cvs-commit at gcc dot gnu.org 2020-04-20 23:55 ` 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-94592-4-8Tsnab8UN2@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).