https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105877
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to hubicka from comment #2)
> > "strip -g" removed .gnu.debuglto_.debug_info sections. Should LTO remove the
> > references of stripped debug info? Or should "strip -g" keep LTO debug
> > info?
>
> I suppose we should try to immitate what happens without -flto, so
> probably check for the presence of debuglto sections and avoid producing
> debug info when they have been stripped?
> I am not sure how hard would be to implement this especially in
> situations where part of object files were stripped and others not?
I think it might be possible to detect whether the compiled objects are
stripped and then avoid streaming references to its debug sections by
magically turning it to -g0. But not sure how awkward this will be.
Not sure why strip now strips .gnu.debuglto_.debug_info, it didn't do that
before.
