Displaying 7 results from an estimated 7 matches for "vregx".
Did you mean:
vreg
2016 May 11
2
[LLVMdev] Improving the quality of debug locations / DbgValueHistoryCalculator
> On May 11, 2016, at 1:12 PM, Francois Pichet <pichet2000 at gmail.com> wrote:
>
> Hello,
>
> Regarding the problem of debug range for optimized code.
> Currently a DEBUG_VALUE will be inserted after the <def>vregX
> DEBUG_VALUE are only valid until the end of the current MachineBasicBlock. That's the main problem.
> Why not simply iterate over all uses of vregX and insert an DEBUG_VALUE in all the MachineBasicBlocks where vregX is used. (pre regalloc)
>
> I prototyped a small pass to do that...
2016 May 11
2
[LLVMdev] Improving the quality of debug locations / DbgValueHistoryCalculator
...On May 11, 2016, at 1:12 PM, Francois Pichet <pichet2000 at gmail.com <mailto:pichet2000 at gmail.com>> wrote:
> >
> > Hello,
> >
> > Regarding the problem of debug range for optimized code.
> > Currently a DEBUG_VALUE will be inserted after the <def>vregX
> > DEBUG_VALUE are only valid until the end of the current MachineBasicBlock. That's the main problem.
> > Why not simply iterate over all uses of vregX and insert an DEBUG_VALUE in all the MachineBasicBlocks where vregX is used. (pre regalloc)
> >
> > I prototyped a sm...
2016 May 11
3
[LLVMdev] Improving the quality of debug locations / DbgValueHistoryCalculator
...1:12 PM, Francois Pichet <pichet2000 at gmail.com <mailto:pichet2000 at gmail.com>> wrote:
>> >
>> > Hello,
>> >
>> > Regarding the problem of debug range for optimized code.
>> > Currently a DEBUG_VALUE will be inserted after the <def>vregX
>> > DEBUG_VALUE are only valid until the end of the current MachineBasicBlock. That's the main problem.
>> > Why not simply iterate over all uses of vregX and insert an DEBUG_VALUE in all the MachineBasicBlocks where vregX is used. (pre regalloc)
>> >
>> > I...
2015 Aug 12
3
[LLVMdev] Improving the quality of debug locations / DbgValueHistoryCalculator
Hi all,
An early implementation of extending debug ranges and providing multiple
location support is done here: http://reviews.llvm.org/D11933
Design document:
https://docs.google.com/document/d/1noDVWTvTWBdYdweICPBwvwyt8QvX4KHl7j3XKNSg1nE/edit?usp=sharing
On Jun 24, 2015, at 12:12 PM, Alexey Samsonov <vonosmas at gmail.com> wrote:
Hi Adrian,
You might want to take a look at abandoned
2016 May 12
2
[LLVMdev] Improving the quality of debug locations / DbgValueHistoryCalculator
...ichet <pichet2000 at gmail.com <mailto:pichet2000 at gmail.com>> wrote:
>>> >
>>> > Hello,
>>> >
>>> > Regarding the problem of debug range for optimized code.
>>> > Currently a DEBUG_VALUE will be inserted after the <def>vregX
>>> > DEBUG_VALUE are only valid until the end of the current MachineBasicBlock. That's the main problem.
>>> > Why not simply iterate over all uses of vregX and insert an DEBUG_VALUE in all the MachineBasicBlocks where vregX is used. (pre regalloc)
>>> >
>...
2018 Mar 02
0
[RFC] llvm-mca: a static performance analysis tool
+Matthias
> On Mar 2, 2018, at 6:42 AM, Andrea Di Biagio <andrea.dibiagio at gmail.com> wrote:
>
>> Known limitations on X86 processors
>> -----------------------------------
>>
>> 1) Partial register updates versus full register updates.
>> <snip>
>
> MachineOperand handles this. You just need to create the machine instrs.
>
>
2018 Mar 02
5
[RFC] llvm-mca: a static performance analysis tool
Hi Andrew,
Thanks for the feedback!
On Fri, Mar 2, 2018 at 1:16 AM, Andrew Trick <atrick at apple.com> wrote:
>
> On Mar 1, 2018, at 9:22 AM, Andrea Di Biagio <andrea.dibiagio at gmail.com>
> wrote:
>
> Hi all,
>
> At Sony we developed an LLVM based performance analysis tool named
> llvm-mca. We
> currently use it internally to statically measure the