diff options
author | Patrick Palka <ppalka@redhat.com> | 2020-05-29 09:44:09 -0400 |
---|---|---|
committer | Patrick Palka <ppalka@redhat.com> | 2020-05-29 09:44:09 -0400 |
commit | e069285cdf457cc85070e522380c4e25b0d2ed25 (patch) | |
tree | 8995b8d5e7269134952bc3393cbdc82250e983d1 /contrib/gcc-changelog/git_commit.py | |
parent | c92716b2b1d117a803775a2e2336b751050ff7c2 (diff) | |
download | gcc-e069285cdf457cc85070e522380c4e25b0d2ed25.zip gcc-e069285cdf457cc85070e522380c4e25b0d2ed25.tar.gz gcc-e069285cdf457cc85070e522380c4e25b0d2ed25.tar.bz2 |
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.
Diffstat (limited to 'contrib/gcc-changelog/git_commit.py')
0 files changed, 0 insertions, 0 deletions