> On Tue, Jan 20, 2015 at 11:14 AM, Jonathan Gray wrote:
> So it seems at some point after gcc 4.4 --std=c89 and --std=c99
> starting allowing anonymous unions/structs when this behaviour
> was otherwise only accepted with --std=gnu99, --std=c99 -fms-extensions
> or omitting a --std option entire
> > Date: Wed, 21 Jan 2015 03:14:10 +1100
> > From: Jonathan Gray
> >
> > So it seems at some point after gcc 4.4 --std=c89 and --std=c99
> > starting allowing anonymous unions/structs when this behaviour
> > was otherwise only accepted with --std=gnu99, --std=c99 -fms-extensions
> > or omitting
> Date: Wed, 21 Jan 2015 03:14:10 +1100
> From: Jonathan Gray
>
> So it seems at some point after gcc 4.4 --std=c89 and --std=c99
> starting allowing anonymous unions/structs when this behaviour
> was otherwise only accepted with --std=gnu99, --std=c99 -fms-extensions
> or omitting a --std option
On Wed, 21 Jan 2015 03:14:10 +1100, Jonathan Gray wrote:
> I'd like to change the defaults for the in tree versions
> of gcc to match to avoid problems like those mentioned here:
> https://bugs.freedesktop.org/show_bug.cgi?id=88467
Makes sense to me. We are going to see this feature used more in
So it seems at some point after gcc 4.4 --std=c89 and --std=c99
starting allowing anonymous unions/structs when this behaviour
was otherwise only accepted with --std=gnu99, --std=c99 -fms-extensions
or omitting a --std option entirely.
clang also has the same behaviour as recent gcc.
struct foo {
