Displaying 3 results from an estimated 3 matches for "diloation".
Did you mean:
dilocation
2018 Sep 19
2
Obtaining the origin function for a local var after inlining
...ic.
Does anyone have an idea why this isn't so?
Right now one needs to build a mapping between AllocaInst and
llvm.dbg.declare() in order to get the debug info for the allocation.
> if you want to find the function that it was inlined *into* then you need to follow the inlinedAt link in the DILoation.
>
> -- adrian
>
> > E.g. when a local buffer %buf is declared in @bar(), but @bar() is
> > inlined into @foo(), then there's a local %buf.i in @foo(), but we
> > need to determine that the local came from @bar(). In the case of
> > nested inline functions we ne...
2018 Sep 17
3
Obtaining the origin function for a local var after inlining
(I think I've asked a similar question off-list a couple of times, but
never got an answer)
Hi folks,
For [K]MSAN we need to figure out which inlined function a local var
originally belonged to in the source file.
E.g. when a local buffer %buf is declared in @bar(), but @bar() is
inlined into @foo(), then there's a local %buf.i in @foo(), but we
need to determine that the local came from
2018 Sep 25
1
Obtaining the origin function for a local var after inlining
...three intrinsics indeed point to line 888, where |siginfo| is declared.
Is the DW_OP_deref tag enough to distinguish the right llvm.dbg.value?
> -- adrian
>
> >
> >> if you want to find the function that it was inlined *into* then you need to follow the inlinedAt link in the DILoation.
> >>
> >> -- adrian
> >>
> >>> E.g. when a local buffer %buf is declared in @bar(), but @bar() is
> >>> inlined into @foo(), then there's a local %buf.i in @foo(), but we
> >>> need to determine that the local came from @bar(). In...