Re: [patch] better dwarf2 debug info for inlined functions

[Daniel Berlin <dberlin at dberlin dot org>]

> > With this extra info, we can now generate the same backtraces with
> > function inlining as we can generate without function inlining.
> 
> How does this affect the size of the debugging information on say, the
> tramp3d-v3 testcase?  I would appreciate a way to turn this extra information
> off, if possible.
> 
You compile with debug info and optimization, and are going to say the
debug info is too big?
That seems weird.


This is very standard information we are producing, and stuff we are
supposed to be producing.

it shouldn't add more than a couple bytes per inlined call site.

> Thanks,
> Richard.