| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
LP64. It fails with +Asserts for Win64.
llvm-svn: 163708
|
| |
|
|
| |
llvm-svn: 163701
|
| |
|
|
|
|
| |
to __SIZE_TYPE__.
llvm-svn: 163700
|
| |
|
|
|
|
|
|
| |
LLP64-incompatible tests.
I think some of them could be rewritten to fit also LLP64.
llvm-svn: 163699
|
| |
|
|
|
|
| |
%t.h might be touched by scanners as a hot file on Windows, to fail to remove %.h with single run.
llvm-svn: 163697
|
| |
|
|
| |
llvm-svn: 163696
|
| |
|
|
| |
llvm-svn: 163691
|
| |
|
|
|
|
|
|
| |
were not emitted.
Fixes <rdar://problem/12280665>.
llvm-svn: 163683
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for halting the propagation of uninitialized value tracking along
a path. Unlike __attribute__((noreturn)), this attribute (which
is used by clients of the static analyzer) can be used to annotate
functions that essentially never return, but in rare cares may be
allowed to return for (special) debugging purposes. This attribute
has been shown in reducing false positives in the static analyzer
by pruning false postives, and is equally applicable here.
Handling this attribute in the CFG itself is another option, but
this is not something all clients (e.g., possibly -Wunreachable-code)
would want to see.
Addresses <rdar://problem/12281583>.
llvm-svn: 163681
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
'Inputs' subdirectory.
The general desire has been to have essentially all of the non-test
input files live in such directories, with some exceptions for obvious
and common patterns like 'foo.c' using 'foo.h'.
This came up because our distributed test runner couldn't find some of
the headers, for example with stl.cpp.
No functionality changed, just shuffling around here.
llvm-svn: 163674
|
| |
|
|
| |
llvm-svn: 163673
|
| |
|
|
|
|
|
| |
parameter packs where the reference is not being expanded but the pack has
been. Previously, Clang would segfault in such cases.
llvm-svn: 163672
|
| |
|
|
|
|
|
|
|
|
| |
args where it should (implicit first arguments). FileCheck-ize a
test as well and update tests to take into account the object
pointer flag.
rdar://9797999
llvm-svn: 163668
|
| |
|
|
| |
llvm-svn: 163656
|
| |
|
|
|
|
| |
':' in its name. // rdar://8366823
llvm-svn: 163650
|
| |
|
|
|
|
|
|
|
|
|
| |
analysis registers a command, it becomes a "known" command for the lexer, since
it has an ID. Having this freedom of choice to register a command is a good
thing since BriefParser does not need this.
But the parser should still invoke the correct semantic analysis method
(actOnUnknownCommand) in this case.
llvm-svn: 163646
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
reinterpret_cast does not provide any of the usual type information that
static_cast or dynamic_cast provide -- only the new type. This can get us
in a situation where the dynamic type info for an object is actually a
superclass of the static type, which does not match what CodeGen does at all.
In these cases, just fall back to the static type as the best possible type
for devirtualization.
Should fix the crashes on our internal buildbot.
llvm-svn: 163644
|
| |
|
|
|
|
| |
on templates.
llvm-svn: 163642
|
| |
|
|
|
|
|
| |
name results in unintended selector name.
// rdar://12263549
llvm-svn: 163634
|
| |
|
|
| |
llvm-svn: 163620
|
| |
|
|
|
|
|
|
|
| |
Fixed by pointing the end location of the preprocessed entity for the #include
at the closing '>', instead of the start of '<'.
rdar://11113134
llvm-svn: 163588
|
| |
|
|
| |
llvm-svn: 163581
|
| |
|
|
|
|
|
|
|
|
|
| |
C++11 [expr.call]p1: ...If the selected function is non-virtual, or if the
id-expression in the class member access expression is a qualified-id,
that function is called. Otherwise, its final overrider in the dynamic type
of the object expression is called.
<rdar://problem/12255556>
llvm-svn: 163577
|
| |
|
|
|
|
|
| |
The one reported bug, which was exposed by stl inlining, is addressed in
r163558.
llvm-svn: 163574
|
| |
|
|
|
|
|
|
|
| |
depth.
We only want to count how many substantial functions we inlined. This
is an improvement to r163558.
llvm-svn: 163571
|
| |
|
|
|
|
| |
Patch by David Tweed, review by myself and John McCall.
llvm-svn: 163564
|
| |
|
|
|
|
| |
rdar://12257073
llvm-svn: 163563
|
| |
|
|
| |
llvm-svn: 163562
|
| |
|
|
|
|
|
|
| |
The option allows to always inline very small functions, whose size (in
number of basic blocks) is set using -analyzer-config
ipa-always-inline-size option.
llvm-svn: 163558
|
| |
|
|
|
|
|
|
|
|
|
|
| |
A couple of missing "RequireNonAbstractType" calls in conditional operator
handling. I looked for opportunities to tie this check in to all relevant
callers of PerformCopyInitialization (couldn't be all callers since this is
called for base subobject copying too, where it's acceptable to copy abstract
types) but the callers varied too much & in many cases had substantial code
or conditionals on the RequireNonAbstractType call, the
PerformCopyInitialization call, or the code between the two calls.
llvm-svn: 163555
|
| |
|
|
|
|
|
|
|
|
|
| |
load in the IndirectField declarations as well.
Field designators in initializer lists depend on traversing the fields
decl chain to find the indirect fields.
Fixes rdar://12239321
llvm-svn: 163552
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a (heavy-handed) solution to PR13724 -- until we know we can do
a good job inlining the STL, it's best to be consistent and not generate
more false positives than we did before. We can selectively whitelist
certain parts of the 'std' namespace that are known to be safe.
This is controlled by analyzer config option 'c++-stdlib-inlining', which
can be set to "true" or "false".
This commit also adds control for whether or not to inline any templated
functions (member or non-member), under the config option
'c++-template-inlining'. This option is currently on by default.
llvm-svn: 163548
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now we have a list of all commands. This is a good thing in itself, but it
also enables us to easily implement typo correction for command names.
With this change we have objects that contain information about each command,
so it makes sense to resolve command name just once during lexing (currently we
store command names as strings and do a linear search every time some property
value is needed). Thus comment token and AST nodes were changed to contain a
command ID -- index into a tables of builtin and registered commands. Unknown
commands are registered during parsing and thus are also uniformly assigned an
ID. Using an ID instead of a StringRef is also a nice memory optimization
since ID is a small integer that fits into a common bitfield in Comment class.
This change implies that to get any information about a command (even a command
name) we need a CommandTraits object to resolve the command ID to CommandInfo*.
Currently a fresh temporary CommandTraits object is created whenever it is
needed since it does not have any state. But with this change it has state --
new commands can be registered, so a CommandTraits object was added to
ASTContext.
Also, in libclang CXComment has to be expanded to include a CXTranslationUnit
so that all functions working on comment AST nodes can get a CommandTraits
object. This breaks binary compatibility of CXComment APIs.
Now clang_FullComment_getAsXML(CXTranslationUnit TU, CXComment CXC) doesn't
need TU parameter anymore, so it was removed. This is a source-incompatible
change for this C API.
llvm-svn: 163540
|
| |
|
|
|
|
|
|
|
| |
analysis that may give false positives because it is confused by aliasing, and
a less precise analysis that has fewer false positives, but may have false
negatives. The more precise warnings are enabled by -Wthread-safety-precise.
An additional note clarify the warnings in the precise case.
llvm-svn: 163537
|
| |
|
|
|
|
| |
test.
llvm-svn: 163536
|
| |
|
|
| |
llvm-svn: 163534
|
| |
|
|
|
|
| |
view them on different builders.
llvm-svn: 163529
|
| |
|
|
|
|
| |
annotations. // rdar://6386358
llvm-svn: 163525
|
| |
|
|
|
|
| |
a C++ dialect. Let's see if this is the portability issue with this test.
llvm-svn: 163524
|
| |
|
|
|
|
| |
super's annotated methods. // rdar://6386358
llvm-svn: 163517
|
| |
|
|
| |
llvm-svn: 163515
|
| |
|
|
| |
llvm-svn: 163514
|
| |
|
|
|
|
|
|
|
| |
I need to see how this breaks on other platforms when I fix the issue
that Benjamin Kramer pointed out.
This includes r163489 and r163490, plus a two line change.
llvm-svn: 163512
|
| |
|
|
|
|
|
|
| |
Android uses the same flavour of crt*.o for PIE and non-PIE executables, and a
different one for DSOs. GNU/Linux, on the other hand, uses one set of crt*.o
for non-PIE executables, and another for both PIE executables and DSOs.
llvm-svn: 163500
|
| |
|
|
|
|
|
| |
r163489, "Take another crack at stabilizing the emission order of analyzer"
r163490, "Use isBeforeInTranslationUnitThan() instead of operator<."
llvm-svn: 163497
|
| |
|
|
|
|
|
|
| |
or the name of a particular processor.
The patch reviewed by Douglas Gregor.
llvm-svn: 163492
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
diagnostics without using FoldingSetNodeIDs. This is done
by doing a complete recursive comparison of the PathDiagnostics.
Note that the previous method of comparing FoldingSetNodeIDs did
not end up relying on unstable things such as pointer addresses, so
I suspect this may still have some issues on various buildbots because
I'm not sure if the true source of non-determinism has been eliminated.
The tests pass for me, so the only way to know is to commit this change
and see what happens.
llvm-svn: 163489
|
| |
|
|
| |
llvm-svn: 163476
|
| |
|
|
|
|
|
|
|
| |
expected-warning-re to let matched for Win32 targets.
- format specifies type 'wchar_t **' (aka 'int **') but the argument has type 'float *'
- format specifies type 'wchar_t **' (aka 'unsigned short **') but the argument has type 'float *'
llvm-svn: 163468
|
| |
|
|
| |
llvm-svn: 163467
|