diff options
author | Quentin Colombet <qcolombet@apple.com> | 2017-04-01 01:26:14 +0000 |
---|---|---|
committer | Quentin Colombet <qcolombet@apple.com> | 2017-04-01 01:26:14 +0000 |
commit | 7f64318938cecbe53ee3ba59c79dd3b32cb7373b (patch) | |
tree | 0638a4c990b690e87dfa3f0c10b37dc845bcd7f2 /llvm/lib/CodeGen/SafeStackColoring.cpp | |
parent | b43da15602e271ff8a3bbcf2f2d16378e31bc76c (diff) | |
download | bcm5719-llvm-7f64318938cecbe53ee3ba59c79dd3b32cb7373b.tar.gz bcm5719-llvm-7f64318938cecbe53ee3ba59c79dd3b32cb7373b.zip |
[RegBankSelect] Support REG_SEQUENCE for generic mapping
REG_SEQUENCE falls into the same category as COPY for operands mapping:
- They don't have MCInstrDesc with register constraints
- The input variable could use whatever register classes
- It is possible to have register class already assigned to the operands
In particular, given REG_SEQUENCE are always target specific because of
the subreg indices. Those indices must apply to the register class of
the definition of the REG_SEQUENCE and therefore, the target must set a
register class to that definition. As a result, the generic code can
always use that register class to derive a valid mapping for a
REG_SEQUENCE.
llvm-svn: 299285
Diffstat (limited to 'llvm/lib/CodeGen/SafeStackColoring.cpp')
0 files changed, 0 insertions, 0 deletions