llvm-svn: 69551

llvm-svn: 69550

llvm-svn: 69548

llvm-svn: 69547

llvm-svn: 69545

for a token is set, this makes the diagnostic "expanded from stack" work
for this diagnostic.  Add a testcase for PR3918.

llvm-svn: 69544

llvm-svn: 69543

llvm-svn: 69540

llvm-svn: 69539

llvm-svn: 69538

llvm-svn: 69537

Another piece of the conditional operator puzzle. We'll want to use FindCompositePointerType in some other places, too.

llvm-svn: 69534

llvm-svn: 69532

in a function-like macro body.  This has the added bonus of moving some
function-like macro specific code out of the object-like macro codepath.

llvm-svn: 69530

with assembler-with-cpp mode.

llvm-svn: 69520

llvm-svn: 69518

@class but no implementation.  This was broken in all 3 runtime
impls.

llvm-svn: 69512

they do allow switches.

llvm-svn: 69510

calling into the jump checker when a function or method is known to contain
no VLAs or @try blocks.

llvm-svn: 69509

llvm-svn: 69508

llvm-svn: 69507

llvm-svn: 69506

 - The confusing IRgen bitfield interface is partly to blame here;
   fixing the functional error for now, cleanups to the interface to
   follow.

llvm-svn: 69503

address taken labels are in function scope

llvm-svn: 69499

llvm-svn: 69498

llvm-svn: 69492

VLA's and statement expressions.

llvm-svn: 69491

llvm-svn: 69490

llvm-svn: 69488

llvm-svn: 69487

the scope checker to not think @catches are nested in each other, eliminating
some bogus notes.

llvm-svn: 69486

llvm-svn: 69485

reasonably well except for the problem that @catches are nested within
each other in the AST, giving the ugly diagnostics in L8.

llvm-svn: 69477

statements don't end up in the LabelMap so we don't have a quick way
to filter them.  We could add state to Sema (a "has vla" and "has 
jump" bit) to try to filter this out, but that would be sort of gross
and I'm not convinced it is the best way.  Thoughts welcome.

llvm-svn: 69476

llvm-svn: 69470

llvm-svn: 69466

This fixes a crash on invalid (test10). rdar://6805469

llvm-svn: 69465

specific bad case instead of on the switch.  Putting it on the
switch means you don't know what case is the problem. For 
example:

scope-check.c:54:3: error: illegal switch case into protected scope
  case 2:
  ^
scope-check.c:53:9: note: jump bypasses initialization of variable length array
    int a[x];
        ^

llvm-svn: 69462

llvm-svn: 69461

llvm-svn: 69460