public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95241] [10/11 Regression] internal compiler error: tree check: expected integer_cst, have range_expr in to_wide, at tree.h:5900 Date: Fri, 29 May 2020 13:44:54 +0000 [thread overview] Message-ID: <bug-95241-4-FCLdVyrD9E@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95241-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95241 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:e069285cdf457cc85070e522380c4e25b0d2ed25 commit r11-722-ge069285cdf457cc85070e522380c4e25b0d2ed25 Author: Patrick Palka <ppalka@redhat.com> Date: Fri May 29 09:44:09 2020 -0400 c++: constexpr ctor with RANGE_EXPR index [PR95241] In the testcase below, the CONSTRUCTOR for 'field' contains a RANGE_EXPR index: {{aggr_init_expr<...>, [1...2]={.off=1}}} but get_or_insert_ctor_field isn't prepared to handle looking up a RANGE_EXPR index. This patch adds limited support to get_or_insert_ctor_field for looking up a RANGE_EXPR index. The limited scope of this patch should make it more suitable for backporting, and more extensive support would be needed only to handle self-modifying CONSTRUCTORs that contain a RANGE_EXPR index, but I haven't yet been able to come up with a testcase that actually creates such a CONSTRUCTOR. gcc/cp/ChangeLog: PR c++/95241 * constexpr.c (get_or_insert_ctor_field): Add limited support for RANGE_EXPR index lookups. gcc/testsuite/ChangeLog: PR c++/95241 * g++.dg/cpp0x/constexpr-array25.C: New test.
next prev parent reply other threads:[~2020-05-29 13:44 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-20 17:13 [Bug c++/95241] New: " tab.debugteam at gmail dot com 2020-05-20 17:25 ` [Bug c++/95241] [10/11 Regression] " mpolacek at gcc dot gnu.org 2020-05-20 18:14 ` ppalka at gcc dot gnu.org 2020-05-22 6:08 ` rguenth at gcc dot gnu.org 2020-05-29 13:44 ` cvs-commit at gcc dot gnu.org [this message] 2020-05-29 13:45 ` [Bug c++/95241] [10 " ppalka at gcc dot gnu.org 2020-05-30 4:20 ` cvs-commit at gcc dot gnu.org 2020-05-30 4:22 ` ppalka at gcc dot gnu.org 2020-05-30 7:30 ` tab.debugteam at gmail dot com
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-95241-4-FCLdVyrD9E@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).