https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99131
--- Comment #2 from David Binderman <dcb314 at hotmail dot com> --- I usually write code that compiles warning free on both gcc and clang. I only noticed this difference between gcc and clang as a result of compiling the latest release of the tor browser. I thought it would be good to generalise it. I guess there must be some way to get both gcc and clang to emit all possible warning messages they can, then diff the two lists, to find out where one compiler could be enhanced. The strings command might be the way forward on this. I'd be happy to help with testing any prototype implementation. Interesting, my usual static analyser, cppcheck, has nothing to say also, so that's probably worth a bug report too.
