- Jun 03, 2013
-
-
Sebastian Pop authored
otherwise, use -polly-detect-scops-in-regions-without-loops to also detect scops in regions without loops llvm-svn: 183113
-
Daniel Jasper authored
These lines almost never aid readability. Before: void f() { int i; // some variable } After: void f() { int i; // some variable } llvm-svn: 183112
-
Vincent Lejeune authored
llvm-svn: 183111
-
Ashok Thirumurthi authored
Thanks to Daniel and valgrind. llvm-svn: 183110
-
Daniel Malea authored
llvm-svn: 183109
-
Vincent Lejeune authored
llvm-svn: 183108
-
Vincent Lejeune authored
llvm-svn: 183107
-
Vincent Lejeune authored
llvm-svn: 183106
-
Kostya Serebryany authored
llvm-svn: 183105
-
Kostya Serebryany authored
llvm-svn: 183104
-
Ahmed Bougacha authored
llvm-svn: 183103
-
Alexey Samsonov authored
llvm-svn: 183102
-
Manuel Klimek authored
This patch ensures that APValues are deallocated with the ASTContext by registering a deallocation function for APValues to the ASTContext. Original version of the patch by James Dennett. llvm-svn: 183101
-
Manuel Klimek authored
This is needed in clang so one can check if the object needs the destructor called after its memory was freed. This is useful when creating many APInt/APFloat objects with placement new, where the overhead of tracking the pointers for cleanup is significant. llvm-svn: 183100
-
Sergey Matveev authored
Objects allocated after a call to __lsan_disable() will be treated as live memory. Also add a ScopedDisabler. llvm-svn: 183099
-
Sergey Matveev authored
Address issue reported by Greg Fitzgerald. llvm-svn: 183098
-
Daniel Jasper authored
An oversight in this detection made clang-format unable to format the following nicely: void aaaaaaaaaaaaaaaaaaa<aaaaaaaaaaaaaaaaaaaaaaaaaaa, bbbbbbbbbbbbbbbbbbbbbbbbbb>( cccccccccccccccccccccccccccc); llvm-svn: 183097
-
Daniel Jasper authored
Before, clang-format would not find a solution for formatting: if ((aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa || bbbbbbbbbbbbbbbbbb) && // aaaaaaaaaaaaaaaa cccccc) { } llvm-svn: 183096
-
Richard Smith authored
which is lifetime-extended by a reference binding. An additional temporary is created for such a bitfield access (although we have no explicit AST representation for it). llvm-svn: 183095
-
Venkatraman Govindaraju authored
llvm-svn: 183094
-
Richard Smith authored
materialized temporary with the corresponding MaterializeTemporaryExpr. This is groundwork for providing C++11's guaranteed static initialization for global references bound to lifetime-extended temporaries (if the initialization is a constant expression). In passing, fix a couple of bugs where some evaluation failures didn't trigger diagnostics, and a rejects-valid where potential constant expression testing would assume that it knew the dynamic type of *this and would reject programs which relied on it being some derived type. llvm-svn: 183093
-
Richard Smith authored
has an initializer. llvm-svn: 183092
-
Rui Ueyama authored
llvm-svn: 183091
-
Venkatraman Govindaraju authored
using two instructions (sethi and store). llvm-svn: 183090
-
Richard Smith authored
lifetime-extending temporaries in reference bindings. llvm-svn: 183089
-
- Jun 02, 2013
-
-
Venkatraman Govindaraju authored
llvm-svn: 183088
-
Rui Ueyama authored
Reviewers: Bigcheese CC: llvm-commits Differential Revision: http://llvm-reviews.chandlerc.com/D905 llvm-svn: 183087
-
Jim Grosbach authored
llvm-svn: 183086
-
David Majnemer authored
clang would incorrectly not allow the following: int x = true ? (throw 1) : 2; The problem exists because we don't see beyond the parens. This, in turn, causes us to believe that we are choosing between void and int which we diagnose as an error. Instead, allow clang to see the 'throw' inside the parens. llvm-svn: 183085
-
David Majnemer authored
In some cases, clang applies the C++ rules for computing the range of a value when said value is an enum. Instead, apply C semantics when in C mode. llvm-svn: 183084
-
Venkatraman Govindaraju authored
llvm-svn: 183083
-
Richard Smith authored
PR12848: When emitting a local variable declared 'constexpr', always initialize it with a store or a memcpy, not by emitting the initializer expression. This is not required for correctness, but more closely aligns with people's expectations, and is cheap (since we've already evaluated the initializer). llvm-svn: 183082
-
Benjamin Kramer authored
llvm-svn: 183081
-
- Jun 01, 2013
-
-
Nick Lewycky authored
index greater than the size of the vector is invalid. The shuffle may be shrinking the size of the vector. Fixes a crash! Also drop the maximum recursion depth of the safety check for this optimization to five. llvm-svn: 183080
-
Venkatraman Govindaraju authored
llvm-svn: 183079
-
David Majnemer authored
llvm-svn: 183078
-
Daniel Jasper authored
Before: return a<b &&c> d; After: return a < b && c > d; llvm-svn: 183077
-
Benjamin Kramer authored
Also simplify code a bit while there. No functionality change. llvm-svn: 183076
-
Benjamin Kramer authored
No functionality change. llvm-svn: 183075
-
Benjamin Kramer authored
llvm-svn: 183074
-