llvm-svn: 157893

so we can destroy it even if it was constructed with "DelayInitialization = true",
and we didn't end up calling Preprocessor::Initialize.

Fixes crashes in rdar://11558355

llvm-svn: 157892

Implementation of a "soft opt-in" option for -Wimplicit-fallthrough diagnostics: -Wimplicit-fallthrough-per-method

llvm-svn: 157871

When we timeout or exceed a max number of blocks within an inlined
function, we retry with no inlining starting from a node right before
the CallEnter node. We assume the state of that node is the state of the
program before we start evaluating the call. However, the node pruning
removes this node as unimportant. 

Teach the node pruning to keep the predecessors of the call enter nodes.

llvm-svn: 157860

We should not stop exploring the path after we return from an empty
function.

llvm-svn: 157859

Need to figure out how to get Frontend's warning parsing without bringing
in all of Frontend.

llvm-svn: 157847

show-enabled uses the command line you give it to build a CompilerInstance,
so any flags you pass will be processed as if running clang proper.

llvm-svn: 157842

llvm-svn: 157833

but different nested name specifiers to quietly clobber each other so
only one remains if they do not refer to the same NamedDecl. Fixes
PR12951.

llvm-svn: 157823

Part of rdar://11570854

llvm-svn: 157787

when migrating.

rdar://11569198

llvm-svn: 157785

Anonymous union members within a struct are now properly handled as an unevaluated field in C++11 mode.  This fixes PR12866.

llvm-svn: 157784

have correct pointer type or issue error,
instead of crashing in IRGen. // rdar:// 11569860

llvm-svn: 157780

llvm-svn: 157733

As per comments following r157659.

llvm-svn: 157722

llvm-svn: 157718

llvm-svn: 157716

This is a large class of false positives where anonymous enums are used to
declare constants (see Clang's Diagnostics.h for example). A small number of
true positives could probably be found in this bucket by still warning if the
anonymous enum is used in a declarator (enum { ... } x;) but so far we don't
believe this to be a source of significant benefit so I haven't bothered to
preserve those cases.

General offline review/acknowledgment by rtrieu.

llvm-svn: 157713

and reported as PR12959. // rdar://11499742

llvm-svn: 157697

supply a simple-minded testcase for r156813, to check whether the embedded montavista gcc toolchain is recognized

llvm-svn: 157686

same value and were initialized with literals.  Clang will warn on code like
this:

enum A {
  FIRST = 1,
  SECOND = 1
};

llvm-svn: 157666

Also, do not display the builtin name and macro expansion when the
function is a builtin.

llvm-svn: 157659

This patch fixes it. // rdar://11488351

llvm-svn: 157646

llvm-svn: 157642

getter result type is safe but does not match with property 
type resulting in spurious warning followed by crash in
IRGen. // rdar://11515196

llvm-svn: 157641

This is a clean-room implementation based on public documentation and
I tried to validate it as much as possible against gcc.

llvm-svn: 157638

llvm-svn: 157635

This doesn't really fit the existing SSELevel so it gets an extra flag.

llvm-svn: 157630

Leave a better fixme for different debug info flags

llvm-svn: 157602

for this. Reported by Timur Iskhodzhanov.

llvm-svn: 157583

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

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

llvm-svn: 157537

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

llvm-svn: 157524

// 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

switch label immediately followed by a 'break;'.

llvm-svn: 157508

add test case for C++ codegen

llvm-svn: 157500

llvm-svn: 157491