- Jan 25, 2013
-
-
Bill Wendling authored
llvm-svn: 173495
-
Richard Osborne authored
llvm-svn: 173494
-
Richard Osborne authored
The order in which operands appear in the encoded instruction is different to order in which they appear in assembly. This changes the XCore backend to use the instruction encoding order. llvm-svn: 173493
-
Eli Bendersky authored
politely report it instead of running into llvm_unreachable. Also patch llvm-dwarfdump to actually check whether the file it's attempting to dump is a valid object file. llvm-svn: 173489
-
David Blaikie authored
llvm-svn: 173487
-
Hal Finkel authored
Suggested by Sean Silva. llvm-svn: 173481
-
Eli Bendersky authored
Flags for dumping specific DWARF sections added in lib/DebugInfo and llvm-dwarfdump. llvm-svn: 173480
-
Richard Osborne authored
llvm-svn: 173479
-
Michael Gottesman authored
llvm-svn: 173478
-
Richard Osborne authored
With this change the operands order matches the order in which the operands are encoded in the instruction. llvm-svn: 173477
-
Richard Osborne authored
llvm-svn: 173476
-
Benjamin Kramer authored
llvm-svn: 173475
-
Pedro Artigas authored
created InternalizePass (useful for pass reuse) llvm-svn: 173474
-
Michael Gottesman authored
custom git script called git-svnup which handles all of the work of using the git-mirrors/keeping the git-svn numbers in sync. llvm-svn: 173472
-
Nadav Rotem authored
llvm-svn: 173471
-
-
Nadav Rotem authored
llvm-svn: 173467
-
Eli Bendersky authored
llvm-svn: 173460
-
Benjamin Kramer authored
Fixes PR15054. llvm-svn: 173459
-
Reid Kleckner authored
This warning fires on: Operator::~Operator() { llvm_unreachable("should never destroy an Operator"); } That seems like a false positive. I don't see any good way to silence the warning here, so I'm disabling it. llvm-svn: 173455
-
Reid Kleckner authored
llvm-svn: 173454
-
Evgeniy Stepanov authored
llvm-svn: 173453
-
Evgeniy Stepanov authored
Only for integers, pointers, and vectors of those. No floats. Instrumentation seems very heavy, and may need to be replaced with some approximation in the future. llvm-svn: 173452
-
Preston Gurd authored
with an initial number of elements, instead of DenseMap, which has zero initial elements, in order to avoid the copying of elements when the size changes and to avoid allocating space every time LegalizeTypes is run. This patch will not affect the memory footprint, because DenseMap will increase the element size to 64 when the first element is added. Patch by Wan Xiaofei. llvm-svn: 173448
-
Hal Finkel authored
Uses the new !add TableGen operator to do more cleanup of the PPC register definitions. llvm-svn: 173446
-
Hal Finkel authored
This adds an !add(a, b) operator to tablegen; this will be used to cleanup the PPC register definitions. llvm-svn: 173445
-
Silviu Baranga authored
Fixed the condition codes for the atomic64 min/umin code generation on ARM. If the sutraction of the higher 32 bit parts gives a 0 result, we need to do the store operation. llvm-svn: 173437
-
Bill Wendling authored
llvm-svn: 173434
-
Andrew Trick authored
llvm-svn: 173433
-
Andrew Trick authored
llvm-svn: 173432
-
Andrew Trick authored
llvm-svn: 173431
-
Andrew Trick authored
This fixes DAG subtree analysis at the boundary. llvm-svn: 173427
-
Andrew Trick authored
Maintain separate per-node and per-tree book-keeping. Track all instructions above a DAG node including nested subtrees. Seperately track instructions within a subtree. Record subtree parents. llvm-svn: 173426
-
Andrew Trick authored
Allow the strategy to select SchedDFS. Allow the results of SchedDFS to affect initialization of the scheduler state. llvm-svn: 173425
-
Andrew Trick authored
llvm-svn: 173424
-
Andrew Trick authored
llvm-svn: 173423
-
NAKAMURA Takumi authored
llvm-svn: 173421
-
Andrew Trick authored
This is mostly refactoring, along with adding an instruction count within the subtrees and ensuring we only look at data edges. llvm-svn: 173420
-
Chandler Carruth authored
loops over instructions in the basic block or the use-def list of the value, neither of which are really efficient when repeatedly querying about values in the same basic block. What's more, we already know that the CondBB is small, and so we can do a much more efficient test by counting the uses in CondBB, and seeing if those account for all of the uses. Finally, we shouldn't blanket fail on any such instruction, instead we should conservatively assume that those instructions are part of the cost. Note that this actually fixes a bug in the pass because isUsedInBasicBlock has a really terrible bug in it. I'll fix that in my next commit, but the fix for it would make this code suddenly take the compile time hit I thought it already was taking, so I wanted to go ahead and migrate this code to a faster & better pattern. The bug in isUsedInBasicBlock was also causing other tests to test the wrong thing entirely: for example we weren't actually disabling speculation for floating point operations as intended (and tested), but the test passed because we failed to speculate them due to the isUsedInBasicBlock failure. llvm-svn: 173417
-
Andrew Trick authored
interface and allow other strategies to select it. llvm-svn: 173413
-