Displaying 6 results from an estimated 6 matches for "computeregisterl".
2015 Dec 04
2
analyzePhysReg question
Ø It would be good to check that this maps correctly onto computeRegisterLiveness: there's a bug in analyzePhysReg and I think other parts of the code base are slightly wrong or will become slightly wrong as well :-(
Yes, I agree. I will also have to look into all other users of analyzePhysReg as well. There are surprisingly few users of either computeRegisterLiven...
2014 Aug 21
3
[LLVMdev] Liveness information still usable after register allocation?
Hi all,
Sorry to bother those not interested in this problem.
I have a problem while I want to reuse the liveness information after
register allocation.
When I use the livein_begin() from MachineBasicBlock to get the live-in
registers after
register alloction. I found that the liveness information is sometime
incorrect. For example,
some registers should be live-in to the machine basic block as
2015 Dec 04
2
analyzePhysReg question
...t lists.llvm.org> wrote:
>>
>>
>> I am looking at results from analyzePhysReg, and am getting results a little
>>
>> different than I expected for x86.
>>
>>
>> The call to this is coming from this code in
>>
>> llvm::MachineBasicBlock::computeRegisterLiveness
>>
>> 1163 MachineOperandIteratorBase::PhysRegInfo Analysis =
>> 1164 ConstMIOperands(I).analyzePhysReg(Reg, TRI);
>>
>> The instruction I being analyzed is:
>> %BX<def> = MOV16rm %EDI, 2, %ECX, 0, %noreg;
>>
>> mem:LD...
2015 Dec 04
2
analyzePhysReg question
I am looking at results from analyzePhysReg, and am getting results a little different than I expected for x86.
The call to this is coming from this code in llvm::MachineBasicBlock::computeRegisterLiveness
1163 MachineOperandIteratorBase::PhysRegInfo Analysis =
1164 ConstMIOperands(I).analyzePhysReg(Reg, TRI);
The instruction I being analyzed is:
%BX<def> = MOV16rm %EDI, 2, %ECX, 0, %noreg; mem:LD2[%arrayidx98](tbaa=!18)
and the Reg being passed in is 21, which is...
2015 Dec 04
2
analyzePhysReg question
...mith, Kevin B via llvm-dev <llvm-
>dev at lists.llvm.org> wrote:
>>
>> I am looking at results from analyzePhysReg, and am getting results a little
>different than I expected for x86.
>>
>> The call to this is coming from this code in
>llvm::MachineBasicBlock::computeRegisterLiveness
>> 1163 MachineOperandIteratorBase::PhysRegInfo Analysis =
>> 1164 ConstMIOperands(I).analyzePhysReg(Reg, TRI);
>>
>> The instruction I being analyzed is:
>> %BX<def> = MOV16rm %EDI, 2, %ECX, 0, %noreg;
>mem:LD2[%arrayidx98](tbaa=!1...
2015 Dec 04
2
analyzePhysReg question
...vm.org>> wrote:
>>>>
>>>> I am looking at results from analyzePhysReg, and am getting results a little
>>> different than I expected for x86.
>>>>
>>>> The call to this is coming from this code in
>>> llvm::MachineBasicBlock::computeRegisterLiveness
>>>> 1163 MachineOperandIteratorBase::PhysRegInfo Analysis =
>>>> 1164 ConstMIOperands(I).analyzePhysReg(Reg, TRI);
>>>>
>>>> The instruction I being analyzed is:
>>>> %BX<def> = MOV16rm %EDI, 2, %ECX, 0,...