| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
llvm-svn: 164139
|
|
|
|
|
|
| |
Patch by Adhemerval Zanella.
llvm-svn: 164138
|
|
|
|
|
|
|
|
| |
splitting aggregates into a real class.
No intended functionality change.
llvm-svn: 164135
|
|
|
|
|
|
|
|
|
| |
store this and use it to not emit long nops when the CPU is geode which
doesnt support them.
Fixes PR11212.
llvm-svn: 164132
|
|
|
|
|
|
| |
...I don't know why this could appease msvc...baad.
llvm-svn: 164130
|
|
|
|
|
|
| |
builders green again.
llvm-svn: 164124
|
|
|
|
|
|
| |
a fix to getCommonType in the previous patch.
llvm-svn: 164120
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
FCAs. This is essential in order to promote allocas that are used in
struct returns by frontends like Clang. The FCA load would block the
rest of the pass from firing, resulting is significant regressions with
the bullet benchmark in the nightly test suite.
Thanks to Duncan for repeated discussions about how best to do this, and
to both him and Benjamin for review.
This appears to have blocked many places where the pass tries to fire,
and so I'm expect somewhat different results with this fix added.
As with the last big patch, I'm including a change to enable the SROA by
default *temporarily*. Ben is going to remove this as soon as the LNT
bots pick up the patch. I'm just trying to get a round of LNT numbers
from the stable machines in the lab.
NOTE: Four clang tests are expected to fail in the brief window where
this is enabled. Sorry for the noise!
llvm-svn: 164119
|
|
|
|
| |
llvm-svn: 164117
|
|
|
|
|
|
| |
- when we may clobber the other S-lane by converting an S to a D instruction, make an effort to work out if the S lane is clobberable or not.
llvm-svn: 164114
|
|
|
|
|
|
|
|
| |
Now where we used to call ReInitMCSubtargetInfo, we actually recompute
the same information as InitMCSubtargetInfo instead of only setting
the feature bits.
llvm-svn: 164105
|
|
|
|
| |
llvm-svn: 164098
|
|
|
|
|
|
| |
model.
llvm-svn: 164092
|
|
|
|
|
|
| |
LLVM_DELETED_FUNCTION.
llvm-svn: 164090
|
|
|
|
|
|
|
|
|
| |
aligned address. Based on patch by David Peixotto.
Also use vld1.64 / vst1.64 with 128-bit alignment to take advantage of alignment
hints. rdar://12090772, rdar://12238782
llvm-svn: 164089
|
|
|
|
| |
llvm-svn: 164087
|
|
|
|
|
|
| |
and a conditional branch; also when removing dead cases from a switch.
llvm-svn: 164084
|
|
|
|
|
|
|
| |
Hanlde the case when we split the default edge if the default target has "icmp"
and unconditinal branch.
llvm-svn: 164076
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add LIS::pruneValue() and extendToIndices(). These two functions are
used by the register coalescer when merging two live ranges requires
more than a trivial value mapping as supported by LiveInterval::join().
The pruneValue() function can remove the part of a value number that is
going to conflict in join(). Afterwards, extendToIndices can restore the
live range, using any new dominating value numbers and updating the SSA
form.
Use this complex value mapping to support merging a register into a
vector lane that has a conflicting value, but the clobbered lane is
undef.
llvm-svn: 164074
|
|
|
|
|
|
|
|
|
|
| |
These extra operands are not needed by register allocators using
VirtRegRewriter, and RAFast don't need them any longer.
By omitting the <imp-def> operands, it becomes possible for the new
register coalescer to track which lanes are valid and which are undef.
llvm-svn: 164073
|
|
|
|
|
|
|
| |
I have to work out the Target/CodeGen header dependencies
before putting this back.
llvm-svn: 164072
|
|
|
|
| |
llvm-svn: 164068
|
|
|
|
| |
llvm-svn: 164066
|
|
|
|
| |
llvm-svn: 164065
|
|
|
|
|
|
| |
model.
llvm-svn: 164061
|
|
|
|
|
|
| |
While we are setting the earlier def to true, also make it live.
llvm-svn: 164056
|
|
|
|
|
|
| |
destination in SimplifyCondBranchToCondBranch.
llvm-svn: 164054
|
|
|
|
|
|
|
|
| |
we will do that when we implement the full save/restore.
Patch by Reed Kotler.
llvm-svn: 164051
|
|
|
|
|
|
| |
frequently called for some backends, and growing into an std::set is overkill for these numbers.
llvm-svn: 164044
|
|
|
|
| |
llvm-svn: 164043
|
|
|
|
|
|
|
| |
- Preserve the original NOutVT during casting from vector to integer by
extracting vector elements.
llvm-svn: 164042
|
|
|
|
| |
llvm-svn: 164040
|
|
|
|
|
|
| |
function warnings use LLVM_ATTRIBUTE_UNUSED.
llvm-svn: 164036
|
|
|
|
|
|
| |
MSVC8 won't compile lower_bound if one is missing.
llvm-svn: 164035
|
|
|
|
|
|
| |
The cases where no initialization happens should still be checked for logic flaws.
llvm-svn: 164032
|
|
|
|
| |
llvm-svn: 164030
|
|
|
|
|
|
| |
This is used in the AMDIL and R600 backends.
llvm-svn: 164029
|
|
|
|
|
|
| |
passes. This may break the buildbots. I plan to revert it in a few hours.
llvm-svn: 164024
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
partition use lists a bit. No functionality changed.
These visitors are actually visiting a tuple of a Use and an offset into
the alloca. However, we use the InstVisitor to handle the dispatch over
the users, and so the Use and Offset are stored in class member
variables and set just before each call to visit(). This is fairly
awkward and makes the functions a bit harder to read, but its the only
real option we have until InstVisitor can be rewritten to use variadic
templates.
However, this pattern shouldn't be followed on the helper member
functions where there is no interface constraint from the visitor. We
already were passing the instruction as a normal parameter rather than
use the Use to get at it, start passing the offset as well. This will
become more important in subsequent patches as the offset will in some
cases change while visiting a single instruction.
llvm-svn: 164003
|
|
|
|
| |
llvm-svn: 164001
|
|
|
|
| |
llvm-svn: 164000
|
|
|
|
|
|
|
|
|
|
|
| |
wide vector types.
It had patterns for zext-loading and extending. This commit adds patterns for loading a wide type, performing a bitcast,
and extending. This is an odd pattern, but it is commonly used when writing code with intrinsics.
rdar://11897677
llvm-svn: 163995
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The live range of an SSA value forms a sub-tree of the dominator tree.
That means the live ranges of two values overlap if and only if the def
of one value lies within the live range of the other.
This can be used to simplify the interference checking a bit: Visit each
def in the two registers about to be joined. Check for interference
against the value that is live in the other register at the def point
only. It is not necessary to scan the set of overlapping live ranges,
this interference check can be done while computing the value mapping
required for the final live range join.
The new algorithm is prepared to handle more complicated conflict
resolution - We can allow overlapping live ranges with different values
as long as the differing lanes are undef or unused in the other
register.
The implementation in this patch doesn't do that yet, it creates code
that is nearly identical to the old algorithm's, except:
- The new stripCopies() function sees through multiple copies while
the old RegistersDefinedFromSameValue() only can handle one.
- There are a few rare cases where the new algorithm can erase an
IMPLICIT_DEF instuction that RegistersDefinedFromSameValue() couldn't
handle.
llvm-svn: 163991
|
|
|
|
| |
llvm-svn: 163974
|
|
|
|
| |
llvm-svn: 163973
|
|
|
|
|
|
|
| |
Kill flags are removed more and more aggressively during the register
allocation passes, it is better to get information from LiveIntervals.
llvm-svn: 163972
|
|
|
|
| |
llvm-svn: 163970
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
What we have so far:
- Some clang test failures (these were known already)
- Perf results are mixed, some big regressions
http://llvm.org/perf/db_default/v4/nts/3844
http://llvm.org/perf/db_default/v4/nts/3845
bullet suffers a lot. matmul is interesting: slower scalar code, faster with -vectorize.
- Some dragonegg selfhost bots crash in SROA during selfhost now
http://lab.llvm.org:8011/builders/dragonegg-x86_64-linux-gcc-4.6-self-host-checks/builds/1632
http://lab.llvm.org:8011/builders/dragonegg-x86_64-linux-gcc-4.5-self-host/builds/1891
llvm-svn: 163968
|
|
|
|
|
|
| |
This was only an issue if sse is disabled.
llvm-svn: 163967
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
new one, and add support for running the new pass in that mode and in
that slot of the pass manager. With this the new pass can completely
replace the old one within the pipeline.
The strategy for enabling or disabling the SSAUpdater logic is to do it
by making the requirement of the domtree analysis optional. By default,
it is required and we get the standard mem2reg approach. This is usually
the desired strategy when run in stand-alone situations. Within the
CGSCC pass manager, we disable requiring of the domtree analysis and
consequentially trigger fallback to the SSAUpdater promotion.
In theory this would allow the pass to re-use a domtree if one happened
to be available even when run in a mode that doesn't require it. In
practice, it lets us have a single pass rather than two which was
simpler for me to wrap my head around.
There is a hidden flag to force the use of the SSAUpdater code path for
the purpose of testing. The primary testing strategy is just to run the
existing tests through that path. One notable difference is that it has
custom code to handle lifetime markers, and one of the tests has been
enhanced to exercise that code.
This has survived a bootstrap and the test suite without serious
correctness issues, however my run of the test suite produced *very*
alarming performance numbers. I don't entirely understand or trust them
though, so more investigation is on-going.
To aid my understanding of the performance impact of the new SROA now
that it runs throughout the optimization pipeline, I'm enabling it by
default in this commit, and will disable it again once the LNT bots have
picked up one iteration with it. I want to get those bots (which are
much more stable) to evaluate the impact of the change before I jump to
any conclusions.
NOTE: Several Clang tests will fail because they run -O3 and check the
result's order of output. They'll go back to passing once I disable it
again.
llvm-svn: 163965
|