llvm-svn: 90326

llvm-svn: 90324

llvm-svn: 90323

llvm-svn: 90322

This is necessary for tests so the results are comparable.

llvm-svn: 90320

llvm-svn: 90319

llvm-svn: 90318

involving unsaved files, using the -remap-file= functionality recently
added to clang-cc.

llvm-svn: 90314

llvm-svn: 90313

llvm-svn: 90312

source files.

llvm-svn: 90311

llvm-svn: 90310

LookupResult::getAsSingleDecl() is no more.  Shift Sema::LookupSingleName to
return null on overloaded results.

llvm-svn: 90309

llvm-svn: 90308

  -remap-file=from;to

which takes the file "from" and transparently replaces its contents
with the contents of the file "to" from the source manager's
perspective. This is the moral equivalent of

  cp from saved
  cp to from
  <call clang>
  cp saved from
  rm saved

without all of the pesky file copying.

llvm-svn: 90307

leaked data structure than before.  This kills off the last remaining 
explicit uses of OverloadedFunctionDecl in Sema.                                         

llvm-svn: 90306

Highlights include:

  Add a helper to generate __cxa_free_exception and _ZSt9terminatev.
  Add a region to handle EH object deallocation for ctor failures for throw.
  Add a terminate handler for __cxa_end_catch.
  A framework for adding cleanup actions for the exceptional edges only.

llvm-svn: 90305

per Chris' comments.  Adjust testcases to match.

llvm-svn: 90304

isVirtual() before we've actually calculated whether the destructor is
virtual.

llvm-svn: 90303

llvm-svn: 90302

it's rare, but possible, for the difference to be significant.

llvm-svn: 90301

files with the contents of an arbitrary memory buffer. Use this new
functionality to drastically clean up the way in which we handle file
truncation for code-completion: all of the truncation/completion logic
is now encapsulated in the preprocessor where it belongs
(<rdar://problem/7434737>).

llvm-svn: 90300

llvm-svn: 90299

llvm-svn: 90298

llvm-svn: 90297

we don't need to use the DoneEvaluation hack when check for 
ObjCMessageExpr.

PreVisitObjCMessageExpr() only checks for undefined receiver or arguments.

Add checker interface EvalNilReceiver(). This is a 'once-and-done' interface.

llvm-svn: 90296

llvm-svn: 90295

llvm-svn: 90294

llvm-svn: 90293

llvm-svn: 90292

llvm-svn: 90291

llvm-svn: 90290

there's nothing interesting we can say now that we're correctly not requiring
the qualifier to name a known base class in dependent contexts.

Require scope specifiers on member access expressions to name complete types
if they're not dependent;  delay lookup when they are dependent.

Use more appropriate diagnostics when qualified implicit member access
expressions find declarations from unrelated classes.

llvm-svn: 90289

(clang/driver) command line arguments (including the source file).
 - The arguments are expected to include the source file.

 - The idea is that even though this is a somewhat odd API, its the form which
   many tools can most easily use (for example, by interposing with the compiler).

Also, switch index-test's -ast-from-source to use this entry point, and provide
a -arg command line argument which can be used to test that the command line
arguments are handled correctly.

llvm-svn: 90288

used to create a particular command.

llvm-svn: 90287

llvm-svn: 90285

Fixes pr5660.

llvm-svn: 90283

llvm-svn: 90282

llvm-svn: 90281

In SourceManager::isBeforeInTranslationUnit, if we are trying to compare two source locations with no common ancestor in the include stack, determine order by assuming memory buffers preceed files, and then that FileIDs are created in order.

The later assumption is patently false, but this was already broken -- this situation is conceptually impossible, my feeling is we should fix SourceManager and friends to make it impossible in practice as well. However, we need to fix PR5662 and perhaps some other things involving memory buffers first. In the short term I'm pretty sure this is reliable.

Chris, Argiris, is this going to break anything that wasn't already broken?

llvm-svn: 90280