| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
"is is" -> "is", "if if" -> "if", "or or" -> "or"
llvm-svn: 329878
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
In the test case, the machine scheduler moves a dead write to a subreg
up into the middle of a segment of the overall reg's live range, where
the segment had liveness only for other subregs in the reg.
handleMoveUp created an invalid live range, causing an assert a bit
later.
This commit fixes it to handle that situation. The segment is split in
two at the insertion point, and the part after the split, and any
subsequent segments up to the old position, are changed to be defined by
the moved def.
V2: Better test.
Subscribers: MatzeB, nhaehnle, llvm-commits
Differential Revision: https://reviews.llvm.org/D43478
Change-Id: Ibc42445ddca84e79ad1f616401015d22bc63832e
llvm-svn: 326087
|
| |
|
|
|
|
|
|
|
|
| |
Headers/Implementation files should be named after the class they
declare/define.
Also eliminated an `#include "llvm/CodeGen/LiveIntervalAnalysis.h"` in
favor of `class LiveIntarvals;`
llvm-svn: 320546
|
| |
|
|
| |
llvm-svn: 15135
|
| |
|
|
|
|
|
|
|
|
|
|
| |
will soon be renamed) into their own file. The new file should not emit
DEBUG output or have other side effects. The LiveInterval class also now
doesn't know whether its working on registers or some other thing.
In the future we will want to use the LiveInterval class and friends to do
stack packing. In addition to a code simplification, this will allow us to
do it more easily.
llvm-svn: 15134
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use an explicit LiveRange class to represent ranges instead of an std::pair.
This is a minor cleanup, but is really intended to make a future patch simpler
and less invasive.
Alkis, could you please take a look at LiveInterval::liveAt? I suspect that
you can add an operator<(unsigned) to LiveRange, allowing us to speed up the
upper_bound call by quite a bit (this would also apply to other callers of
upper/lower_bound). I would do it myself, but I still don't understand that
crazy liveAt function, despite the comment. :)
Basically I would like to see this:
LiveRange dummy(index, index+1);
Ranges::const_iterator r = std::upper_bound(ranges.begin(),
ranges.end(),
dummy);
Turn into:
Ranges::const_iterator r = std::upper_bound(ranges.begin(),
ranges.end(),
index);
llvm-svn: 15130
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
interfere. Because these intervals have a single definition, and one of them
is a copy instruction, they are always safe to merge even if their lifetimes
interfere. This slightly reduces the amount of spill code, for example on
252.eon, from:
12837 spiller - Number of loads added
7604 spiller - Number of stores added
5842 spiller - Number of register spills
18155 liveintervals - Number of identity moves eliminated after coalescing
to:
12754 spiller - Number of loads added
7585 spiller - Number of stores added
5803 spiller - Number of register spills
18262 liveintervals - Number of identity moves eliminated after coalescing
The much much bigger win would be to merge intervals with multiple definitions
(aka phi nodes) but this is not that day.
llvm-svn: 15124
|
| |
|
|
| |
llvm-svn: 15115
|
| |
|
|
|
|
|
| |
intervals need not be sorted anymore. Removing this redundant step
improves LiveIntervals running time by 5% on 176.gcc.
llvm-svn: 15106
|
| |
|
|
|
|
|
| |
fortunately, they are easy to handle if we know about them. This patch fixes
some serious pessimization of code produced by the linscan register allocator.
llvm-svn: 15092
|
| |
|
|
|
|
| |
"Support/Debug.h".
llvm-svn: 15089
|
| |
|
|
| |
llvm-svn: 15031
|
| |
|
|
| |
llvm-svn: 15005
|
| |
|
|
|
|
|
| |
is a simple change, but seems to improve code a little. For example, on
256.bzip2, we went from 75.0s -> 73.33s (2% speedup).
llvm-svn: 15004
|
| |
|
|
| |
llvm-svn: 15003
|
| |
|
|
|
|
| |
ask instructions for their parent.
llvm-svn: 14998
|
| |
|
|
| |
llvm-svn: 14997
|
| |
|
|
|
|
|
|
|
|
| |
* vreg <-> vreg joining now works, enable it unconditionally when joining
is enabled (which is the default).
* Fix a serious pessimization of spill code where we were saying that a
spilled DEF operand was live into the subsequent instruction. This allows
for substantially better code when spilling starts to happen.
llvm-svn: 14993
|
| |
|
|
|
|
|
|
|
| |
order, causing the inactive list in the linearscan list to get unsorted, which
basically fuxored everything up severely.
These seems to fix the joiner, so with more testing I will enable it by default.
llvm-svn: 14992
|
| |
|
|
|
|
|
|
|
|
| |
Heavily refactor handleVirtualRegisterDef, adding comments and making it more
efficient. It is also much easier to follow and convince ones self that it is
correct :)
Add -debug output to the joine, showing the result of joining the intervals.
llvm-svn: 14989
|
| |
|
|
|
|
| |
but make virtreg->virtreg joining stay off by default
llvm-svn: 14916
|
| |
|
|
| |
llvm-svn: 14720
|
| |
|
|
| |
llvm-svn: 14719
|
| |
|
|
| |
llvm-svn: 14655
|
| |
|
|
|
|
|
| |
classes: just ignore that move. Thanks to Vladimir Prus who found the
bug!
llvm-svn: 14644
|
| |
|
|
|
|
| |
don't exist, we don't have to pretend to handle them.
llvm-svn: 14567
|
| |
|
|
|
|
| |
use them instead of a local LiveVariables numbering
llvm-svn: 14523
|
| |
|
|
|
|
| |
map.
llvm-svn: 14518
|
| |
|
|
|
|
| |
block.
llvm-svn: 14475
|
| |
|
|
| |
llvm-svn: 14474
|
| |
|
|
|
|
| |
MachineBasicBlock that is not yet attached to a MachineFunction. This change includes changing the third operand (TargetMachine) to a pointer for the MachineInstr::print function.
llvm-svn: 14389
|
| |
|
|
|
|
|
|
|
| |
existing llvm::Interval class.
Patch contributed by Vladimir Prus!
http://mail.cs.uiuc.edu/pipermail/llvmbugs/2004-June/000710.html
llvm-svn: 14281
|
| |
|
|
| |
llvm-svn: 13956
|
| |
|
|
| |
llvm-svn: 13910
|
| |
|
|
|
|
|
| |
spills. This allows for more flexibility when allocating registers for
spill code.
llvm-svn: 13907
|
| |
|
|
| |
llvm-svn: 13892
|
| |
|
|
| |
llvm-svn: 13416
|
| |
|
|
|
|
| |
workaround, use the C HUGE_VAL macro instead.
llvm-svn: 13377
|
| |
|
|
| |
llvm-svn: 13302
|
| |
|
|
| |
llvm-svn: 12872
|
| |
|
|
| |
llvm-svn: 12869
|
| |
|
|
| |
llvm-svn: 12866
|
| |
|
|
| |
llvm-svn: 12791
|
| |
|
|
|
|
| |
instruction to make the API more flexible.
llvm-svn: 12386
|
| |
|
|
| |
llvm-svn: 12058
|
| |
|
|
|
|
|
| |
MRegisterInfo::is{Physical,Virtual}Register. Apply appropriate fixes
to relevant files.
llvm-svn: 11882
|
| |
|
|
| |
llvm-svn: 11721
|
| |
|
|
|
|
| |
parts of the compiler
llvm-svn: 11719
|
| |
|
|
| |
llvm-svn: 11704
|
| |
|
|
|
|
|
| |
Also make it less aggressive as the current implementation breaks in
some cases.
llvm-svn: 11696
|