search for: createtargetregisterallocator

...ister > sets. > > Bikeshedding: usesVirtualRegstersAfterRegAlloc() - Are you actually > "allocating" virtual registers, or just using the ones that the > infrastructure already provides? Not exactly; the actual register allocation does nothing (i.e. WebAssemblyPassConfig::createTargetRegisterAllocator() returns nullptr) and we just use 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...

...>> >> Bikeshedding: usesVirtualRegstersAfterRegAlloc() - Are you actually "allocating" virtual registers, or just using the ones that the infrastructure already provides? >> >> Not exactly; the actual register allocation does nothing (i.e. WebAssemblyPassConfig::createTargetRegisterAllocator() returns nullptr) and we just use 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...

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

...sVirtualRegstersAfterRegAlloc() - Are you actually >> "allocating" virtual registers, or just using the ones that the >> infrastructure already provides? >> >> >> Not exactly; the actual register allocation does nothing (i.e. >> WebAssemblyPassConfig::createTargetRegisterAllocator() returns >> nullptr) and we just use 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? >>...