This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/65797] [5 regression] IPA ICF causes function to be emitted with no debug line info
- From: "hubicka at ucw dot cz" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 17 Apr 2015 23:09:18 +0000
- Subject: [Bug tree-optimization/65797] [5 regression] IPA ICF causes function to be emitted with no debug line info
- Auto-submitted: auto-generated
- References: <bug-65797-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65797
--- Comment #5 from Jan Hubicka <hubicka at ucw dot cz> ---
Well, if you turn one function to alias of another, there is no way to preserve
it (like Gold's ICF doesn't). With dwarf extensions we can restore some of the
info based on context where the function is called, but not all of it. In this
case I guess it would be an improvement to have wrapper function in the
backtrace followed by the unexepected function we redirected to.
Honza
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65797
>
> --- Comment #4 from Ian Lance Taylor <ian at airs dot com> ---
> I think we should have a goal of making backtraces always work. I don't know
> why we would ever want backtraces to fail. Every function should have a name
> and a file name. I can accept that in some cases there may be no useful line
> information, but it seems clear to me that a function should always have a
> name.
>
> I would guess that thunks do not appear in backtraces because they end with a
> jump instruction rather than a call. Note that my test case used
> -fno-optimize-sibling-calls.
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.