| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
| |
the fast unwinder for malloc/free. Linux-x86-only for now.
llvm-svn: 172397
|
| |
|
|
|
|
|
| |
While reviewing r172303 I noticed that I wasn't sure whether we still
format those correctly and didn't see any tests.
llvm-svn: 172396
|
| |
|
|
|
|
| |
threads can access non yet allocated shadow)
llvm-svn: 172395
|
| |
|
|
|
|
| |
weird false positives on googletest)
llvm-svn: 172394
|
| |
|
|
| |
llvm-svn: 172393
|
| |
|
|
| |
llvm-svn: 172392
|
| |
|
|
| |
llvm-svn: 172391
|
| |
|
|
| |
llvm-svn: 172390
|
| |
|
|
| |
llvm-svn: 172389
|
| |
|
|
|
|
|
|
| |
1. Increase size classes from 32k to 128k
2. Use lock-free stack in central cache
3. Use blocking mutex when allocate new memory with mmap
llvm-svn: 172388
|
| |
|
|
| |
llvm-svn: 172387
|
| |
|
|
| |
llvm-svn: 172386
|
| |
|
|
| |
llvm-svn: 172385
|
| |
|
|
|
|
|
| |
on redeclarations, since that makes us pick wrong prior declarations under
some circumstances.
llvm-svn: 172384
|
| |
|
|
| |
llvm-svn: 172383
|
| |
|
|
|
|
|
|
|
|
|
| |
1) Supported by Clang, and
2) Supported by GCC, and
3) Documented in GCC's manual.
g++ allows its C++11-style attributes to appertain only to the entity being
declared, and never to a type (even for a type attribute), so we do the same.
llvm-svn: 172382
|
| |
|
|
| |
llvm-svn: 172381
|
| |
|
|
| |
llvm-svn: 172380
|
| |
|
|
|
|
| |
than 2 arguments.
llvm-svn: 172379
|
| |
|
|
|
|
| |
needing to specify everything twice. No functional change intended
llvm-svn: 172378
|
| |
|
|
|
|
|
|
| |
They work fine, but this fifth use of colons (after labels, in ?:,
in initalizer lists in constructors, in objc method expressions, and in
bitfields) wasn't covered by tests yet.
llvm-svn: 172377
|
| |
|
|
|
|
| |
we know whether it is static.
llvm-svn: 172376
|
| |
|
|
| |
llvm-svn: 172375
|
| |
|
|
| |
llvm-svn: 172374
|
| |
|
|
| |
llvm-svn: 172373
|
| |
|
|
|
|
| |
callers, removing unneeded const_cast
llvm-svn: 172372
|
| |
|
|
|
|
| |
use doxygen). Still some work to do though.
llvm-svn: 172371
|
| |
|
|
| |
llvm-svn: 172370
|
| |
|
|
| |
llvm-svn: 172369
|
| |
|
|
|
|
|
|
| |
2x blocks each assigned a value via a phi-node causing each to depend on the other.
A test case is provided as well.
llvm-svn: 172368
|
| |
|
|
| |
llvm-svn: 172367
|
| |
|
|
|
|
| |
Patch contributed by Andrew Turner.
llvm-svn: 172366
|
| |
|
|
|
|
| |
Patch contributed by Andrew Turner.
llvm-svn: 172365
|
| |
|
|
| |
llvm-svn: 172364
|
| |
|
|
|
|
| |
cache result of Size/OffsetVisitor to speedup analysis of PHI nodes
llvm-svn: 172363
|
| |
|
|
| |
llvm-svn: 172362
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
clang-format should not change whether or not there is a line break
before a line comment as this strongly influences the percieved binding.
User input: void f(int a,
// b is awesome
int b);
void g(int a, // a is awesome
int b);
Before: void f(int a, // b is awesome
int b);
void g(int a, // a is awesome
int b);
After: <unchanged from input>
llvm-svn: 172361
|
| |
|
|
| |
llvm-svn: 172360
|
| |
|
|
| |
llvm-svn: 172359
|
| |
|
|
| |
llvm-svn: 172358
|
| |
|
|
| |
llvm-svn: 172357
|
| |
|
|
| |
llvm-svn: 172356
|
| |
|
|
|
|
|
|
|
|
|
| |
Note that I don't know whether we should put {} on a single line in this
case, but it is probably a theoretical issue as in practice such
structs, classes or unions won't be empty.
Before: union A {}
a;
After: union A {} a;
llvm-svn: 172355
|
| |
|
|
|
|
|
|
|
|
| |
flag information down from the Clang driver into the Gold linker plugin
for LTO. This allows specifying -march on the linker commandline and
should hopefully have it pass all the way through to the LTO optimizer.
Fixes PR14697.
llvm-svn: 172354
|
| |
|
|
|
|
|
| |
Those can occur when something between the sextload and the store is on the same
chain and blocks isel. Fixes PR14887.
llvm-svn: 172353
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In ArrayRef<T>(X), X should not be temporary value. It could be rewritten more redundantly;
llvm::Type *XTy = X->getType();
ArrayRef<llvm::Type *> Ty(XTy);
llvm::Value *Callee = CGF.CGM.getIntrinsic(IntrinsicID, Ty);
Since it is safe if both XTy and Ty are temporary value in one statement, it could be shorten;
llvm::Value *Callee = CGF.CGM.getIntrinsic(IntrinsicID, ArrayRef<llvm::Type*>(X->getType()));
ArrayRef<T> has an implicit constructor to create uni-entry of T;
llvm::Value *Callee = CGF.CGM.getIntrinsic(IntrinsicID, X->getType());
MSVC-generated clang.exe crashed.
llvm-svn: 172352
|
| |
|
|
|
|
|
|
|
|
| |
I am not aware of a case where that would be wrong. The specific case I
am fixing are function parameters wrapped in parenthesis (e.g. in
macros).
Before: function(a,(b));
After: function(a, (b));
llvm-svn: 172351
|
| |
|
|
|
|
| |
Before: #include <a - a>
After: #include <a-a>
llvm-svn: 172350
|
| |
|
|
|
|
|
|
|
| |
A ")" before any of "=", "{" or ";" won't be a cast. This fixes issues
with the formatting of unnamed parameters.
Before: void f(int *){}
After: void f(int *) {}
llvm-svn: 172349
|
| |
|
|
|
|
| |
and i16).
llvm-svn: 172348
|