https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69650
--- Comment #20 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to David Malcolm from comment #18) > FWIW Bernd posted a different patch for this, here: > https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00598.html FWIW, if that works for all testcases here, it seems a better solution. Even if it misses some corner-case, it seems a better design to catch this invalid input at the caller and give an error than try to guess in line-map.c what the caller was trying to do and recover somehow.
