Re: [PATCH 2/3] Avoid creating an initializer for a flexible array member

2016-01-10 Thread Patrick Palka
On Sun, Jan 3, 2016 at 3:14 PM, Martin Sebor wrote: > On 12/31/2015 08:40 AM, Patrick Palka wrote: >> >> If we do create such an initializer, we end up with an error_mark_node >> during gimplification, because in cp-gimplify.c we pass this >> VEC_INIT_EXPR of the flexible array

Re: [PATCH 2/3] Avoid creating an initializer for a flexible array member

2016-01-03 Thread Martin Sebor
On 12/31/2015 08:40 AM, Patrick Palka wrote: If we do create such an initializer, we end up with an error_mark_node during gimplification, because in cp-gimplify.c we pass this VEC_INIT_EXPR of the flexible array member to build_vec_init, for which it spits on an error_mark_node. This happens

[PATCH 2/3] Avoid creating an initializer for a flexible array member

2015-12-31 Thread Patrick Palka
If we do create such an initializer, we end up with an error_mark_node during gimplification, because in cp-gimplify.c we pass this VEC_INIT_EXPR of the flexible array member to build_vec_init, for which it spits on an error_mark_node. This happens in e.g. the test case g++.dg/ext/array1.C. This