https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19315
--- Comment #7 from Iain Sandoe <iains at gcc dot gnu.org> --- IMHO (as you say in c#3) this is "surprising behaviour" * if there's any case you'd want it - then maybe you should have to ask for it. (so if it's intentional it should be behind some flag?) * it ought to warn by default (not require '-pedantic'). * as Richi commented in 86670, it means grokdeclarator has conflicting storage classes which doesn't seem like a useful idea for maintenance. I guess the point is "what do we want the behaviour to be?". Documenting it doesn't seem to really make it less surprising (if it's an 'extension' then one ought to be able to identify a sensible use-case and put it in the test-suite).
