- PR3566

llvm-svn: 64492

just silently return an error to avoid bogus diagnostics.

llvm-svn: 64491

PTH: Cache directory and negative 'stat' calls.  This gives us a 1% performance improvement on Cocoa.h (fsyntax-only+PTH).

llvm-svn: 64490

llvm-svn: 64489

 - Fix emission of static functions with constructor attribute while I
   was here.
<rdar://problem/6140899> [codegen] "static" and attribute-constructor interact poorly

llvm-svn: 64488

for attribute used support.  
- No functionality change.

llvm-svn: 64487

llvm-svn: 64486

llvm-svn: 64485

llvm-svn: 64482

llvm-svn: 64481

wine sources.  This was happening because HighlightMacros was 
calling EnterMainFile multiple times on the same preprocessor
object and getting an assert due to the new #line stuff (the
file in question was bison output with #line directives).

The fix for this is to not reenter the file.  Instead, 
relex the tokens in raw mode, swizzle them a bit and repreprocess
the token stream.  An added bonus of this is that rewrite macros
will now hilight the macro definition as well as its uses.  Woo.

llvm-svn: 64480

llvm-svn: 64479

llvm-svn: 64478

Add some boilerplate to the PTH file to prepare for the caching of stats for directories (and negative stats too).

llvm-svn: 64477

llvm-svn: 64476

llvm-svn: 64475

by DeclContexts (always) rather than by statements. 

DeclContext currently goes out of its way to avoid destroying any
Decls that might be owned by a DeclGroupOwningRef. However, in an
error-recovery situation, a failure in a declaration statement can
cause all of the decls in a DeclGroupOwningRef to be destroyed after
they've already be added into the DeclContext. Hence, DeclContext is
left with already-destroyed declarations, and bad things happen. This
problem was causing failures that showed up as assertions on x86 Linux
in test/Parser/objc-forcollection-neg-2.m.

llvm-svn: 64474

llvm-svn: 64473

llvm-svn: 64472

llvm-svn: 64471

implementation with no category declaration!

llvm-svn: 64470

 - Now at 1274 passes on gcc compat suite vs 1262.

llvm-svn: 64469

printing getName(), so that unnamed values are printed correctly.

llvm-svn: 64468

llvm-svn: 64467

llvm-svn: 64466

about the code it describes, but at least now the comment
is right.

llvm-svn: 64465

being used for atomic intrinsics, it seems the
access may be volatile.  No code was exploiting
the original non-volatile definition, so only
the comment needs changing.

llvm-svn: 64464

it only reads memory!  The other change has no
functional effect, it just seems more logical to
go in order of decreasing knowledge.

llvm-svn: 64463

llvm-svn: 64461

llvm-svn: 64460

llvm-svn: 64459

llvm-svn: 64458

llvm-svn: 64457

llvm-svn: 64456

llvm-svn: 64455

llvm-svn: 64454

mark the first argument nocapture if endptr=NULL for each particular call.

llvm-svn: 64453

llvm-svn: 64452

llvm-svn: 64451

llvm-svn: 64450