Clang incorrectly takes an unnamed bitfield as a member

[RealLitb]

Bugzilla Link	10289
Resolution	FIXED
Resolved on	Oct 10, 2011 12:22
Version	trunk
OS	Linux
CC	@DougGregor

Extended Description

The following is valid C++03 code, as far as I can see

struct A {
private:
int : 0;
};

A a = { };

"A" is an aggregate, but clang complains

main1.cpp:6:3: error: non-aggregate type 'A' cannot be initialized with an initializer list
A a = { };

[RealLitb]

A different instance of this:

struct A {
const int : 0;
};

A a;

C++03 calls it an error if "a" has a "const .. subobject". The only subobject variety that could potentially fit here is a "member subobject". But since unnamed bitfields are not members, I don't think that the unnamed bitfield is a subobject (it's only used as a layout directive anyway).

Comeau online rejects this case but accepts my earlier test-case (the aggregate one).

In C++0x, the FDIS does not use the term "subobject" here, but just invokes the default constructor, which will never touch unnamed members. So in C++0x it seems well-formed too.

[DougGregor]

Fixed in Clang r141549.