https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65797
--- Comment #3 from Jan Hubicka <hubicka at ucw dot cz> --- Hi, the ICF wrapper are created same way as thunks (by expand_thunk) which probably suppress debug info because we do not want to see it for thunks. I suppose it is: DECL_IGNORED_P (thunk_fndecl) = 1 I suppose we can add a parameter that will enable debug info production and pass it as true via the create_wrapper path (can't hack it right now as I am on a trip in China) I am adding Martin to CC. In many cases we however create a wrapper where keeping function is backtrace is even harder. If go needs functions in backtrace even in this case (when they are not exported nor have address taken) perhaps we have to disable ICF? We may add a way to disable ICF per function basis. Honza
