https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107950

--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
I suppose a fix would be to provide a dummy implementation for
range_label_for_type_mismatch::get_text in lto/, but I wonder how
for example the fortran frontend avoids this issue?

f951 has rich_location uses but no range_label_for_type_mismatch, it looks
like range_label_for_* is used only from the C family frontends, so maybe
another fix would be to move that class and implementation somewhere to
c-family/?

Reply via email to