search for: hasinterval

...y has a different value at the new location. Reserved registers without any defs anywhere in the function are treated as ambient registers that can be read anywhere. These registers don't get a LiveInterval, and are skipped here: // Reserved registers are OK. if (MO.isUndef() || !lis.hasInterval(MO.getReg())) continue; Reserved registers with defs get LiveIntervals, and are value-checked just like virtual registers. Also note that unreserved, unallocatable registers exist. For example the ARM %cpsr status register. /jakob

I'm working on some enhancements to rematerialization that I hope to contribute. It's mostly working but I am running into one problem. It boils down to having spilled a register used by the remat candidate. I thought this is what getReMatImplicitUse is supposed to handle but it looks inconsistent to me. The comment says this: /// getReMatImplicitUse - If the remat definition MI has

...location. Yes. > Reserved registers without any defs anywhere in the function are > treated as ambient registers that can be read anywhere. These > registers don't get a LiveInterval, and are skipped here: > > // Reserved registers are OK. > if (MO.isUndef() || !lis.hasInterval(MO.getReg())) > continue; Ok, that translates to getReMatImplicitUse pretty well. > Reserved registers with defs get LiveIntervals, and are value-checked > just like virtual registers. Yes. > Also note that unreserved, unallocatable registers exist. For example > the ARM %...