llvm-svn: 163491

llvm-svn: 163490

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

of a std::string.

llvm-svn: 163488

llvm-svn: 163487

analyzer tests.

llvm-svn: 163486

llvm-svn: 163485

llvm-svn: 163484

llvm-svn: 163483

We just need a single SourceLocation for previous comment end.

llvm-svn: 163482

llvm-svn: 163481

llvm-svn: 163480

llvm-svn: 163479

LiveVariables: Compute a set of defs and kills to speed up updating LV during critical edge splitting.

Previously we checked if the register is def'd in a block via the def/use list a
nd walked the list of kills to check if the register is killed in a block. Both
of these checks can be made much cheaper by walking the block first and
recording all defs and kills.

This reduces the compile time of the test case from PR13651 from 40s to 15s at
-O2. The compile time is still dominated by LV updating but now the main culprit
is SparseBitVector's slowness.

llvm-svn: 163478

llvm-svn: 163477

llvm-svn: 163476

llvm-svn: 163473

llvm-svn: 163472

This code has been replaced by the SCEVValidator a while ago.

llvm-svn: 163471

For example, which('loop-convert') returns 'loop-convert' when the directory 'loop-convert' exists.

llvm-svn: 163469

clang/test/Sema/format-strings-scanf.c: Relax a couple of expressions with 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

Otherwise a '"' in the error message, yields an invalid .dot file.

llvm-svn: 163466

llvm-svn: 163465

llvm-svn: 163464

llvm-svn: 163463

llvm-svn: 163462

llvm-svn: 163461

PathDiagnosticEventPieces were *always* pruned.  Instead, they
are suppose to only be pruned if the entire call gets pruned.

llvm-svn: 163460

string literal, produce a diagnostic pointing at the erroneous character
range, not at the start of the literal.

llvm-svn: 163459

Set operation action for FFLOOR to Expand for all vector types for X86. Set FFLOOR of v4f32 to Expand for ARM. v2f64 was already correct.

llvm-svn: 163458

Revert "Add -exact-match option to FileCheck to allow clients to do exact matches without using regular expressions."

Turns out I did not need it after all.  If we find a use for it in the future, we
can resurrect it.

llvm-svn: 163457

llvm-svn: 163456

of the analyzer by using the FullProfile() of a PathDiagnostic
for ordering them.

llvm-svn: 163455

llvm-svn: 163454

As a corollary to the previous commit, even when an extension is
available, we can still offer a fixit to the standard modifier.

llvm-svn: 163453

This seems to be a GNU libc extension; we offer a fixit to %lld on
these platforms.

<rdar://problem/11518237>

llvm-svn: 163452

the trap BB out of the individual checks and into a common function, to prepare
for making this code call into a runtime library. Rename the existing EmitCheck
to EmitTypeCheck to clarify it and to move it out of the way of the new
EmitCheck.

llvm-svn: 163451

run code when it didn't really need to run.

<rdar://problem/12145006>

llvm-svn: 163450

ObjCSelfInitChecker stashes information in the GDM to persist it across
function calls; it is stored in pre-call checks and retrieved post-call.
The post-call check is supposed to clear out the stored state, but was
failing to do so in cases where the call did not have a symbolic return
value.

This was actually causing the inappropriate cache-out from r163361.
Per discussion with Anna, we should never actually cache out when
assuming the receiver of an Objective-C message is non-nil, because
we guarded that node generation by checking that the state has changed.
Therefore, the only states that could reach this exact ExplodedNode are
ones that should have merged /before/ making this assumption.

r163361 has been reverted and the test case removed, since it won't
actually test anything interesting now.

llvm-svn: 163449