https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69650
--- Comment #13 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Richard Biener from comment #10) > Not sure who's familiar with the C/C++ FE interfacing to libcpp and if > those "bogus" locations should simply never be assigned to input_location... As long as we keep mucking up input_location to hack passing around the proper locations, we will keep having surprises like this caused by unrelated changes elsewhere.