public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/103443] consteval function rejected as constant expression Date: Fri, 26 Nov 2021 16:32:59 +0000 [thread overview] Message-ID: <bug-103443-4-WqxaHuD8Gr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103443-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103443 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2021-11-26 CC| |jakub at gcc dot gnu.org, | |jason at gcc dot gnu.org, | |ppalka at gcc dot gnu.org --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Seems while parsing the default argument of the template parameter finish_call_expr notes the argument of the index_sequence2mask call is non-dependent, so make_args_non_dependent wraps that argument with NON_DEPENDENT_EXPR. But later we call build_new_function_call -> build_over_call -> fold_non_dependent_expr -> fold_non_dependent_expr_template -> instantiate_non_dependent_expr_internal -> tsubst_copy_and_build which instantiates it, but the NON_DEPENDENT_EXPR is still among the arguments. Later build_over_call sees it is a call to an immediate function and so calls cxx_constant_value on it, but the constant evaluation fails because NON_DEPENDENT_EXPR isn't handled in constexpr.c at all. Shall constexpr.c handle NON_DEPENDENT_EXPR, or can that wrap expressions that really can't be constant expression evaluated?
next prev parent reply other threads:[~2021-11-26 16:32 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-26 14:56 [Bug c++/103443] New: " vincent.hamp at higaski dot at 2021-11-26 16:32 ` jakub at gcc dot gnu.org [this message] 2022-03-04 15:17 ` [Bug c++/103443] " cvs-commit at gcc dot gnu.org 2022-03-04 15:29 ` ppalka at gcc dot gnu.org 2022-03-04 15:29 ` ppalka 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-103443-4-WqxaHuD8Gr@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).