- Nov 30, 2012
-
-
Douglas Gregor authored
building module 'Foo' imported from..." notes (the same we we provide "In file included from..." notes) in the diagnostic, so that we know how this module got included in the first place. This is part of <rdar://problem/12696425>. llvm-svn: 169021
-
Chad Rosier authored
llvm-svn: 169020
-
Dmitry Vyukov authored
llvm-svn: 169019
-
Jyotsna Verma authored
llvm-svn: 169018
-
Dmitry Vyukov authored
tsan: add __libc_memalign interceptor (used by dynamic loader to allocate tls for dlopen'ed modules) llvm-svn: 169017
-
Nadav Rotem authored
Remove the use of LPPassManager. We can remove LPM because we dont need to run any additional loop passes on the new vector loop. llvm-svn: 169016
-
Dmitry Vyukov authored
llvm-svn: 169015
-
Eli Bendersky authored
llvm-svn: 169002
-
Eli Bendersky authored
instead of 1 or true (?!) llvm-svn: 169001
-
Manuel Klimek authored
Patch by Edwin Vane. llvm-svn: 169000
-
NAKAMURA Takumi authored
FIXME: Please add another RUN line if you would like to check also on ppc64. llvm-svn: 168999
-
Adhemerval Zanella authored
instruction (vmaddfp) to conform with IEEE to ensure the sign of a zero result when resulting product is -0.0. The -0.0 vector addend to vmaddfp is generated by a creating a vector with full bits sets and then shifting each elements by 31-bits to the left, resulting in a vector of 0x80000000 (or -0.0 as float). The 'buildvec_canonicalize.ll' was adjusted to reflect this change and the 'vec_mul.ll' was complemented with the float vector multiplication test. llvm-svn: 168998
-
Evgeniy Stepanov authored
llvm-svn: 168997
-
Chandler Carruth authored
Rationale: 1) This was the name in the comment block. ;] 2) It matches Clang's __has_feature naming convention. 3) It matches other compiler-feature-test conventions. Sorry for the noise. =] I've also switch the comment block to use a \brief tag and not duplicate the name. llvm-svn: 168996
-
Kostya Serebryany authored
llvm-svn: 168995
-
Chandler Carruth authored
llvm-svn: 168994
-
Chandler Carruth authored
references from whether it supports an R-value reference *this. No version of GCC today supports the latter, which breaks GCC C++11 compiles of LLVM and Clang now. Also add doxygen comments clarifying what's going on here, and update the usage in Optional. I'll update the usages in Clang next. llvm-svn: 168993
-
Kostya Serebryany authored
llvm-svn: 168992
-
Patrik Hagglund authored
For example, don't allow empty strings to be passed to getInt. Move asserts inside parseSpecifier. (One day we may want to pass parse error messages to the user - from LLParser - instead of using asserts, but keep the code simple until then. There have been an attempt to do this. See r142288, which got reverted, and r142605.) llvm-svn: 168991
-
Kostya Serebryany authored
llvm-svn: 168990
-
Chandler Carruth authored
We're iterating over a non-deterministically ordered container looking for two saturating flags. To do this correctly, we have to saturate both, and only stop looping if both saturate to their final value. Otherwise, which flag we see first changes the result. This is also a micro-optimization of the previous version as now we don't go into the (possibly expensive) test logic once the first violation of either constraint is detected. llvm-svn: 168989
-
Chandler Carruth authored
functionality changed. Evan's commit r168970 moved the code that the primary comment in this function referred to to the other end of the function without moving the comment, and there has been a steady creep of "boolean" logic in it that is simpler if handled via early exit. That way each special case can have its own comments. I've also made the variable name a bit more explanatory than "AllFit". This is in preparation to fix the non-deterministic output of this function. llvm-svn: 168988
-
Dmitry Vyukov authored
llvm-svn: 168987
-
Eric Christopher authored
llvm-svn: 168986
-
Dmitry Vyukov authored
llvm-svn: 168985
-
Eli Friedman authored
the beginning and end of the range are in different macro arguments. PR14399. llvm-svn: 168984
-
Jyotsna Verma authored
llvm-svn: 168983
-
Richard Smith authored
llvm-svn: 168977
-
Jyotsna Verma authored
addressing mode. llvm-svn: 168976
-
Meador Inge authored
The simplify-libcalls pass maintained a statistic to count the number of library calls that have been simplified. Now that library call simplification is being carried out in instcombine the statistic should be moved to there. llvm-svn: 168975
-
Chandler Carruth authored
depends on the IR infrastructure, there is no sense in it being off in Support land. This is in preparation to start working to expand InstVisitor into more special-purpose visitors that are still generic and can be re-used across different passes. The expansion will go into the Analylis tree though as nothing in VMCore needs it. llvm-svn: 168972
-
Evan Cheng authored
the tables cannot fit in registers (i.e. bitmap), do not emit the table if it's using an illegal type. rdar://12779436 llvm-svn: 168970
-
Quentin Colombet authored
llvm-svn: 168968
-
Jordan Rose authored
If 'x' is a temporary, x.getAs<Foo>() may not be safe if the result is supposed to persist (if its address is stored somewhere). Since getAs() can return a null value, the result is almost always stored into a variable, which of course is not safe when the original value dies. This has caused several bugs with GCC's "Temporaries May Vanish Sooner Than You Expect" optimization; in C++11 builds, at least, we'll be able to catch these problems now. I would suggest applying these to other getAs() and get*As() methods (castAs is "better" because sometimes the result is used directly, which means the temporary will still be live), but these two have both caused trouble in the analyzer in the past. llvm-svn: 168967
-
Tobias Grosser authored
generation. We don't use the exact same way to build loop body for GPGPU codegen as openmp codegen and other transformations do currently, in which cases 'createLoop' function is called recursively. GPGPU codegen may fail due to improper restore of ValueMap and ClastVars . Contributed by: Yabin Hu <yabin.hwu@gmail.com> llvm-svn: 168966
-
Preston Briggs authored
more information for dependences between instructions that don't share a common loop. Updated the test results appropriately. llvm-svn: 168965
-
Tobias Grosser authored
Contributed-by:
Yabin Hu <yabin.hwu@gmail.com> llvm-svn: 168964
-
Jordan Rose authored
This expands to '&', and is intended to be used when an /optional/ rvalue override is available. Before: void foo() const { ... } After: void foo() const LLVM_LVALUE_FUNCTION { ... } void foo() && { ... } This is used to allow moving the contents of an Optional. llvm-svn: 168963
-
Douglas Gregor authored
llvm-svn: 168962
-
Douglas Gregor authored
import of that module elsewhere, don't try to build the module again: it won't work, and the experience is quite dreadful. We track this information somewhat globally, shared among all of the related CompilerInvocations used to build modules on-the-fly, so that a particular Clang instance will only try to build a given module once. Fixes <rdar://problem/12552849>. llvm-svn: 168961
-