| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
llvm-svn: 172367
|
| |
|
|
| |
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: 172357
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
llvm-svn: 172345
|
| |
|
|
|
|
| |
on theree targets, i686, amd64, win64.
llvm-svn: 172344
|
| |
|
|
|
|
| |
builtins-multiprecision.c.
llvm-svn: 172343
|
| |
|
|
| |
llvm-svn: 172342
|
| |
|
|
|
|
|
| |
We lower all of these intrinsics into a 2x chained usage of
uadd.with.overflow.
llvm-svn: 172341
|
| |
|
|
| |
llvm-svn: 172340
|
| |
|
|
|
|
|
|
|
|
| |
Before:
[color getRed: &r green: &g blue: &b alpha: &a];
Now:
[color getRed:&r green:&g blue:&b alpha:&a];
llvm-svn: 172337
|
| |
|
|
|
|
| |
happens to work already.
llvm-svn: 172335
|
| |
|
|
| |
llvm-svn: 172334
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Before:
if ((self = [super initWithContentRect:contentRect styleMask:
styleMask backing:NSBackingStoreBuffered defer:YES])) {
Now:
if ((self = [super initWithContentRect:contentRect styleMask:styleMask
backing:NSBackingStoreBuffered defer:YES])) {
llvm-svn: 172333
|
| |
|
|
|
|
| |
Comment is taken from the commit message of r151080, by Jean-Daniel Dupas
llvm-svn: 172332
|
| |
|
|
| |
llvm-svn: 172331
|
| |
|
|
|
|
| |
more than a minute.
llvm-svn: 172330
|
| |
|
|
| |
llvm-svn: 172326
|
| |
|
|
|
|
| |
brought into 'clang' namespace by clang/Basic/LLVM.h
llvm-svn: 172323
|
| |
|
|
| |
llvm-svn: 172321
|
| |
|
|
|
|
| |
other headers included before them.
llvm-svn: 172320
|
| |
|
|
| |
llvm-svn: 172317
|
| |
|
|
| |
llvm-svn: 172316
|
| |
|
|
| |
llvm-svn: 172314
|
| |
|
|
| |
llvm-svn: 172308
|
| |
|
|
|
|
|
|
| |
canBreakBefore() does not allow breaking after ':' for LT_ObjCMethodDecl lines,
so if Newline is true in addTokenToState() for ':' then LT_ObjCMethodDecl
cannot be set. No functionality change.
llvm-svn: 172307
|
| |
|
|
|
|
| |
The containing if checks for this already. No functionality change.
llvm-svn: 172306
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The testcase in pr14929 shows that this is extremely hard to do. If we choose
to apply the attribute, that causes the visibility of some decls to change and
that can happen really late (during codegen).
Current gcc warns and ignores the attribute in this testcase with a warning.
This suggest that the correct solution is to find a point in the compilation
where we can compute the visibility and
* assert it was never computed before
* reject any attempts to compute it again in the future (with warnings).
llvm-svn: 172305
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This follows the approach suggested by djasper in PR14911: When a '[' is
seen that's at the start of a line, follows a binary operator, or follows one
of : [ ( return throw, that '[' and its closing ']' are marked as
TT_ObjCMethodExpr and every ':' in that range that isn't part of a ternary
?: is marked as TT_ObjCMethodExpr as well.
Update the layout routines to not output spaces around ':' tokens that are
marked TT_ObjCMethodExpr, and only allow breaking after such tokens, not
before.
Before:
[self adjustButton : closeButton_ ofKind : NSWindowCloseButton];
Now:
[self adjustButton:closeButton_ ofKind:NSWindowCloseButton];
llvm-svn: 172304
|
| |
|
|
| |
llvm-svn: 172303
|
| |
|
|
| |
llvm-svn: 172302
|
| |
|
|
| |
llvm-svn: 172301
|
| |
|
|
| |
llvm-svn: 172295
|
| |
|
|
|
|
| |
Thanks Eli Friedman for noticing it.
llvm-svn: 172292
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
which a particular declaration resides. Use this information to
customize the "definition of 'blah' must be imported from another
module" diagnostic with the module the user actually has to
import. Additionally, recover by importing that module, so we don't
complain about other names in that module.
Still TODO: coming up with decent Fix-Its for these cases, and expand
this recovery approach for other name lookup failures.
llvm-svn: 172290
|
| |
|
|
| |
llvm-svn: 172289
|
| |
|
|
|
|
| |
an init list with multiple elements.
llvm-svn: 172285
|
| |
|
|
| |
llvm-svn: 172283
|
| |
|
|
|
|
|
|
|
|
|
| |
Previously, -Wunused-comparison ignored comparisons in both macro bodies and
macro arguments, but we would still emit a -Wunused-value warning for either.
Now we correctly emit -Wunused-comparison for expressions in macro arguments.
Also, add isMacroBodyExpansion to SourceManager, to go along with
isMacroArgExpansion.
llvm-svn: 172279
|
| |
|
|
|
|
|
| |
of their own (or are syntheszed), use prperty's comment.
for them. // rdar://12791315
llvm-svn: 172278
|
| |
|
|
|
|
| |
Fixes PR 14634 and <rdar://problem/12903080>.
llvm-svn: 172274
|
| |
|
|
|
|
|
| |
import incomplete definitions for RecordDecls and then
mark the resulting definition as complete.
llvm-svn: 172273
|
| |
|
|
| |
llvm-svn: 172272
|
| |
|
|
| |
llvm-svn: 172270
|