https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119481
--- Comment #6 from Alejandro Colomar <alx at kernel dot org> --- (In reply to Eric Botcazou from comment #5) > What's the point in saying that extensions violate a standard, since they > are designed for this? There are extensions that define something not defined by the standard, and others that violate it in ways explicitly prohibited by the standard. This is one of the latter. But maybe I should say (part of) this extension is quite dangerous, regardless of it violating the standard. > GCC is a production compiler, not a linter. So let's not have diagnostics at all? Why lint? > Moreover, the warning would suddenly flag code using the extensions that has > worked perfectly well for the past 15 years, thus gratuitously breaking > compatibility. And it would allow using the extension in new code, in ways that are not dangerous.
