https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119430
--- Comment #13 from Alexandre Oliva <aoliva at gcc dot gnu.org> --- I'm not sure how to tell, but the fact that it has an lto-related symbolic name suggested to me it was generated by the compiler rather than by the linker: __sinput__get_source_file_index__assertions.0.lto_priv.0_veneer Grepping for veneer in the sources, I don't see that the compiler would generate such symbols, but the linker would pick such names for some stubs. So I stand corrected, thanks for the lead. I wonder if this is the sort of thing that -mlong-calls is meant to work around...
