- Nov 29, 2012
-
-
Nadav Rotem authored
llvm-svn: 168927
-
Meador Inge authored
This patch migrates the puts optimizations from the simplify-libcalls pass into the instcombine library call simplifier. All the simplifiers from simplify-libcalls have now been migrated to instcombine. Yay! Just a few other bits to migrate (prototype attribute inference and a few statistics) and simplify-libcalls can finally be put to rest. llvm-svn: 168925
-
Jim Grosbach authored
MachOObjectFile owns a MachOObj, but never frees it. Both MachOObjectFile and MachOObj want to own the MemoryBuffer, though, so we have to be careful and give them each one of their own. Thanks to Greg Clayton, Eric Christopher and Michael Spencer for helping figure out what's going wrong here. rdar://12561773 llvm-svn: 168923
-
Benjamin Kramer authored
Follow up to 168711: It's safe to base this analysis on the found compare, just return the value for the right predicate. Thanks to Andy for catching this. llvm-svn: 168921
-
Andrew Trick authored
llvm-svn: 168914
-
Alexey Samsonov authored
[ASan] Simplify check added in r168861. Bail out from module pass early if the module is blacklisted. llvm-svn: 168913
-
Matt Beaumont-Gay authored
llvm-svn: 168911
-
Alexey Samsonov authored
llvm-svn: 168910
-
Pedro Artigas authored
start up and clean up module passes, now that ASAN and TSAN are fixed the tests pass llvm-svn: 168905
-
Meador Inge authored
This patch migrates the fputs optimizations from the simplify-libcalls pass into the instcombine library call simplifier. llvm-svn: 168893
-
Meador Inge authored
This patch migrates the fwrite optimizations from the simplify-libcalls pass into the instcombine library call simplifier. llvm-svn: 168892
-
Meador Inge authored
This patch migrates the fprintf optimizations from the simplify-libcalls pass into the instcombine library call simplifier. llvm-svn: 168891
-
Evgeniy Stepanov authored
Handle insertelement, extractelement, shufflevector. llvm-svn: 168889
-
Evgeniy Stepanov authored
The old version failed on a 3-arg instruction with (-1, 0, 0) shadows (it would pick the 3rd operand origin irrespective of its shadow). The new version always picks the origin of the rightmost poisoned operand. llvm-svn: 168887
-
Silviu Baranga authored
llvm-svn: 168886
-
Benjamin Kramer authored
This was found by MSVC10's STL debug mode on a test from the test suite. Sadly std::is_heap isn't standard so there is no way to assert this without writing our own heap verify, which looks like overkill to me. llvm-svn: 168885
-
Evgeniy Stepanov authored
llvm-svn: 168884
-
Justin Holewinski authored
If we need to split the operand of a VSELECT, it must be the mask operand. We split the entire VSELECT operand with EXTRACT_SUBVECTOR. llvm-svn: 168883
-
Justin Holewinski authored
Allow targets to prefer TypeSplitVector over TypePromoteInteger when computing the legalization method for vectors For some targets, it is desirable to prefer scalarizing <N x i1> instead of promoting to a larger legal type, such as <N x i32>. llvm-svn: 168882
-
Evgeniy Stepanov authored
This is a special case of signed relational comparison where result only depends on the sign of x. llvm-svn: 168881
-
Evgeniy Stepanov authored
This change ensures that shadow memory accesses have the same alignment as corresponding app memory accesses. llvm-svn: 168880
-
Evgeniy Stepanov authored
Rewrite getOriginPtr in a way that lets subsequent optimizations factor out the common part of Shadow and Origin address calculation. Improves perf by up to 5%. llvm-svn: 168879
-
Evgeniy Stepanov authored
llvm-svn: 168878
-
Evgeniy Stepanov authored
This was already done for memmove, where it is required for correctness. This change improves performance by avoiding copyingthe same memory twice. Also, the library functions are given __msan_ prefix to prevent instcombine pass from converting them back to intrinsics. llvm-svn: 168876
-
Elena Demikhovsky authored
The logic was not changed, only names. llvm-svn: 168875
-
Evgeniy Stepanov authored
llvm-svn: 168873
-
Evgeniy Stepanov authored
Compiler pass only. llvm-svn: 168866
-
Kostya Serebryany authored
[asan/tsan] initialize the asan/tsan callbacks in runOnFunction as opposed to doInitialization. This is required to allow the upcoming changes in PassManager behavior llvm-svn: 168864
-
Kostya Serebryany authored
llvm-svn: 168861
-
Preston Briggs authored
llvm-svn: 168854
-
Jakob Stoklund Olesen authored
This saves a bit of memory. llvm-svn: 168852
-
Shuxin Yang authored
Approved by: Eli and Michael. llvm-svn: 168848
-
Jakob Stoklund Olesen authored
This could cause miscompilations in targets where sub-register composition is not always idempotent (ARM). <rdar://problem/12758887> llvm-svn: 168837
-
Nick Lewycky authored
Also a couple not-user-visible changes; using empty() instead of size(), and make inSection() not insert NULL Regex*'s into StringMap when doing a lookup. llvm-svn: 168833
-
Nadav Rotem authored
llvm-svn: 168832
-
Bill Wendling authored
delete those as well. llvm-svn: 168829
-
- Nov 28, 2012
-
-
Jyotsna Verma authored
llvm-svn: 168810
-
Benjamin Kramer authored
Fixes 14337. llvm-svn: 168809
-
Jakob Stoklund Olesen authored
No functional change, just moved header files. Targets can inject custom passes between register allocation and rewriting. This makes it possible to tweak the register allocation before rewriting, using the full global interference checking available from LiveRegMatrix. llvm-svn: 168806
-
Eli Bendersky authored
appropriate unit tests. This change in itself is not expected to affect any functionality at this point, but it will serve as a stepping stone to improve FileCheck's variable matching capabilities. Luckily, our regex implementation already supports backreferences, although a bit of hacking is required to enable it. It supports both Basic Regular Expressions (BREs) and Extended Regular Expressions (EREs), without supporting backrefs for EREs, following POSIX strictly in this respect. And EREs is what we actually use (rightly). This is contrary to many implementations (including the default on Linux) of POSIX regexes, that do allow backrefs in EREs. Adding backref support to our EREs is a very simple change in the regcomp parsing code. I fail to think of significant cases where it would clash with existing things, and can bring more versatility to the regexes we write. There's always the danger of a backref in a specially crafted regex causing exponential matching times, but since we mainly use them for testing purposes I don't think it's a big problem. [it can also be placed behind a flag specific to FileCheck, if needed]. For more details, see: * http://lists.cs.uiuc.edu/pipermail/llvmdev/2012-November/055840.html * http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20121126/156878.html llvm-svn: 168802
-