[PATCH] [PBQP] Teach PassConfig to tell if the default register allocator is used

Arnaud De Grandmaison Arnaud.DeGrandmaison at arm.com
Tue Oct 21 14:04:29 PDT 2014


Answering to myself there: the part of the patch affecting TargetPassConfig can be simplified to something innocuous. I thus updated the patch and went for post-commit review with r220321.

From: llvm-commits-bounces at cs.uiuc.edu [mailto:llvm-commits-bounces at cs.uiuc.edu] On Behalf Of Arnaud A. de Grandmaison
Sent: 21 October 2014 19:10
To: llvm-commits at cs.uiuc.edu; 'Lang Hames'
Subject: [PATCH] [PBQP] Teach PassConfig to tell if the default register allocator is used

This enables targets to adapt their pass pipeline to the register allocator in use.

For example, with the AArch64 backend, when using PBQP with cortex-a57, the FPLoadBalancing pass is no longer necessary.

This patch addresses the last bits of the changes made by Lang Hames on improving how targets can provide their own constraint builders @r219421, and provides a generic way which can be used by other backends.

This is not as flexible as I would like it to be, as it can only tell if the default allocator was superseded on the command line (we do not know which one was actually selected), but this is simple enough for now and I doubt many people are playing with more than 2 allocators at the same time...

Cheers,
--
Arnaud A. de Grandmaison


-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20141021/18602bf3/attachment.html>


More information about the llvm-commits mailing list