public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94523] New: [10 Regression] error: 'constexpr' evaluation depth exceeds maximum of 512 (use '-fconstexpr-depth=' to increase the maximum) since r10-7490-g76f09260b7eccd6c Date: Tue, 07 Apr 2020 19:16:24 +0000 [thread overview] Message-ID: <bug-94523-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94523 Bug ID: 94523 Summary: [10 Regression] error: 'constexpr' evaluation depth exceeds maximum of 512 (use '-fconstexpr-depth=' to increase the maximum) since r10-7490-g76f09260b7eccd6c Product: gcc Version: 10.0 Status: UNCONFIRMED Keywords: rejects-valid Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: marxin at gcc dot gnu.org CC: jason at gcc dot gnu.org Target Milestone: --- It's a test-case reduced from pybind11 package: $ cat pybind11.ii template <bool, typename a> using b = a; struct d { char ao; template <typename ap> constexpr d(ap) : ao{} {} }; template <int... au> struct e { static constexpr auto aw = d(au...); }; template <int c> b<c, d> ax(e<1>::aw); $ g++-9 pybind11.ii -c $ g++ pybind11.ii -c ... pybind11.ii:6:55: in 'constexpr' expansion of 'd(1)' pybind11.ii:6:55: in 'constexpr' expansion of 'd(1)' pybind11.ii:6:55: in 'constexpr' expansion of 'd(1)' pybind11.ii:6:55: in 'constexpr' expansion of 'd(1)' pybind11.ii:6:55: in 'constexpr' expansion of 'd(1)' pybind11.ii:6:55: error: 'constexpr' evaluation depth exceeds maximum of 512 (use '-fconstexpr-depth=' to increase the maximum) 6 | template <int... au> struct e { static constexpr auto aw = d(au...); }; | ^~
next reply other threads:[~2020-04-07 19:16 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-07 19:16 marxin at gcc dot gnu.org [this message] 2020-04-07 19:16 ` [Bug c++/94523] " marxin at gcc dot gnu.org 2020-04-08 8:19 ` arnaud.giersch at free dot fr 2020-04-08 8:30 ` marxin at gcc dot gnu.org 2020-04-08 19:51 ` jason at gcc dot gnu.org 2020-04-09 11:32 ` reichelt at gcc dot gnu.org 2020-04-09 11:36 ` reichelt at gcc dot gnu.org 2020-04-09 11:58 ` reichelt at gcc dot gnu.org 2020-04-09 21:34 ` cvs-commit at gcc dot gnu.org 2020-04-10 21:31 ` jason 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-94523-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).