Displaying 3 results from an estimated 3 matches for "tok1".
Did you mean:
tok
2016 Jan 06
2
Proposal for multi location debug info support in LLVM IR
...; ; alt becomes unavailable
> ...
> ; %loc is still available here.
>
> Any other advantages that I missed?
>
> -- adrian
>
>
> One thing I’m wondering about is whether we couldn’t design a friendlier (assembler) syntax for the three different use-cases:
> %tok1 = call llvm.dbg.value(token %undef, %1, !var, !())
> %tok2 = call llvm.dbg.value(token %token, %2, !var, !())
> %tok3 = call llvm.dbg.value(token %tok1, %undef, !var, !())
>
> Could be written as e.g.:
>
> %tok1 = call llvm.dbg.value.new(%1, !var, !())
> %tok2 = call...
2016 Jan 05
2
Proposal for multi location debug info support in LLVM IR
On Tue, Jan 5, 2016 at 6:59 PM, Adrian Prantl <aprantl at apple.com> wrote:
> Thanks for the clarification, Paul!
> Keno, just a few more questions for my understanding:
>
> > - Indicating that a value changed at source level (e.g. because an
> > assignment occurred)
>
> This is done by a key call.
Correct
> > - Indicating that the same
2016 Jan 15
2
Proposal for multi location debug info support in LLVM IR
...e.
>> >
>> > Any other advantages that I missed?
>> >
>> > -- adrian
>> >
>> >
>> > One thing I’m wondering about is whether we couldn’t design a
>> friendlier (assembler) syntax for the three different use-cases:
>> > %tok1 = call llvm.dbg.value(token %undef, %1, !var, !())
>> > %tok2 = call llvm.dbg.value(token %token, %2, !var, !())
>> > %tok3 = call llvm.dbg.value(token %tok1, %undef, !var, !())
>> >
>> > Could be written as e.g.:
>> >
>> > %tok1 = call ll...