https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122685
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- 4824:8 does make sense though. Looks like clang is not printing out warning/notes atomically. So if you are using -j they all get messed up :).
