({}) should be rejected at file scope.

[llvmbot]

Bugzilla Link	3062
Resolution	FIXED
Resolved on	Mar 12, 2010 00:56
Version	unspecified
OS	All
Reporter	LLVM Bugzilla Contributor
CC	@efriedma-quic

Extended Description

We should never ever ever accept

int x[({10;})];

but we do. gcc rejects ({}) outside functions.

[lattner]

Yeah, this should be rejected, we should consider this to be a "constant with side effects"

[llvmbot]

I'd advocate going further and do the gcc thing of not even handling outside of functions just to make sure such usages are strictly disallowed.

[efriedma-quic]

Yeah, this should be rejected, we should consider this to be a "constant with
side effects"

Huh? What's the side effect? There isn't any good reason to reject on those grounds. And in fact, gcc accepts "int* a() {static int a[({10;})]; return a;}".

Anyway "int x[({10;})];" isn't a good testcase because of bug 2361; try something like struct x{int x[({10;})];} instead.

[llvmbot]

The point I wanted to make is that gcc rejects always at file scope, which I would like to follow.

[efriedma-quic]

Fixed in r62943.

[lattner]

nice, this also rejects:

void foo(int x[({10;})]);