llvm/test/CodeGen/X86/pre-split4.ll, branch release_27http://llvm.orghttps://git.amat.us/llvm/atom/test/CodeGen/X86/pre-split4.ll?h=release_272009-09-08T23:54:48ZEliminate more uses of llvm-as and llvm-dis.2009-09-08T23:54:48ZDan Gohmangohman@apple.com2009-09-08T23:54:48Zurn:sha1:36a0947820fd4aa4b8a5fa26e3f079bdf572bc81
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@81290 91177308-0d34-0410-b5e6-96231b3b80d8
Split the Add, Sub, and Mul instruction opcodes into separate2009-06-04T22:49:04ZDan Gohmangohman@apple.com2009-06-04T22:49:04Zurn:sha1:ae3a0be92e33bc716722aa600983fc1535acb122
integer and floating-point opcodes, introducing
FAdd, FSub, and FMul.
For now, the AsmParser, BitcodeReader, and IRBuilder all preserve
backwards compatability, and the Core LLVM APIs preserve backwards
compatibility for IR producers. Most front-ends won't need to change
immediately.
This implements the first step of the plan outlined here:
http://nondot.org/sabre/LLVMNotes/IntegerOverflow.txt
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@72897 91177308-0d34-0410-b5e6-96231b3b80d8
Previously, RecursivelyDeleteDeadInstructions provided an option2009-05-02T18:29:22ZDan Gohmangohman@apple.com2009-05-02T18:29:22Zurn:sha1:afc36a9520971832dfbebc0333593bf5d3098296
of returning a list of pointers to Values that are deleted. This was
unsafe, because the pointers in the list are, by nature of what
RecursivelyDeleteDeadInstructions does, always dangling. Replace this
with a simple callback mechanism. This may eventually be removed if
all clients can reasonably be expected to use CallbackVH.
Use this to factor out the dead-phi-cycle-elimination code from LSR
utility function, and generalize it to use the
RecursivelyDeleteTriviallyDeadInstructions utility function.
This makes LSR more aggressive about eliminating dead PHI cycles;
adjust tests to either be less trivial or to simply expect fewer
instructions.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@70636 91177308-0d34-0410-b5e6-96231b3b80d8
Remove the "fast" cases for spill and restore point determination, as these were subtlely wrong in obscure cases. Patch the testcase2009-03-31T08:27:09ZOwen Andersonresistor@mac.com2009-03-31T08:27:09Zurn:sha1:696a1307ba5e98fe813d21cecb9dbfd72be8562c
to account for this change.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@68093 91177308-0d34-0410-b5e6-96231b3b80d8
If val# def is ~0U, meaning it's defined by a PHI, and it's previously split, spill before the barrier because it's impossible to determine if all the defs are spilled in the same spill slot.2008-10-25T00:52:41ZEvan Chengevan.cheng@apple.com2008-10-25T00:52:41Zurn:sha1:78dfef771b2552090be60bee404570c2a0b03bcb
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@58129 91177308-0d34-0410-b5e6-96231b3b80d8