public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109876] New: initializer_list not usable in constant expressions in a template Date: Tue, 16 May 2023 18:33:44 +0000 [thread overview] Message-ID: <bug-109876-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109876 Bug ID: 109876 Summary: initializer_list not usable in constant expressions in a template Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: barry.revzin at gmail dot com Target Milestone: --- Consider this example: #include <initializer_list> template <int S> struct Array { }; #ifdef USE_TEMPLATE template <int N> #endif struct Foo { static constexpr std::initializer_list<int> num = { 1, 2 }; Array<num.size()> ctx; }; #ifdef USE_TEMPLATE void f(Foo<5>) { } #else void f(Foo) { } #endif In all recent versions of gcc, compiling with -DUSE_TEMPLATE fails with an error like: <source>:15:17: in 'constexpr' expansion of 'Foo<N>::num.std::initializer_list<int>::size()' <source>:15:19: error: the value of 'Foo<N>::num' is not usable in a constant expression 15 | Array<num.size()> ctx; | ^ This used to work in gcc 7 and gcc 8 (except 8.1), and I don't think there's anything about Foo being a template that should prevent this from working. The non-template case works on all gcc versions I've tried.
next reply other threads:[~2023-05-16 18:33 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-16 18:33 barry.revzin at gmail dot com [this message] 2023-05-16 18:40 ` [Bug c++/109876] [10/11/12/13/14 Regression] " mpolacek at gcc dot gnu.org 2023-05-16 18:43 ` pinskia at gcc dot gnu.org 2023-05-16 18:45 ` mpolacek at gcc dot gnu.org 2023-05-16 18:46 ` pinskia at gcc dot gnu.org 2023-05-16 19:13 ` mpolacek at gcc dot gnu.org 2023-05-18 16:41 ` mpolacek at gcc dot gnu.org 2023-05-18 17:07 ` ppalka at gcc dot gnu.org 2023-05-18 17:26 ` jason at gcc dot gnu.org 2023-05-19 21:01 ` mpolacek at gcc dot gnu.org 2023-05-24 20:20 ` mpolacek at gcc dot gnu.org 2023-05-24 20:28 ` jason at gcc dot gnu.org 2023-05-26 17:02 ` mpolacek at gcc dot gnu.org 2023-05-26 18:08 ` mpolacek at gcc dot gnu.org 2023-07-07 10:45 ` [Bug c++/109876] [11/12/13/14 " rguenth at gcc dot gnu.org 2023-07-14 17:16 ` cvs-commit at gcc dot gnu.org 2023-07-14 17:18 ` [Bug c++/109876] [11/12/13 " mpolacek at gcc dot gnu.org 2023-07-19 11:26 ` rguenth at gcc dot gnu.org 2023-12-12 0:37 ` cvs-commit at gcc dot gnu.org 2023-12-12 0:39 ` [Bug c++/109876] [11/12 " 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-109876-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).