diff options
author | Jason Merrill <jason@redhat.com> | 2020-11-20 16:50:20 -0500 |
---|---|---|
committer | Jason Merrill <jason@redhat.com> | 2020-11-24 14:57:56 -0500 |
commit | 92a30040c8d3ea4899979ec41a7e8e6a625c438d (patch) | |
tree | c4f91105a4b1b013955ef68e18f7a57c72dce78e /contrib/gcc-changelog/git_commit.py | |
parent | ce2d9549f2b2bcb70a1a6f8f4e776e1ed427546b (diff) | |
download | gcc-92a30040c8d3ea4899979ec41a7e8e6a625c438d.zip gcc-92a30040c8d3ea4899979ec41a7e8e6a625c438d.tar.gz gcc-92a30040c8d3ea4899979ec41a7e8e6a625c438d.tar.bz2 |
c++: ICE with int{} in template. [PR97899]
split_nonconstant_init_1 was confused by a CONSTRUCTOR with non-aggregate
type, which (with COMPOUND_LITERAL_P set) we use in a template to represent
a braced functional cast. It seems to me that there's no good reason to do
split_nonconstant_init at all in a template.
gcc/cp/ChangeLog:
PR c++/97899
* typeck2.c (store_init_value): Don't split_nonconstant_init in a
template.
gcc/testsuite/ChangeLog:
PR c++/97899
* g++.dg/cpp0x/initlist-template3.C: New test.
Diffstat (limited to 'contrib/gcc-changelog/git_commit.py')
0 files changed, 0 insertions, 0 deletions