diff options
author | Jason Merrill <jason@redhat.com> | 2022-12-06 18:10:48 -0500 |
---|---|---|
committer | Jason Merrill <jason@redhat.com> | 2022-12-08 13:43:25 -0500 |
commit | bd0485f20f4794f9787237706a6308473a8e9415 (patch) | |
tree | fce5865dde25c38a2f1d403cf3ba3154b3d0e5f1 /libgcc | |
parent | d081807d8d70e3e87eae41e1560e54d503f4d465 (diff) | |
download | gcc-bd0485f20f4794f9787237706a6308473a8e9415.zip gcc-bd0485f20f4794f9787237706a6308473a8e9415.tar.gz gcc-bd0485f20f4794f9787237706a6308473a8e9415.tar.bz2 |
c++: build initializer_list<string> in a loop [PR105838]
The previous patch avoided building an initializer_list<string> at all when
building a vector<string>, but in situations where that isn't possible, we
could still build the initializer_list with a loop over a constant array.
This is represented using a VEC_INIT_EXPR, which required adjusting a couple
of places that expected the initializer array to have the same type as the
target array and fixing build_vec_init not to undo our efforts.
PR c++/105838
gcc/cp/ChangeLog:
* call.cc (convert_like_internal) [ck_list]: Use
maybe_init_list_as_array.
* constexpr.cc (cxx_eval_vec_init_1): Init might have
a different type.
* tree.cc (build_vec_init_elt): Likewise.
* init.cc (build_vec_init): Handle from_array from a
TARGET_EXPR. Retain TARGET_EXPR of a different type.
gcc/testsuite/ChangeLog:
* g++.dg/tree-ssa/initlist-opt2.C: New test.
Diffstat (limited to 'libgcc')
0 files changed, 0 insertions, 0 deletions