Displaying 6 results from an estimated 6 matches for "d45078".
2018 Mar 30
0
[RFC] Generate Debug Information for Labels in Function
...18, at 11:29 PM, Hsiangkai Wang <hsiangkai at gmail.com> wrote:
>
> I agree with you. Attach debug metadata to basic block will be a
> better solution. I will change my design to convey debug metadata
> through basic block instead of intrinsic.
>
> https://reviews.llvm.org/D45078
In this revised design it is now possible to attach a DILabel to a BasicBlock. When the basic block is inlined it will be ambiguous to which function the DILabel belongs. For instructions, we store the inline information in the inlinedAt: field of its DILocation. In order to handle inlining for DI...
2018 Mar 30
2
[RFC] Generate Debug Information for Labels in Function
...dbg attachment. In IR assembler this could look like this:
>
> top, !label !10, !dbg !11:
>
I agree with you. Attach debug metadata to basic block will be a
better solution. I will change my design to convey debug metadata
through basic block instead of intrinsic.
https://reviews.llvm.org/D45078
> That said, perhaps this isn't even necessary. The only information that is stored in DILabel is the name of the label (which is redundant with the actual name of the label) and its source location, which is also stored in the DILocation (!11). I'm wondering if the DILocation of a labe...
2018 Mar 30
4
[RFC] Generate Debug Information for Labels in Function
...ai Wang <hsiangkai at gmail.com> wrote:
>>
>> I agree with you. Attach debug metadata to basic block will be a
>> better solution. I will change my design to convey debug metadata
>> through basic block instead of intrinsic.
>>
>> https://reviews.llvm.org/D45078
>
> In this revised design it is now possible to attach a DILabel to a BasicBlock. When the basic block is inlined it will be ambiguous to which function the DILabel belongs. For instructions, we store the inline information in the inlinedAt: field of its DILocation. In order to handle inlin...
2019 Jan 30
2
[RFC] Generate Debug Information for Labels in Function
...t;>
> > >> I agree with you. Attach debug metadata to basic block will be a
> > >> better solution. I will change my design to convey debug metadata
> > >> through basic block instead of intrinsic.
> > >>
> > >> https://reviews.llvm.org/D45078
> > >
> > > In this revised design it is now possible to attach a DILabel to a
> > BasicBlock. When the basic block is inlined it will be ambiguous to
> > which function the DILabel belongs. For instructions, we store the
> > inline information in the inlinedAt:...
2018 Mar 29
0
[RFC] Generate Debug Information for Labels in Function
>
> On Mar 27, 2018, at 7:41 PM, Hsiangkai Wang via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> Hello all,
>
> I would like to enhance LLVM debug info that supports setting
> breakpoint on labels in function.
>
> Generally, if users use GDB as their debugger, they could set
> breakpoints on labels in function. Following is an example.
>
> // C
2018 Mar 28
7
[RFC] Generate Debug Information for Labels in Function
Hello all,
I would like to enhance LLVM debug info that supports setting
breakpoint on labels in function.
Generally, if users use GDB as their debugger, they could set
breakpoints on labels in function. Following is an example.
// C program
static int
myfunction (int arg)
{
int i, j, r;
j = 0; /* myfunction location */
r = arg;
top:
++j; /* top location */
if (j == 10)
goto