search for: targetlacksphysicalregissters

Displaying 4 results from an estimated 4 matches for "targetlacksphysicalregissters".

2015 Dec 10
2
Allowing virtual registers after register allocation
...the regular infrastructure virtual registers. However we do run a custom register coloring pass which reduces the total number of virtual registers used. > Is the answer the same for the NVPTX backend? Yes (at least, they have a null TargetRegisterAllocator too). > Maybe something like: targetLacksPhysicalRegissters() would be better? > Maybe. We actually do have "physical" registers called SP and FP (returned by TargetRegisterInfo::getFrameRegister() and used by some default ISel lowerings and by FrameIndex elimination) but of course they aren't really physical registers either. ------------...
2015 Dec 09
2
Allowing virtual registers after register allocation
Hi all, Virtual ISAs such as WebAssembly and NVPTX use infinite virtual register sets instead of traditional phsyical registers. PrologEpilogInserter is run after register allocation and asserts that all virtuals have been allocated but doesn't otherwise depend on this if scavenging is not needed. We'd like to use the target-independent PEI code for WebAssembly, so we're proposing a
2015 Dec 10
3
Allowing virtual registers after register allocation
...s. However we do run a custom register coloring pass which reduces the total number of virtual registers used. >> >> Is the answer the same for the NVPTX backend? >> >> Yes (at least, they have a null TargetRegisterAllocator too). >> >> Maybe something like: targetLacksPhysicalRegissters() would be better? >> >> Maybe. We actually do have "physical" registers called SP and FP (returned by TargetRegisterInfo::getFrameRegister() and used by some default ISel lowerings and by FrameIndex elimination) but of course they aren't really physical registers either....
2015 Dec 10
2
Allowing virtual registers after register allocation
...r coloring pass which >> reduces the total number of virtual registers used. >> >> >> Is the answer the same for the NVPTX backend? >> >> >> Yes (at least, they have a null TargetRegisterAllocator too). >> >> >> Maybe something like: targetLacksPhysicalRegissters() would be >> better? >> >> >> >> Maybe. We actually do have "physical" registers called SP and FP >> (returned by TargetRegisterInfo::getFrameRegister() and used by some >> default ISel lowerings and by FrameIndex elimination) but of course &g...