| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
| |
llvm-svn: 111082
|
| |
|
|
| |
llvm-svn: 111073
|
| |
|
|
| |
llvm-svn: 111068
|
| |
|
|
| |
llvm-svn: 111063
|
| |
|
|
| |
llvm-svn: 111061
|
| |
|
|
|
|
|
|
|
|
|
| |
- Eliminate redundant successors.
- Convert an indirectbr with one successor into a direct branch.
Also, generalize SimplifyCFG to be able to be run on a function entry block.
It knows quite a few simplifications which are applicable to the entry
block, and it only needs a few checks to avoid trouble with the entry block.
llvm-svn: 111060
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
had its address taken.
llvm-svn: 111058
|
| |
|
|
|
|
| |
This fixes another part of PR7792.
llvm-svn: 111057
|
| |
|
|
|
|
|
|
|
| |
The earliestStart argument is entirely specific to linear scan allocation, and
can be easily calculated by RegAllocLinearScan.
Replace std::vector with SmallVector.
llvm-svn: 111055
|
| |
|
|
| |
llvm-svn: 111050
|
| |
|
|
|
|
| |
instruction opcode. This fixes part of PR7792.
llvm-svn: 111047
|
| |
|
|
|
|
|
| |
when they are the same loop. Don't compare two instructions'
loop depths when they are in the same block.
llvm-svn: 111045
|
| |
|
|
|
|
|
|
| |
When a live range is contained a single block, we can split it around
instruction clusters. The current approach is very primitive, splitting before
and after the largest gap between uses.
llvm-svn: 111043
|
| |
|
|
|
|
|
| |
ScalarEvolution::getAddExpr, which can be pretty expensive, when nothing
has changed, which is pretty common.
llvm-svn: 111042
|
| |
|
|
| |
llvm-svn: 111041
|
| |
|
|
|
|
| |
rather than testing whether the loop contains the other's header.
llvm-svn: 111039
|
| |
|
|
| |
llvm-svn: 111038
|
| |
|
|
|
|
|
| |
the constant operand on the left, as that's where ScalarEvolution
will end up canonicalizing to.
llvm-svn: 111037
|
| |
|
|
|
|
|
| |
associated loop. This avoids potentially expensive traversals
of the add recurrence's operands.
llvm-svn: 111034
|
| |
|
|
|
|
| |
same lines as the change I made for ARM saturate instructions.
llvm-svn: 111029
|
| |
|
|
|
|
| |
misanalysis and is undesirable.
llvm-svn: 111028
|
| |
|
|
| |
llvm-svn: 111022
|
| |
|
|
| |
llvm-svn: 111021
|
| |
|
|
| |
llvm-svn: 111019
|
| |
|
|
| |
llvm-svn: 111001
|
| |
|
|
| |
llvm-svn: 111000
|
| |
|
|
|
|
|
|
|
|
| |
numbers match. The old check could accidentally leave holes in openli.
Also let useIntv add all ranges for the phi-def value inserted by
enterIntvAtEnd. This works as long at the value mapping is established in
enterIntvAtEnd.
llvm-svn: 110995
|
| |
|
|
|
|
| |
function to do it.
llvm-svn: 110994
|
| |
|
|
|
|
| |
it previously failed.
llvm-svn: 110987
|
| |
|
|
|
|
| |
catch bad shufflevector operations when they are created, rather than waiting for someone to notice later on.
llvm-svn: 110986
|
| |
|
|
| |
llvm-svn: 110983
|
| |
|
|
| |
llvm-svn: 110982
|
| |
|
|
| |
llvm-svn: 110981
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This can happen if the original interval has been broken into two disconnected
parts. Ideally, we should be able to detect when the graph is disconnected and
create separate intervals, but that code is not implemented yet.
Example:
Two basic blocks are both branching to a loop header. Our interval is defined in
both basic blocks, and live into the loop along both edges.
We decide to split the interval around the loop. The interval is split into an
inside part and an outside part. The outside part now has two disconnected
segments, one in each basic block.
If we later decide to split the outside interval into single blocks, we get one
interval per basic block and an empty dupli for the remainder.
llvm-svn: 110976
|
| |
|
|
|
|
|
| |
split intervals. THis means the analysis can be used for multiple splits as long
as curli doesn't shrink.
llvm-svn: 110975
|
| |
|
|
|
|
| |
before it rewrites the code, we need to use that in the post-rewrite pass.
llvm-svn: 110962
|
| |
|
|
| |
llvm-svn: 110954
|
| |
|
|
|
|
|
| |
the memory barrier variants (other than 'SY' full system domain read and write)
are treated as one instruction with option operand.
llvm-svn: 110951
|
| |
|
|
|
|
|
| |
If a phi-def value were removed from the interval, the phi-kill flags are no
longer valid.
llvm-svn: 110949
|
| |
|
|
|
|
| |
split point is in the middle of an IT block, it should move it up to just above the IT instruction. rdar://8302637
llvm-svn: 110947
|
| |
|
|
|
|
|
|
|
|
| |
Here we guess that AVX will have domain issues, so just implement them for consistency and in the future we remove if it's unnecessary.
- Make foldMemoryOperandImpl aware of 256-bit zero vectors folding and support the 128-bit counterparts of AVX too.
- Make sure MOV[AU]PS instructions are only selected when SSE1 is enabled, and duplicate the patterns to match AVX.
- Add a testcase for a simple 128-bit zero vector creation.
llvm-svn: 110946
|
| |
|
|
| |
llvm-svn: 110944
|
| |
|
|
| |
llvm-svn: 110940
|
| |
|
|
| |
llvm-svn: 110937
|
| |
|
|
|
|
|
|
|
|
| |
Before spilling a live range, we split it into a separate range for each basic
block where it is used. That way we only get one reload per basic block if the
new smaller ranges can allocate to a register.
This type of splitting is already present in the standard spiller.
llvm-svn: 110934
|
| |
|
|
|
|
|
|
| |
having it finish processing all of the muliply operands before
starting the whole getAddExpr process over again, instead of
immediately after the first simplification.
llvm-svn: 110916
|
| |
|
|
| |
llvm-svn: 110915
|
| |
|
|
|
|
|
|
| |
by having it finish processing the whole operand list before
starting the whole getAddExpr process over again, instead of
immediately after the first duplicate is found.
llvm-svn: 110914
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
target triple and straightens it out. This does less than gcc's script
config.sub, for example it turns i386-mingw32 into i386--mingw32 not
i386-pc-mingw32, but it does a decent job of turning funky triples into
something that the rest of the Triple class can understand. The plan
is to use this to canonicalize triple's when they are first provided
by users, and have the rest of LLVM only deal with canonical triples.
Once this is done the special case workarounds in the Triple constructor
can be removed, making the class more regular and easier to use. The
comments and unittests for the Triple class are already adjusted in this
patch appropriately for this brave new world of increased uniformity.
llvm-svn: 110909
|