https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69550
--- Comment #8 from Milan Bouchet-Valat <nalimilan at club dot fr> --- (In reply to Marek Polacek from comment #6) > (In reply to Milan Bouchet-Valat from comment #5) > > Note this actually also happens with the C compiler (the attached example > > also illustrates this). > > That's the correct behavior. 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.
