search for: syrmia

...f potential complexity, since we need to carry that info throughout IR and use it as a backup. Best regards, Djordje ________________________________ 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 a...

...> start with something simple? -check-debugify already knows how to > report when & where a location is dropped, it would be simple to teach > it to emit a report when a variable is fully optimized-out. > > >> On Jun 17, 2020, at 2:10 AM, Djordje <djordje.todorovic at syrmia.com >> <mailto:djordje.todorovic at syrmia.com>> wrote: >> >> I am sharing the proposal [0] which gives a brief introduction for >> the implementation of the LLVM DI Checker utility. On a very high >> level, it is a pair of LLVM (IR) Passes that check the p...

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

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 tha...

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

Hi, I am sharing the proposal [0] which gives a brief introduction for the implementation of the LLVM DI Checker utility. On a very high level, it is a pair of LLVM (IR) Passes that check the preservation of the original debug info in the optimizations. There are options controlling the passes, that could be invoked from ``clang`` as well as from ``opt`` level. By testing the utility on the

Currently there is a series of patches undergoing review[0] that seek to enable the use of multiple IR/MIR values when describing a source variable's location. The current plan for the MIR is to add a new instruction, DBG_VALUE_LIST, that supports this functionality by having a variable number of operands. It may be better however to simply replace the existing DBG_VALUE behaviour entirely