|
Revision tags: llvmorg-3.1.0-rc2, llvmorg-3.1.0-rc1 |
|
| #
1fa5bcbe |
| 08-Feb-2012 |
Andrew Trick <[email protected]> |
Codegen pass definition cleanup. No functionality.
Moving toward a uniform style of pass definition to allow easier target configuration. Globally declare Pass ID. Globally declare pass initializer.
Codegen pass definition cleanup. No functionality.
Moving toward a uniform style of pass definition to allow easier target configuration. Globally declare Pass ID. Globally declare pass initializer. Use INITIALIZE_PASS consistently. Add a call to the initializer from CodeGen.cpp. Remove redundant "createPass" functions and "getPassName" methods.
While cleaning up declarations, cleaned up comments (sorry for large diff).
llvm-svn: 150100
show more ...
|
|
Revision tags: llvmorg-3.0.0, llvmorg-3.0.0-rc4, llvmorg-3.0.0-rc3, llvmorg-3.0.0-rc2, llvmorg-3.0.0-rc1, llvmorg-2.9.0, llvmorg-2.9.0-rc3, llvmorg-2.9.0-rc2, llvmorg-2.9.0-rc1 |
|
| #
2f931281 |
| 10-Jan-2011 |
Anton Korobeynikov <[email protected]> |
Rename TargetFrameInfo into TargetFrameLowering. Also, put couple of FIXMEs and fixes here and there.
llvm-svn: 123170
|
| #
d23b3d2d |
| 07-Jan-2011 |
Bob Wilson <[email protected]> |
Fix a comment typo.
llvm-svn: 122994
|
| #
3fff1fd4 |
| 17-Dec-2010 |
Bill Wendling <[email protected]> |
During local stack slot allocation, the materializeFrameBaseRegister function may be called. If the entry block is empty, the insertion point iterator will be the "end()" value. Calling ->getParent()
During local stack slot allocation, the materializeFrameBaseRegister function may be called. If the entry block is empty, the insertion point iterator will be the "end()" value. Calling ->getParent() on it (among others) causes problems.
Modify materializeFrameBaseRegister to take the machine basic block and insert the frame base register at the beginning of that block. (It's very similar to what the code does all ready. The only difference is that it will always insert at the beginning of the entry block instead of after a previous materialization of the frame base register. I doubt that that matters here.)
<rdar://problem/8782198>
llvm-svn: 122104
show more ...
|
|
Revision tags: llvmorg-2.8.0, llvmorg-2.8.0-rc3, llvmorg-2.8.0-rc2, llvmorg-2.8.0-rc1, llvmorg-2.8.0-rc0 |
|
| #
365e931f |
| 31-Aug-2010 |
Jim Grosbach <[email protected]> |
Improve virtual frame base register allocation heuristics.
1. Allocate them in the entry block of the function to enable function-wide re-use. The instructions to create them should be re-mat
Improve virtual frame base register allocation heuristics.
1. Allocate them in the entry block of the function to enable function-wide re-use. The instructions to create them should be re-materializable, so there shouldn't be additional cost compared to creating them local to the basic blocks where they are used. 2. Collect all of the frame index references for the function and sort them by the local offset referenced. Iterate over the sorted list to allocate the virtual base registers. This enables creation of base registers optimized for positive-offset access of frame references. (Note: This may be appropriate to later be a target hook to do the sorting in a target appropriate manner. For now it's done here for simplicity.)
llvm-svn: 112609
show more ...
|
| #
2eedb794 |
| 24-Aug-2010 |
Jim Grosbach <[email protected]> |
Add ARM heuristic for when to allocate a virtual base register for stack access. rdar://8277890&7352504
llvm-svn: 111968
|
| #
b77d67f3 |
| 24-Aug-2010 |
Jim Grosbach <[email protected]> |
Move enabling the local stack allocation pass into the target where it belongs. For now it's still a command line option, but the interface to the generic code doesn't need to know that.
llvm-svn: 1
Move enabling the local stack allocation pass into the target where it belongs. For now it's still a command line option, but the interface to the generic code doesn't need to know that.
llvm-svn: 111942
show more ...
|
| #
754f8e60 |
| 23-Aug-2010 |
Jim Grosbach <[email protected]> |
Better handling of local offsets for downwards growing stacks. This corrects relative offsets when there are offsets encoded in the instructions and simplifies final allocation in PEI. rdar://8277890
Better handling of local offsets for downwards growing stacks. This corrects relative offsets when there are offsets encoded in the instructions and simplifies final allocation in PEI. rdar://8277890
llvm-svn: 111836
show more ...
|
| #
7648a211 |
| 20-Aug-2010 |
Jim Grosbach <[email protected]> |
Downwards growing stack allocation order reverses relative offsets
llvm-svn: 111673
|
| #
7110941d |
| 20-Aug-2010 |
Jim Grosbach <[email protected]> |
Add more dbg output
llvm-svn: 111670
|
| #
0600691f |
| 20-Aug-2010 |
Jim Grosbach <[email protected]> |
properly check for whether base regs were inserted
llvm-svn: 111646
|
| #
56e56323 |
| 19-Aug-2010 |
Jim Grosbach <[email protected]> |
Better handling of offsets on frame index references. rdar://8277890
llvm-svn: 111585
|
| #
743d7c80 |
| 19-Aug-2010 |
Jim Grosbach <[email protected]> |
Update local stack block allocation to let PEI do the allocs if no additional base registers were required. This will allow for slightly better packing of the locals when alignment padding is necessa
Update local stack block allocation to let PEI do the allocs if no additional base registers were required. This will allow for slightly better packing of the locals when alignment padding is necessary after callee saved registers.
llvm-svn: 111508
show more ...
|
| #
3ac05936 |
| 18-Aug-2010 |
Jim Grosbach <[email protected]> |
Add a newline to debug output
llvm-svn: 111453
|
| #
dbfc2ce9 |
| 18-Aug-2010 |
Jim Grosbach <[email protected]> |
Enable ARM base register reuse to local stack slot allocation. Whenever a new frame index reference to an object in the local block is seen, check if it's near enough to any previously allocaated bas
Enable ARM base register reuse to local stack slot allocation. Whenever a new frame index reference to an object in the local block is seen, check if it's near enough to any previously allocaated base register to re-use.
rdar://8277890
llvm-svn: 111443
show more ...
|
| #
e0e9b301 |
| 18-Aug-2010 |
Jim Grosbach <[email protected]> |
Add hook for re-using virtual base registers for local stack slot access. Nothing fancy, just ask the target if any currently available base reg is in range for the instruction under consideration an
Add hook for re-using virtual base registers for local stack slot access. Nothing fancy, just ask the target if any currently available base reg is in range for the instruction under consideration and use the first one that is. Placeholder ARM implementation simply returns false for now.
ongoing saga of rdar://8277890
llvm-svn: 111374
show more ...
|
| #
3cf08661 |
| 17-Aug-2010 |
Jim Grosbach <[email protected]> |
Add materialization of virtual base registers for frame indices allocated into the local block. Resolve references to those indices to a new base register. For simplification and testing purposes, a
Add materialization of virtual base registers for frame indices allocated into the local block. Resolve references to those indices to a new base register. For simplification and testing purposes, a new virtual base register is allocated for each frame index being resolved. The result is truly horrible, but correct, code that's good for exercising the new code paths.
Next up is adding thumb1 support, which should be very simple. Following that will be adding base register re-use and implementing a reasonable ARM heuristic for when a virtual base register should be generated at all.
llvm-svn: 111315
show more ...
|
| #
1a58ce76 |
| 17-Aug-2010 |
Jim Grosbach <[email protected]> |
silence warning
llvm-svn: 111274
|
| #
c252ee23 |
| 17-Aug-2010 |
Jim Grosbach <[email protected]> |
Add hook to examine an instruction referencing a frame index to determine whether to allocate a virtual frame base register to resolve the frame index reference in it. Implement a simple version for
Add hook to examine an instruction referencing a frame index to determine whether to allocate a virtual frame base register to resolve the frame index reference in it. Implement a simple version for ARM to aid debugging.
In LocalStackSlotAllocation, scan the function for frame index references to local frame indices and ask the target whether to allocate virtual frame base registers for any it encounters. Purely infrastructural for debug output. Next step is to actually allocate base registers, then add intelligent re-use of them.
rdar://8277890
llvm-svn: 111262
show more ...
|
| #
a7c562d6 |
| 16-Aug-2010 |
Jim Grosbach <[email protected]> |
tidy up. remove unused local.
llvm-svn: 111206
|
| #
36d5ec38 |
| 16-Aug-2010 |
Jim Grosbach <[email protected]> |
Better handle alignment requirements for local objects in pre-regalloc frame mapping. Have the local block track its alignment requirement, and then apply that when the block itself is allocated. Pre
Better handle alignment requirements for local objects in pre-regalloc frame mapping. Have the local block track its alignment requirement, and then apply that when the block itself is allocated. Previously, offsets could get adjusted in PEI to be different, relative to one another, than the block allocation thought they would be, which defeats the point of doing the allocation this way. Continuing rdar://8277890
llvm-svn: 111197
show more ...
|
| #
8be0196a |
| 16-Aug-2010 |
Jim Grosbach <[email protected]> |
track local frame size in MFI, not local to the pass, since PEI needs it.
llvm-svn: 111164
|
| #
a030fa52 |
| 14-Aug-2010 |
Jim Grosbach <[email protected]> |
Add a local stack object block allocation pass. This is still an experimental pass that allocates locals relative to one another before register allocation and then assigns them to actual stack slots
Add a local stack object block allocation pass. This is still an experimental pass that allocates locals relative to one another before register allocation and then assigns them to actual stack slots as a block later in PEI. This will eventually allow targets with limited index offset range to allocate additional base registers (not just FP and SP) to more efficiently reference locals, as well as handle situations where locals cannot be referenced via SP or FP at all (dynamic stack realignment together with variable sized objects, for example). It's currently incomplete and almost certainly buggy. Work in progress.
Disabled by default and gated via the -enable-local-stack-alloc command line option.
rdar://8277890
llvm-svn: 111059
show more ...
|