search for: asowda

Displaying 10 results from an estimated 10 matches for "asowda".

2020 Feb 10
2
Enabling debug entry value production by default
...> > *From:* vsk at apple.com <vsk at apple.com> *On Behalf Of * Vedant Kumar > *Sent:* Friday, February 7, 2020 3:26 PM > *To:* Robinson, Paul <paul.robinson at sony.com> > *Cc:* David Blaikie <dblaikie 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()`. > &gt...
2020 Feb 07
2
Enabling debug entry value production by default
...2:04 PM > To: David Blaikie <dblaikie at gmail.com <mailto:dblaikie at gmail.com>> > Cc: llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>; nikola.prica at rt-rk.com <mailto:nikola.prica at rt-rk.com>; ibaev at cisco.com <mailto:ibaev at cisco.com>; asowda at cisco.com <mailto:asowda at cisco.com> > Subject: Re: [llvm-dev] 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...
2020 Sep 01
2
[RFC] [DebugInfo] Using DW_OP_entry_value within LLVM IR
..._______ From: David Stenberg <david.stenberg at ericsson.com> Sent: Tuesday, September 1, 2020 11:38 AM To: Djordje Todorovic <Djordje.Todorovic at syrmia.com>; llvm-dev at lists.llvm.org <llvm-dev at lists.llvm.org> Cc: paul.robinson at sony.com <paul.robinson at sony.com>; asowda at cisco.com <asowda at cisco.com>; jeremy.morse at sony.com <jeremy.morse at sony.com>; ibaev at cisco.com <ibaev at cisco.com>; vsk at apple.com <vsk at apple.com>; aprantl at apple.com <aprantl at apple.com>; Petar Jovanovic <petar.jovanovic at syrmia.com>; Ni...
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
2019 Feb 08
3
RFC: [DebugInfo] Improving Debug Information in LLVM to Recover Optimized-out Function Parameters
Thank you for your interest and comments! Please see my responses inline. On 2/7/19, 3:17 PM, "aprantl at apple.com on behalf of Adrian Prantl" <aprantl at apple.com> wrote: > On Feb 7, 2019, at 1:49 PM, Ananthakrishna Sowda (asowda) via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi, > Following is a proposal to improve location coverage for Function parameters in LLVM. The patches for review will be posted soon. > > RFC: [DebugInfo] Improving Debug Information in LLVM to Recov...
2020 Sep 01
4
[RFC] [DebugInfo] Using DW_OP_entry_value within LLVM IR
Hi all, The debug entry values feature introduces new DWARF symbols (tags, attributes, operations) on caller (call site) as well as on callee side; and the intention is to improve debugging user experience by using the functionality (especially in “optimized” code by turning “<optimized_out>” values into real values). The call site information includes info about call itself (described with
2019 Feb 07
2
RFC: [DebugInfo] Improving Debug Information in LLVM to Recover Optimized-out Function Parameters
Hi, Following is a proposal to improve location coverage for Function parameters in LLVM. The patches for review will be posted soon. RFC: [DebugInfo] Improving Debug Information in LLVM to Recover Optimized-out Function Parameters Ananthakrishna Sowda(Cisco), asowda at cisco.com Nikola Prica (RT-RK/Cisco), nprica at rtrk.com Djordje Todorovic(RT-RK/Cisco), djtodorovic at rtrk.com Ivan Baev (Cisco), ibaev at cisco.com Overview of the problem Software release products are compiled with optimization level –O2 and higher. Such products might produce a core-file...
2019 Feb 08
2
RFC: [DebugInfo] Improving Debug Information in LLVM to Recover Optimized-out Function Parameters
...debugging experience). A couple of questions below. --paulr Thanks for the comments and feedback. I have added my replies inline. -Ananth > -----Original Message----- > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of > Ananthakrishna Sowda (asowda) via llvm-dev > Sent: Thursday, February 07, 2019 9:32 PM > To: Adrian Prantl > Cc: llvm-dev at lists.llvm.org > Subject: Re: [llvm-dev] RFC: [DebugInfo] Improving Debug Information in > LLVM to Recover Optimized-out Function Parameters > > Thank yo...
2020 Sep 08
2
[RFC] [DebugInfo] Using DW_OP_entry_value within LLVM IR
Hi Djordje, [Late reply as I was away, alas], For the example in https://reviews.llvm.org/D85012 , I'm not sure that just using an entry value is correct. The reason why the dbg.values for arguments are set to undef is not because the value can't be described, it's because deadargelim changes all the call sites to pass in 'undef', which I believe makes the value unrecoverable
2020 Sep 09
2
[RFC] [DebugInfo] Using DW_OP_entry_value within LLVM IR
Hi Djordje, On Wed, Sep 9, 2020 at 7:52 AM Djordje Todorovic <Djordje.Todorovic at syrmia.com> wrote: > Using entry-values ('callee' side of the feature) is not enough in any case. It is always connected to the call-site-param (function arguments but we call it call-site-params; 'caller' side of the feature) debug info. I believe that there are call-site-params that could