Displaying 4 results from an estimated 4 matches for "getmergeddebugloc".
2017 Feb 08
2
Stripping Debug Locations on cross BB moves, part 2 (PR31891)
...as taken when it was
> really the else branch, being the canonical example)
>
> Calls don't seem fundamentally special here - except due to limitations of
> the IR representation.
>
>
> The CSE example is a good one, though I *think* in this case we will end
> up calling getMergedDebugLocation() which will return a line 0 location.
>
I think getMergedDebugLocation (or whatever it's called) currently returns
a null location, which is a bit different from line 0.
Line zero is tricky to use as it can make the line table larger (file
size)/worse for the user (similarly jumpy be...
2017 Feb 09
2
Stripping Debug Locations on cross BB moves, part 2 (PR31891)
...as taken when it was
> really the else branch, being the canonical example)
>
> Calls don't seem fundamentally special here - except due to limitations of
> the IR representation.
>
>
> The CSE example is a good one, though I *think* in this case we will end
> up calling getMergedDebugLocation() which will return a line 0 location.
>
>
> I think getMergedDebugLocation (or whatever it's called) currently returns
> a null location, which is a bit different from line 0.
>
>
> Indeed it does, I misremembered. Looks like we have the same latent
> problem with...
2017 Feb 10
2
Stripping Debug Locations on cross BB moves, part 2 (PR31891)
...t the if branch was taken when it was really the else branch, being the canonical example)
>
> Calls don't seem fundamentally special here - except due to limitations of the IR representation.
>
> The CSE example is a good one, though I *think* in this case we will end up calling getMergedDebugLocation() which will return a line 0 location.
>
> I think getMergedDebugLocation (or whatever it's called) currently returns a null location, which is a bit different from line 0.
>
> Indeed it does, I misremembered. Looks like we have the same latent problem with all users of get...
2017 Feb 08
2
Stripping Debug Locations on cross BB moves, part 2 (PR31891)
On Wed, Feb 8, 2017 at 9:36 AM Adrian Prantl <aprantl at apple.com> wrote:
>
> > On Feb 8, 2017, at 9:25 AM, David Blaikie <dblaikie at gmail.com> wrote:
> >
> > So Reid came across a case where the current strategy (dropping
> locations when they move across basic blocks) proves to be at odds with
> another precept we have: inlinable calls must have