search for: 560327b3

On Sep 7, 2010, at 6:27 PM, Lang Hames wrote: > The design I have in mind is this: We add a method to TargetRegisterInfo which returns a PBQPProblemBuilder for the target architectures. I implement a base PBQPProblemBuilder by simply lifting the current construction process out of the PBQP allocator and into its own class. Anyone (such as yourself, Carlos) who wants to represent more esoteric

...> > It might as well register a function that allocates AND configures PBQP > properly then. There is no need for a target hook. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100909/560327b3/attachment.html>

Hi Carlos, Jakob, The PBQP allocator was designed to support a very wide range of constraints, and can handle something like this easily. Say you have 4 of these orX/irX registers, then for any pair of virtual registers used in such an add instruction you would add the following constraint matrix to the PBQP instance: [ 0 inf inf inf ] [ inf 0 inf inf ] [ inf inf 0 inf ] [ inf inf inf 0