http://isocpp.org/blog/2013/04/trip-report-iso-c-spring-2013...
That being said, you are correct that it would be good to see warnings in something other than just -pedantic for that.
(Of course, part of that is presumably that gcc's nonconformance is generally useful, as in this case...)
This is pretty standard type of issues for any ANSI/ISO language regardless of the vendor.
Oh boy the joys of doing C and C++ development across multiple OS in the late 90's with commercial compilers.
In my experience, gcc is also significantly better with standards conformance than VC++, either with default settings or with strict warning/conformance options turned on. [I was on a team doing shared g++/vc++ develeopment, and it fell to me to fix all the code checked in by devs using non-standard VC++ extensions... way, way, way too much time... >< ]
Here is a much, much more serious issue. Variable length arrays of C++ types. Totally not in the C++ standard anywhere. Accepted by g++ and clang++, even if I turn on all warnings, and use '-std=c++11', which is supposed to turn off extensions. I have to add -pedantic to finally get a warning.
Now, I'm not saying they should break this code, but this is a much, much, much more serious unlabelled breakage of the standard, which is never going to get fixed, and goes back to the start of g++ and clang++.