llvm-svn: 114184

llvm-svn: 114183

llvm-svn: 114176

It is also workaround for PR7927.

llvm-svn: 114175

llvm-svn: 114173

used on Darwin anymore, and Clang might not always link with the library it is
currently found in.

llvm-svn: 114165

expression to include the modifier.
 - Gross, but this a corner case we don't expect to see often in practice, but
   it is worth accepting.
 - Also improves diagnostics on invalid modifiers.

llvm-svn: 114154

so that it detects errors on platforms where libm doesn't set errno.
It's still subject to host libm details though.

llvm-svn: 114148

because it was using Twine.h's declaration of operator<<(const Twine &).

llvm-svn: 114141

Allow the PassRegistry mutex to be lazily initialized, and clean up the global namespace at the same time.

llvm-svn: 114131

synchronize any method that might lazily initialize the pImpl.

llvm-svn: 114130

llvm-svn: 114128

llvm-svn: 114126

llvm-svn: 114121

If FE forgot to provide a file name (usually it uses "stdin" as name in such situation) then make one up to ensure that debug info is not malformed.

llvm-svn: 114119

Revert r114097, adding back in the assertion against replacing an Instruction by itself.  Now that CorrelatedValuePropagation is
more careful not to call SimplifyInstructionsInBlock() on an unreachable block, the issue has been fixed at a higher level.  Add
a big warning to SimplifyInstructionsInBlock() to hopefully prevent this in the future.

llvm-svn: 114117

llvm-svn: 114116

same order as gnu as.

llvm-svn: 114109

to optimize unreachable blocks.

llvm-svn: 114105

walking the asm arguments once and stashing their Values.  This is
wrong because the same memory location can be in the list twice, and
if the first one has a sunkaddr substituted, the stashed value for the
second one will be wrong (use-after-free).  PR 8154.

llvm-svn: 114104

It is possible, under specific circumstances involving ptrtoint ConstantExpr's, for LVI to end up trying to merge
a Constant into a ConstantRange.  Handle this conservatively for now, rather than asserting.  The testcase is
more complex that I would like, but the manifestation of the problem is sensitive to iteration orders and the state of the
LVI cache, and I have not been able to reproduce it with manually constructed or simplified cases.

Fixes PR8162.

llvm-svn: 114103

(PICLDRB, et. al.) and PICSTR*

llvm-svn: 114098

to replace an instruction with itself.  Add a predicate to the simplifier to prevent this case.

llvm-svn: 114097

from the APFloat.

llvm-svn: 114096

llvm-svn: 114091

llvm-svn: 114077

This cleans up after the mess r108567 left in the CellSPU backend.
ORCvt-instruction were used to reinterpret registers, and the ORs were then
removed by isMoveInstr(). This patch now removes 350 instrucions of format:
	or $3, $3, $3
(from the 52 testcases in CodeGen/CellSPU). One case of a nonexistant or is
checked for.

Some moves of the form 'ori $., $., 0' and 'ai $., $., 0' still remain.

llvm-svn: 114074

Cameron Esfahani, tweaked to use array_lengthof.

llvm-svn: 114073

with attribute warn_unused_result" here - suppress the warning harder.

llvm-svn: 114072

used for anything.

llvm-svn: 114067

instead of using default predicates on the expanded instructions.

llvm-svn: 114066

unnecessary dtor for MCOperand.

llvm-svn: 114064

llvm-svn: 114048

register allocation to VLDMD and VSTMD respectively.  This avoids using the
dregpair operand modifier.

llvm-svn: 114047

be possible to implement this very carefully to allow a lock-free implementation while still
avoiding illegal interleavings, but I haven't been able to figure one out.

llvm-svn: 114046

great deal because we don't have to worry about maintaining SSA form.

Unconditionally copy back to dupli when the register is live out of the split
range, even if the live-out value was defined outside the range. Skipping the
back-copy only makes sense when the live range is going to spill outside the
split range, and we don't know that it will. Besides, this was a hack to avoid
SSA update issues.

Clear up some confusion about the end point of a half-open LiveRange. Methinks
LiveRanges need to be closed so both start and end are included in the range.
The low bits of a SlotIndex are symbolic, so a half-open range doesn't really
make sense. This would be a pervasive change, though.

llvm-svn: 114043

llvm-svn: 114037

Since PassRegistry is currently a shared global object, it needs locking.  While it might intuitively seem
that all the setup of this class currently happens at static initialization time, this misses the fact
that some later events can cause mutation of the PassRegistrationListeners list, and thus cause race issues.

llvm-svn: 114036

llvm-svn: 114032

llvm-svn: 114030