[llvm-dev] Status of PBQP register allocator?

[Nate Voorhies via llvm-dev]

Hi all,

I was wondering about whether the PBQP register allocator is likely to be
maintained in the future.  It's proving to be a nice way to encode some
instruction encoding constraints for an out-of-tree backend we have, but
there's concern about it being abandoned or bitrotting in the future.

Also, if PBQP is likely to lapse out of regular maintenance in the future,
is there a simple way to express constraints on allocated registers (such
as sharing an encoding, despite being in different register classes) chosen
for a particular instruction in the Greedy allocator?

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171005/85595ef9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4837 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171005/85595ef9/attachment.bin>