[llvm-dev] handling "overlapping" register classes
Preston Briggs via llvm-dev
llvm-dev at lists.llvm.org
Mon Oct 5 11:41:48 PDT 2015
I'm working on generating code for a machine that has a register set kind
of like the 68000.
For those who don't recall, the 68K has 8 Data registers that can be used
for ordinary integer
instructions like add, subtract, multiply, shift, etc., and 8 Address
registers that can be use for
integer addition and a few other things, especially base registers for
The Data register, on the other hand, cannot be used as base registers.
So, neither is more general than the other. We can use either for integer
but only Address registers as base registers and only Data registers for
multiplication, etc. (I may have a few details wrong, but since this is
only an example,
I don't think they're too important.)
Back when, I defined 3 register classes: Address, Data, and General,
where Address = 1, Data = 2, and General = 3.
My approach was to begin by defining every symbolic register (aka live
as General. Then I'd walk through all the instructions, intersecting the
for the particular instruction to yield a perhaps less general register
For example, an Add instruction would require and produce General registers
have add instructions for both Address and Data registers). But an
would require an Address register, so when we notice a General register
being used in
an addressing mode, intersection the Addressing requirement (= 1) with the
register (= 3) yields 1, implying the register needs to be an Address
When building the interference graph and noting that 2 live ranges were
if the intersection of their classes was non-zero, I'd add an interference
to the IG.
Similarly, I'd make symbolic registers of Address class interfere with all
Data registers and vice versa. In this fashion, since live ranges that are
(have higher degree) tend to be colored first, live ranges that must be
must be Data will end up in the right place, with the coloring algorithm
balancing everyone's requirements.
Care is required when a live range ends up with class = 0; implies copies
So, finally, my question: Is there any similar scheme in LLVM's code
What I'm looking for is a way to select the one of the two available
instructions (add using Address registers or add using Data registers) so
minimize the number of Address-Data copies.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev