Displaying 4 results from an estimated 4 matches for "regallocbigblock".
2007 Nov 06
1
[LLVMdev] Question about register allocators
What is the status of RegAllocLocal, RegAllocBigBlock and
RegAllocSimple allocators? I am considering using one of them as a
basis for a course project on register allocation in my class. In
particular, are those allocators in regular use and/or have they been
tested recently? I am particularly interested in the code as of
version 4.0 but...
2007 Jul 13
0
[LLVMdev] [PATCH] Re: Pluggable Register Coalescers
...point
- virtual bool runOnMachineFunction(MachineFunction&);
+ virtual bool runOnMachineFunction(MachineFunction&mf) {
+ doWork(mf);
+ }
/// print - Implement the dump method.
virtual void print(std::ostream &O, const Module* = 0) const;
Index: llvm/lib/CodeGen/RegAllocBigBlock.cpp
===================================================================
--- llvm/lib/CodeGen/RegAllocBigBlock.cpp (revision 58818)
+++ llvm/lib/CodeGen/RegAllocBigBlock.cpp (working copy)
@@ -36,6 +36,7 @@
#include "llvm/CodeGen/MachineFrameInfo.h"
#include "llvm/CodeGen/LiveVariab...
2007 Jul 11
3
[LLVMdev] Pluggable Register Coalescers
On Jul 11, 2007, at 11:39 AM, David Greene wrote:
> On Wednesday 11 July 2007 12:41, Tanya M. Lattner wrote:
>
>> I think the coalescer should be flexible enough to be run
>> independent of
>> the register allocator. For example, you may want to expose the
>> copies
>> induced by transforming out of SSA to the scheduler. If the
>> scheduler is
2007 Jun 22
3
[LLVMdev] BigBlock register allocator
...stuck, using only a single register
(and the stack, a lot!) for hundreds or thousands of instructions at a
time, greatly slowing (+bloating) the code. Luckily, I didn't have the
presence of mind to actually try using the local register allocator
before I ripped its guts out, turning it into RegAllocBigBlock.cpp
that's now in CVS. (Had I done that, I would have been quite happy to
find that the local allocator produced much better code, much faster
than linearscan.)
The good news is the new "BigBlock" allocator turns out to produce even
better code than the local allocator when bloc...