https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121944
--- Comment #2 from Alejandro Colomar <foss+...@alejandro-colomar.es> --- (In reply to Harald van Dijk from comment #1) > I think 6.11.5p2 specifically calls out that a warning may be expected in > the future and implies no warning is expected yet. Of course, GCC is free to > ignore this, what does and doesn't get warned about isn't a question of > conformance but of QoI. > > 6.11.5 Storage-class specifiers > > 1 The placement of a storage-class specifier other than at the beginning of > the declaration specifiers in a declaration is an obsolescent feature. I read it more as a warning that this might be removed entirely in the future, and that implementations are welcome to start warning about it, to open the path for removal. (As a side note, Joseph noted that glibc uses 'static' in places other than the first, after macro expansion, for some tricks they do, so removal isn't in the table for now. But the diagnostic is still welcome, IMO.) > > 2 Future standardization may change the auto storage-class specifier to a > type specifier.
