| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
declaration of class metadata when they are defined later.
llvm-svn: 152500
|
| |
|
|
|
|
| |
// rdar://11024543
llvm-svn: 152496
|
| |
|
|
|
|
| |
No functionality change.
llvm-svn: 152494
|
| |
|
|
| |
llvm-svn: 152493
|
| |
|
|
|
|
|
|
| |
track whether the referenced declaration comes from an enclosing
local context. I'm amenable to suggestions about the exact meaning
of this bit.
llvm-svn: 152491
|
| |
|
|
|
|
|
|
| |
enum is scoped or not, which is not relevant here. Instead, phrase the loop in
the same terms that the standard uses, instead of this awkward set of
conditions that is *nearly* equal.
llvm-svn: 152489
|
| |
|
|
|
|
|
| |
please annotate it with a note explaining why this wrong-seeming behaviour is
correct.
llvm-svn: 152488
|
| |
|
|
|
|
| |
doing a copy. Fixes PR12139.
llvm-svn: 152485
|
| |
|
|
|
|
|
|
| |
should not impede creating a proper TypeLoc info for the decl-spec.
This improves our semantic error recovery.
llvm-svn: 152481
|
| |
|
|
|
|
|
|
|
|
|
| |
Before r151307 this part worked without compiler errors but now it only verifies
that our handling of irregular pragmas is broken compared to gcc, it has no
practical usefulness; it creates invalid structs that cannot be used for 'offsetof' testing.
If we later decide to handle irregular pragmas without compiler errors we can
put back this part.
llvm-svn: 152480
|
| |
|
|
|
|
|
|
| |
we correctly emit loads of BlockDeclRefExprs even when they
don't qualify as ODR-uses. I think I'm adequately convinced
that BlockDeclRefExpr can die.
llvm-svn: 152479
|
| |
|
|
| |
llvm-svn: 152478
|
| |
|
|
| |
llvm-svn: 152476
|
| |
|
|
| |
llvm-svn: 152475
|
| |
|
|
|
|
| |
constructors. Fixes PR12219.
llvm-svn: 152470
|
| |
|
|
| |
llvm-svn: 152469
|
| |
|
|
|
|
|
|
|
|
|
| |
doesn't understand. We registered
as aborted, but didn't treat such cases as sinks in the ExplodedGraph.
Along the way, add basic support for CXXCatchStmt, expanding the set of code we actually analyze (hopefully correctly).
Fixes: <rdar://problem/10892489>
llvm-svn: 152468
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- We do this when it is easy to determine that the backend will pass them on
the stack properly by itself.
Currently LLVM codegen is really bad in some cases with byval, for example, on
the test case here (which is derived from Sema code, which likes to pass
SourceLocations around)::
struct s47 { unsigned a; };
void f47(int,int,int,int,int,int,struct s47);
void test47(int a, struct s47 b) { f47(a, a, a, a, a, a, b); }
we used to emit code like this::
...
movl %esi, -8(%rbp)
movl -8(%rbp), %ecx
movl %ecx, (%rsp)
...
to handle moving the struct onto the stack, which is just appalling.
Now we generate::
movl %esi, (%rsp)
which seems better, no?
llvm-svn: 152462
|
| |
|
|
| |
llvm-svn: 152461
|
| |
|
|
|
|
| |
// rdar://11023563
llvm-svn: 152459
|
| |
|
|
|
|
| |
innermost type. Fixes PR12142.
llvm-svn: 152456
|
| |
|
|
|
|
|
|
| |
copy-construction, which Daniel Dunbar reports as giving a 0.75% speedup on
403.gcc/combine.c. The performance differences on my constexpr torture tests
are below the noise floor.
llvm-svn: 152455
|
| |
|
|
|
|
| |
ivars in the modern rewriter.
llvm-svn: 152451
|
| |
|
|
|
|
| |
annotations. Fixes <rdar://problem/10824732>.
llvm-svn: 152448
|
| |
|
|
|
|
| |
in Objective-C++.
llvm-svn: 152446
|
| |
|
|
|
|
|
|
|
|
| |
basic source character set in C++98. Add -Wc++98-compat diagnostics for same in
literals in C++11. Extend such support to cover string literals as well as
character literals, and mark N2170 as done.
This seems too minor to warrant a release note to me. Let me know if you disagree.
llvm-svn: 152444
|
| |
|
|
|
|
| |
actually happened.
llvm-svn: 152442
|
| |
|
|
| |
llvm-svn: 152441
|
| |
|
|
|
|
|
|
|
|
|
| |
We do not reanalyze a function, which has already been analyzed as an
inlined callee. As per PRELIMINARY testing, this gives over
50% run time reduction on some benchmarks without decreasing of the
number of bugs found.
Turning the mode on by default.
llvm-svn: 152440
|
| |
|
|
| |
llvm-svn: 152439
|
| |
|
|
|
|
|
|
| |
invalid ParmVarDecls.
Part of rdar://11007039.
llvm-svn: 152437
|
| |
|
|
|
|
|
| |
LLVM_READONLY.", getTypeInfo() is totally not READONLY, which I should have
probably noticed given that I made it so mere hours ago. Oops.
llvm-svn: 152434
|
| |
|
|
| |
llvm-svn: 152433
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When an error made a record member invalid, the record would stay as "isBeingDefined" and
not "completeDefinition". Even easily recoverable errors ended up propagating records in
such "beingDefined" state, for example:
struct A {
~A() const; // expected-error {{'const' qualifier is not allowed on a destructor}}
};
struct B : A {}; // A & B would stay as "not complete definition" and "being defined".
This weird state was impending lookups in the records and hitting assertion in the ASTWriter.
Part of rdar://11007039
llvm-svn: 152432
|
| |
|
|
| |
llvm-svn: 152431
|
| |
|
|
| |
llvm-svn: 152430
|
| |
|
|
| |
llvm-svn: 152429
|
| |
|
|
|
|
| |
LLVM_READONLY.
llvm-svn: 152428
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- The theory here is that we have these functions sprinkled in all over the
place. This should allow the optimizer to at least realize it can still do
load CSE across these calls.
- I blindly marked all instances as such, even though the optimizer can infer
this attribute in some instances (some of the inline ones) as that was easier
and also, when given the choice between thinking and not thinking, I prefer
the latter.
You might think this is mere frivolity, but actually this is good for a .7 -
1.1% speedup on 403.gcc/combine.c, JSC/Interpreter.cpp,
OGF/NSBezierPath-OAExtensions.m.
llvm-svn: 152426
|
| |
|
|
| |
llvm-svn: 152424
|
| |
|
|
|
|
|
| |
to forward class, and assigning to an 'id' type var, message
sends default to 'id'. // rdar"//10988847
llvm-svn: 152420
|
| |
|
|
|
|
|
|
|
| |
- getSourceRange().getBegin() is about as awesome a pattern as .copy().size().
I already killed the hot paths so this doesn't seem to impact performance on my
tests-of-the-day, but it is a much more sensible (and shorter) pattern.
llvm-svn: 152419
|
| |
|
|
|
|
| |
{CXXBaseSpecifier,Declarator,DeclSpec,TypeLoc,UnqualifiedId}::getLoc{Start,End}.
llvm-svn: 152418
|
| |
|
|
|
|
|
| |
- This cuts the # of getSourceRange calls by 60% on
OGF/NSBezierPath-OAExtensions.m.
llvm-svn: 152412
|
| |
|
|
|
|
|
|
| |
- getSourceRange() can be very expensive, we should try to avoid it if at all possible.
In conjunction with the previous commit I measured a ~2% speedup on 403.gcc/combine.c and a 3% speedup on OmniGroupFrameworks/NSBezierPath-OAExtensions.m.
llvm-svn: 152411
|
| |
|
|
|
|
|
|
| |
methods.
- There are probably a lot more of these worth adding, but these are a start at hitting some of the exprs for which getSourceRange().getBegin() is a poor substitute for getLocStart().
llvm-svn: 152410
|
| |
|
|
| |
llvm-svn: 152409
|
| |
|
|
|
|
| |
more obvious.
llvm-svn: 152408
|
| |
|
|
|
|
| |
long).
llvm-svn: 152404
|
| |
|
|
|
|
|
|
|
| |
This renames the -Wformat-non-standard flag to -Wformat-non-iso,
rewords the current warnings a bit (pointing out that a format string
is not supported by ISO C rather than being "non standard"),
and adds a warning about positional arguments.
llvm-svn: 152403
|