https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69550
--- Comment #9 from Marek Polacek <mpolacek at gcc dot gnu.org> --- (In reply to Milan Bouchet-Valat from comment #8) > As I said, I don't deny it's the correct application of the standard, nor > that it's a sane behavior. But the fact that this was accepted without even > a warning by default in the last GCC release, and that no way to disable the > error is offered in GCC 6 creates problems for existing code bases. Note that this was only accepted by the C++ compiler; the C compiler always rejected such a code (going back to at least gcc 3.4).
