https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86417
--- Comment #5 from janus at gcc dot gnu.org --- (In reply to Thomas Koenig from comment #4) > The idea of the warning is to ensure that we have > Location information everywhere, and that patches > Which do not correctly set the location should cause > something visible during testing. We do not have this for > release. Thanks for the explanation. Makes sense. Do you have any idea what might have caused the regression? > We should take care to always regression test libgomp.fortran > as well... Yes, I finally got into this habit, after repeatedly breaking libgomp tests with my patches without noticing it. I also tried to document how to do this at the bottom of this wiki page: https://gcc.gnu.org/wiki/TestCaseWriting It took me a while to figure out how to actually run the Fortran subset of the libgomp suite (which is not very well documented, or I'm too stupid to find it).