search for: regsoverlap

...ture also means that the complete set of aliasing registers can get quite large. Some NEON registers have more than 40 aliases. The register units help control that complexity. Each physreg has an associated set of regunits, and two physregs alias if and only if their regunit sets overlap. See TRI::regsOverlap(). The regunits usually correspond to the leaf sub-registers - the registers that have no sub-registers themselves. However, the numbering is different, and if you use 'Aliases = ...' in your register file, they no longer correspond exactly to the leaf registers. /jakob

...fined, used, and killed. So your example should look like: entry (0x8503c80, LLVM BB @0x8501af0, ID#0): Live Ins: %R0 %R1 %reg1024 = ORI %R0<kill>, 0, %V4R0<imp-use> %reg1025 = ORI %R1<kill>, 0, %V4R0<imp-use,kill> KillsRegister should check for exact match rather than regsOverlap. There are probably other similar bugs in LiveVariables. Please file a bug, I'll look at after I get back from vacation in a week. Evan > > Thanks > -- > Christopher Lamb > > > > _______________________________________________ > LLVM Developers mailing list &gt...

Jakob Stoklund Olesen <stoklund at 2pi.dk> writes: >> A MachineOperand has both a getReg() and a getSubReg() interface. >> For a physical register operand, is getReg() guaranteed to be the >> "most super" register with getSubReg() providing the specific >> subregister information for the operand? If so then for my current >> purposes it seems I

On Mar 27, 2007, at 3:25 PM, Evan Cheng wrote: > > On Mar 25, 2007, at 7:12 AM, Christopher Lamb wrote: > >> While beginning to add vector registers to a back end I came >> across the following problem: as soon as I define two sets of >> registers that have a many-to-one mapping the live interval pass >> appears to double-kill the mapped-onto register. I