Displaying 3 results from an estimated 3 matches for "r1300".
Did you mean:
1300
2008 Oct 20
3
[LLVMdev] Virtual Register allocation across functions
...s is to use virtual
registers, except that they are being restarted after each function and
clobbering registers in previous functions. For example:
start function 0
r1024 = mov %var0.0
r1025 = mov %var0.1
lots of intermediate code
call function1 w/ 3 parameters
more intermediate code
%r1300 = add %call.result, %r1024
end function 0
start function 1
%r1024 = mov %var1.0
%r1025 = mov %var1.1
%r1026 = mov %var1.2
some code
return some value
end function 0
The mov to r1024 in function 1 clobbers the data from function 0. The
only ways I can think to get around this, is to p...
2008 Oct 20
0
[LLVMdev] Virtual Register allocation across functions
No, there isn't something like that right now. What are you trying to
accomplish?
If you wish to implement this, it shouldn't be hard to do. Right now,
MachineRegisterInfo re-starts virtual register number at
TargetRegisterInfo::FirstVirtualRegister. You can add a mechanism to
change that to a variable instead.
Evan
On Oct 20, 2008, at 1:43 PM, Villmow, Micah wrote:
> Is
2008 Oct 20
2
[LLVMdev] Virtual Register allocation across functions
Is there currently a way to have virtual register allocation information
be saved across functions so that if I create a new virtual register in
a function that it doesn't use a virtual register allocated in any
previous function?
Thanks,
Micah Villmow
Systems Engineer
Advanced Technology & Performance
Advanced Micro Devices Inc.
4555 Great America Pkwy,
Santa Clara, CA. 95054