llvm-svn: 114835

Add constified overloads for findNearestCommonDominator.

llvm-svn: 114834

llvm-svn: 114832

to link in "core".

llvm-svn: 114831

llvm-svn: 114830

rename writeHeader's Name argument to Title, to be consistent
with WriteGraph.

llvm-svn: 114829

llvm-svn: 114828

llvm-svn: 114827

llvm-svn: 114826

llvm-svn: 114825

targeted at symbols into relocations relative to the containing section.

Patch by Nathan Jeffords!

llvm-svn: 114823

llvm-svn: 114822

llvm-svn: 114821

llvm-svn: 114819

My previous fix for rdar://8456371 should only apply to fmulp/faddp,
not to fmul/fadd.  Instruction set orthogonality is overrated or 
something.

llvm-svn: 114818

support aligned comm.  Detect when compiling for 10.4 and don't
emit an alignment for comm.  THis will hopefully fix PR8198.

llvm-svn: 114817

llvm-svn: 114815

divide support also.

llvm-svn: 114813

llvm-svn: 114812

llvm-svn: 114811

but balrog was wanting it on irc.

llvm-svn: 114809

Fixed some tests to avoid LiveIntervals::getInstructionFromIndex(..) overhead where possible. Thanks to Jakob for the suggestions.

llvm-svn: 114798

not generating build targets for those parts of the build.

llvm-svn: 114797

for real.

Patch by Nathan Jeffords!

llvm-svn: 114796

available targets unless LLVM_INCLUDE_X is ON. LLVM_BUILD_X implies
LLVM_INCLUDE_X"

It breaks the configuration phase when cmake is invoked without
parameters, it is too complex for the purpose and introduces an
incovenience for the user (as both LLVM_BUILD_X and LLVM_INCLUDE_X
must set to OFF for not including X on the build)

llvm-svn: 114795

llvm-svn: 114794

llvm-svn: 114792

Removed VNInfo::isDefAccurate(). Def "accuracy" can be checked by testing whether LiveIntervals::getInstructionFromIndex(def) returns NULL.

llvm-svn: 114791

llvm-svn: 114789

llvm-svn: 114788

llvm-svn: 114787

symbols defined in merge sections in independent atoms.

llvm-svn: 114786

LoadPRE was not properly checking that the load it was PRE'ing post-dominated the block it was being hoisted to.
Splitting critical edges at the merge point only addressed part of the issue; it is also possible for non-post-domination
to occur when the path from the load to the merge has branches in it.  Unfortunately, full anticipation analysis is
time-consuming, so for now approximate it.  This is strictly more conservative than real anticipation, so we will miss
some cases that real PRE would allow, but we also no longer insert loads into paths where they didn't exist before. :-)

This is a very slight net positive on SPEC for me (0.5% on average).  Most of the benchmarks are largely unaffected, but
when it pays off it pays off decently: 181.mcf improves by 4.5% on my machine.

llvm-svn: 114785

llvm-svn: 114784

llvm-svn: 114782

of the source, not the original alignment since it may no longer
be valid.

Fixes rdar://8400094

llvm-svn: 114781

llvm-svn: 114780

llvm-svn: 114779

and it will be removed shortly.

llvm-svn: 114778

llvm-svn: 114776