Thanks; I've already fixed it.
Jason
> Tested x86_64-pc-linux-gnu, applying to trunk for now.
This was put yesterday on the 4.7 branch and broke the build:
../../src/gcc/cp/call.c: In function 'type_has_extended_temps':
../../src/gcc/cp/call.c:8866: error: 'for' loop initial declaration used
outside C99 mode
make[3]: *** [cp/call.o
> Tested x86_64-pc-linux-gnu, applying to trunk for now.
This was put yesterday on the 4.7 branch and broke the build:
../../src/gcc/cp/call.c: In function 'type_has_extended_temps':
../../src/gcc/cp/call.c:8866: error: 'for' loop initial declaration used
outside C99 mode
make[3]: *** [cp/call.o
On 01/03/2013 11:54 AM, Jakub Jelinek wrote:
I'd say safer would be to scan the gimple dump instead...
That makes sense.
commit 8a13c5cee23447467ed58bb1f213cad9050e3f87
Author: jason
Date: Thu Jan 3 18:34:48 2013 +
PR c++/53650
* g++.dg/init/array34.C: Check gimple dump, no
On Thu, Jan 03, 2013 at 11:48:48AM -0500, Jason Merrill wrote:
> --- /dev/null
> +++ b/gcc/testsuite/g++.dg/init/array34.C
> @@ -0,0 +1,13 @@
> +// PR c++/53650
> +// We should loop over array inits if they don't involve temporaries
> +// that need extending.
> +// { dg-final { scan-assembler-times
