https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65834
--- Comment #2 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Andrew Pinski from comment #1) > Maybe someone might want to put something else after TEST. I think both are > correct to warn. clang error location might be more useful in some cases > but wrong in others. Likewise the way GCC is correct for some cases but > wrong for others. The biggest question is which happens more often in real > life. I don't have any thoughts on that one. Note that Clang gives the same location as GCC. My suggestion is to improve over clang to show the macro value as empty. If one adds something after TEST, then the error (and locations) would be totally different, which is ok.
