llvm-svn: 157557

This comes up in the begin/end calls of a range-for (see the included test
case). Other suggestions are welcome, though this seems to do the trick without
regressing anything.

llvm-svn: 157553

as zeroes. Now the digits are properly non-zero.

llvm-svn: 157552

The DenseMap reallocates after 64 insertions so this only happened in
large test cases under very specific circumstances.

llvm-svn: 157549

bitwidth and signedness. Also rename the variable to reflect its purpose.

No test case - discovered during random code exploration.

llvm-svn: 157547

to the declaration in this patch. // rdar://10893232

llvm-svn: 157537

Retain + Release on a ref counted pointer is cheap, but not free (it adds a function call in this case).

llvm-svn: 157534

llvm-svn: 157533

While there make it a SmallPtrSet.

llvm-svn: 157532

llvm-svn: 157531

llvm-svn: 157530

clang/lib/Rewrite/Rewriter.cpp: Don't try to rename opened files on Win32. Win32 doesn't allow rename/removing opened files.

llvm-svn: 157528

the Microsoft Visual C++ ABI. Currently limited to type and integral
non-type arguments. Based on a patch by Timur Iskhodzhanov!

llvm-svn: 157524

No test as the output is highly dependend on the local configuration.

llvm-svn: 157520

// rdar://11528439

llvm-svn: 157517

-Wsometimes-uninitialized diagnostics to make it clearer that the cause
of the issue may be a condition which must always evaluate to true or
false, rather than an uninitialized variable.

To emphasize this, add a new note with a fixit which removes the
impossible condition or replaces it with a constant.

Also, downgrade the diagnostic from -Wsometimes-uninitialized to
-Wconditional-uninitialized when it applies to a range-based for loop,
since the condition is not written explicitly in the code in that case.

llvm-svn: 157511

llvm-svn: 157510

switch label immediately followed by a 'break;'.

llvm-svn: 157508

add test case for C++ codegen

llvm-svn: 157500

llvm-svn: 157491

method template.

llvm-svn: 157486

llvm-svn: 157483

function template.

llvm-svn: 157480

llvm-svn: 157478

the visibility.

llvm-svn: 157475

Similar fixes for function and member template to follow as I write the
testcases.

llvm-svn: 157470

llvm-svn: 157469

llvm-svn: 157462

llvm-svn: 157459

-Wsometimes-uninitialized. This detects cases where an explicitly-written branch
inevitably leads to an uninitialized variable use (so either the branch is dead
code or there is an uninitialized use bug).

This chunk of warnings tentatively lives within -Wuninitialized, in order to
give it more visibility to existing Clang users.

llvm-svn: 157458

Load custom plugins when running scan-build. This is useful when
additional static analysis Checkers must be provided via clang's plugin
interface.

Loading additional plugins can now be done via the scan-build call:
scan-build -load-plugin <plugin.so>

A patch by Thomas Hauth.

llvm-svn: 157452

if the value isn't an unsigned char or EOF behavior is undefined
(and on Windows there's an assertion)

llvm-svn: 157445

llvm-svn: 157440

llvm-svn: 157436

backing two propeties because proprty names
match except for first letter being of different
case. // rdar://11528439, [PR12936].

llvm-svn: 157435

llvm-svn: 157434

Implement the C++11 discarded value expression rules for volatile lvalues.  <rdar://problem/10790820>.

llvm-svn: 157420

landed in LLVM core

llvm-svn: 157418

A minor tweak to the new volatile lvalue warning: don't warn on "(void)x", where "x" refers to a local variable.  This should silence a useless warning in compiler-rt and other places. 

llvm-svn: 157414

renaming in r157403.

llvm-svn: 157413