Displaying 3 results from an estimated 3 matches for "constructcallsiteentrydies".
2020 Feb 07
2
Enabling debug entry value production by default
The actual DWARF emission for call site parameters is gated inside of DwarfDebug::constructCallSiteEntryDIEs by `tuneForGDB() || tuneForLLDB()`.
However, we are creating+updating CallSiteInfo (basically, in-memory only bookkeeping used by the backend to keep track of call sites) even when the debugger tuning is set to the Sony debugger. If this creates problems, feel free to file a bug and I'll addre...
2020 Feb 10
2
Enabling debug entry value production by default
...at gmail.com>; nikola.prica at rt-rk.com; ibaev at cisco.com; asowda at cisco.com; llvm-dev at lists.llvm.org
> *Subject:* Re: [llvm-dev] Enabling debug entry value production by default
>
>
>
> The actual DWARF emission for call site parameters is gated inside of DwarfDebug::constructCallSiteEntryDIEs by `tuneForGDB() || tuneForLLDB()`.
>
>
>
> However, we are creating+updating CallSiteInfo (basically, in-memory only bookkeeping used by the backend to keep track of call sites) even when the debugger tuning is set to the Sony debugger. If this creates problems, feel free to file a...
2020 Feb 07
2
Enabling debug entry value production by default
Yep, TAG_call_site_parameter and its children shouldn't require any extra relocations. Thanks!
vedant
> On Feb 7, 2020, at 2:01 PM, David Blaikie <dblaikie at gmail.com> wrote:
>
> For that sort of small growth, if it doesn't add more relocations (I think the call sites need them (but they're already emitted/that's not what we're discussing enabling here), but