Displaying 5 results from an estimated 5 matches for "call_discriminator".
2017 Feb 08
3
Stripping Debug Locations on cross BB moves, part 2 (PR31891)
...ubroutine can be described)
Any ideas on how we should approach this?
We could have a bit in DebugLoc (or other choice of representation) for the
non-line location. For the line table this would work the same as absent
DebugLoc - for calls it would cause call_file/line/discriminator (do we
have a call_discriminator? We probably should, don't know if we do) to be
omitted which is something the LLVM IR representation currently can't
express.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170208/90e9c7e9/attachmen...
2017 Feb 08
2
Stripping Debug Locations on cross BB moves, part 2 (PR31891)
...deas on how we should approach this?
> >
> > We could have a bit in DebugLoc (or other choice of representation) for
> the non-line location. For the line table this would work the same as
> absent DebugLoc - for calls it would cause call_file/line/discriminator (do
> we have a call_discriminator? We probably should, don't know if we do) to
> be omitted which is something the LLVM IR representation currently can't
> express.
>
> Even if the function calls are not inlined it could be preferable to keep
> a debug location. It's a very odd debugging experience to be...
2017 Feb 08
2
Stripping Debug Locations on cross BB moves, part 2 (PR31891)
...deas on how we should approach this?
> >
> > We could have a bit in DebugLoc (or other choice of representation) for
> the non-line location. For the line table this would work the same as
> absent DebugLoc - for calls it would cause call_file/line/discriminator (do
> we have a call_discriminator? We probably should, don't know if we do) to
> be omitted which is something the LLVM IR representation currently can't
> express.
>
> Even if the function calls are not inlined it could be preferable to keep
> a debug location. It's a very odd debugging experience to be...
2017 Feb 09
2
Stripping Debug Locations on cross BB moves, part 2 (PR31891)
...deas on how we should approach this?
> >
> > We could have a bit in DebugLoc (or other choice of representation) for
> the non-line location. For the line table this would work the same as
> absent DebugLoc - for calls it would cause call_file/line/discriminator (do
> we have a call_discriminator? We probably should, don't know if we do) to
> be omitted which is something the LLVM IR representation currently can't
> express.
>
> Even if the function calls are not inlined it could be preferable to keep
> a debug location. It's a very odd debugging experience to be...
2017 Feb 10
2
Stripping Debug Locations on cross BB moves, part 2 (PR31891)
...> > Any ideas on how we should approach this?
> >
> > We could have a bit in DebugLoc (or other choice of representation) for the non-line location. For the line table this would work the same as absent DebugLoc - for calls it would cause call_file/line/discriminator (do we have a call_discriminator? We probably should, don't know if we do) to be omitted which is something the LLVM IR representation currently can't express.
>
> Even if the function calls are not inlined it could be preferable to keep a debug location. It's a very odd debugging experience to be stopped at a b...