- Feb 05, 2012
-
-
Duncan Sands authored
compiling sqlite3, by only doing dom queries after the cheap check rather than interleaved with it. llvm-svn: 149836
-
David Blaikie authored
llvm-svn: 149813
-
NAKAMURA Takumi authored
llvm-svn: 149810
-
Chris Lattner authored
but with a critical fix to the SelectionDAG code that optimizes copies from strings into immediate stores: the previous code was stopping reading string data at the first nul. Address this by adding a new argument to llvm::getConstantStringInfo, preserving the behavior before the patch. llvm-svn: 149800
-
- Feb 04, 2012
-
-
Hal Finkel authored
By default, boost the chain depth contribution of loads and stores. This will allow a load/store pair to vectorize even when it would not otherwise be long enough to satisfy the chain depth requirement. llvm-svn: 149761
-
- Feb 03, 2012
-
-
Jim Grosbach authored
llvm-svn: 149650
-
Jim Grosbach authored
llvm-svn: 149649
-
Jim Grosbach authored
More targetted fix replacing d0e277d272d517ca1cda368267d199f0da7cad95. llvm-svn: 149648
-
Jim Grosbach authored
This reverts commit d0e277d272d517ca1cda368267d199f0da7cad95. llvm-svn: 149647
-
- Feb 02, 2012
-
-
Benjamin Kramer authored
Also silences warnings about bodyless for loops. llvm-svn: 149612
-
Hal Finkel authored
As suggested by Nick Lewycky, the tree traversal queues have been changed to SmallVectors and the associated loops have been rotated. Also, an 80-col violation was fixed. llvm-svn: 149607
-
Hal Finkel authored
Long basic blocks with many candidate pairs (such as in the SHA implementation in Perl 5.14; thanks to Roman Divacky for the example) used to take an unacceptably-long time to compile. Instead, break long blocks into groups so that no group has too many candidate pairs. llvm-svn: 149595
-
- Feb 01, 2012
-
-
Stepan Dyatkovskiy authored
The purpose of refactoring is to hide operand roles from SwitchInst user (programmer). If you want to play with operands directly, probably you will need lower level methods than SwitchInst ones (TerminatorInst or may be User). After this patch we can reorganize SwitchInst operands and successors as we want. What was done: 1. Changed semantics of index inside the getCaseValue method: getCaseValue(0) means "get first case", not a condition. Use getCondition() if you want to resolve the condition. I propose don't mix SwitchInst case indexing with low level indexing (TI successors indexing, User's operands indexing), since it may be dangerous. 2. By the same reason findCaseValue(ConstantInt*) returns actual number of case value. 0 means first case, not default. If there is no case with given value, ErrorIndex will returned. 3. Added getCaseSuccessor method. I propose to avoid usage of TerminatorInst::getSuccessor if you want to resolve case successor BB. Use getCaseSuccessor instead, since internal SwitchInst organization of operands/successors is hidden and may be changed in any moment. 4. Added resolveSuccessorIndex and resolveCaseIndex. The main purpose of these methods is to see how case successors are really mapped in TerminatorInst. 4.1 "resolveSuccessorIndex" was created if you need to level down from SwitchInst to TerminatorInst. It returns TerminatorInst's successor index for given case successor. 4.2 "resolveCaseIndex" converts low level successors index to case index that curresponds to the given successor. Note: There are also related compatability fix patches for dragonegg, klee, llvm-gcc-4.0, llvm-gcc-4.2, safecode, clang. llvm-svn: 149481
-
NAKAMURA Takumi authored
llvm-svn: 149475
-
Hal Finkel authored
llvm-svn: 149472
-
Argyrios Kyrtzidis authored
These are: r149348 r149351 r149352 r149354 r149356 r149357 r149361 r149362 r149364 r149365 llvm-svn: 149470
-
Hal Finkel authored
This is the initial checkin of the basic-block autovectorization pass along with some supporting vectorization infrastructure. Special thanks to everyone who helped review this code over the last several months (especially Tobias Grosser). llvm-svn: 149468
-
Jim Grosbach authored
Changing arguments from being passed as fixed to varargs is unsafe, as the ABI may require they be handled differently (stack vs. register, for example). Remove two tests which rely on the bitcast being folded into the direct call, which is exactly the transformation that's unsafe. llvm-svn: 149457
-
Lenny Maiorani authored
Make the EarlyCSE optimizer not use recursion to do a depth first iteration. llvm-svn: 149445
-
- Jan 31, 2012
-
-
Bill Wendling authored
vector. This potentially saves a resizing. llvm-svn: 149369
-
Bill Wendling authored
llvm-svn: 149368
-
Chris Lattner authored
ConstantDataArray::getString instead. llvm-svn: 149365
-
Chris Lattner authored
eliminate the last uses of GetConstantStringInfo from this file, I didn't realize I was that close... llvm-svn: 149354
-
Chris Lattner authored
dramatically more efficient than GetConstantStringInfo. llvm-svn: 149352
-
Chris Lattner authored
llvm-svn: 149340
-
Bill Wendling authored
llvm-svn: 149328
-
Bill Wendling authored
llvm-svn: 149323
-
Bill Wendling authored
llvm-svn: 149322
-
Bill Wendling authored
llvm-svn: 149318
-
Bill Wendling authored
llvm-svn: 149317
-
Bill Wendling authored
llvm-svn: 149316
-
Bill Wendling authored
The eh.selector and eh.resume intrinsics aren't used anymore. Get rid of some calls to them. llvm-svn: 149314
-
Bill Wendling authored
llvm-svn: 149312
-
Bill Wendling authored
llvm-svn: 149307
-
Kostya Serebryany authored
llvm-svn: 149300
-
- Jan 30, 2012
-
-
Chad Rosier authored
llvm-svn: 149289
-
Chad Rosier authored
llvm-svn: 149275
-
Alexander Potapenko authored
Fix compilation of ASan tests on OS X Lion (see http://code.google.com/p/address-sanitizer/issues/detail?id=32) The redzones emitted by AddressSanitizer for CFString instances confuse the linker and are of little use, so we shouldn't add them. llvm-svn: 149243
-
- Jan 29, 2012
-
-
Nick Lewycky authored
llvm-svn: 149185
-
- Jan 28, 2012
-
-
Kostya Serebryany authored
llvm-svn: 149172
-