llvm-svn: 67633

is specified.
 - No easy way to make a safe test case for this (given where the
   driver is supposed to put temp files).

llvm-svn: 67632

llvm-svn: 67629

 - <rdar://problem/6715818> clang doesn't honor gcc semantic that last
    -O optimization option wins.

llvm-svn: 67628

Fix the bug that Eli noticed where we wouldn't look at function decls outside the class declaration.

llvm-svn: 67627

llvm-svn: 67626

llvm-svn: 67625

llvm-svn: 67624

llvm-svn: 67623

llvm-svn: 67622

Similarly for ppc64.  This should probably move into the driver, along
with all the other target selection stuff other than -triple.

llvm-svn: 67621

llvm-svn: 67620

change the __VERSION__ string to be more sensible.  It would be useful to include the clang version # too.

llvm-svn: 67619

the target constraint specifies a specific physreg.

llvm-svn: 67618

llvm-svn: 67617

fail.

llvm-svn: 67616

translation, the former we support, the later we don't (yet).

llvm-svn: 67611

 - Substitutes both clang and clang-cc.

 - Incorporates patch from Jon Simons to diagnose if clang or clang-cc
   isn't found.

 - Uses full path when running scripts, for more precision in the
   output.

llvm-svn: 67610

llvm-svn: 67609

llvm-svn: 67608

 - Updated ccc & driver to look in libexec/ for tools.

llvm-svn: 67607

Again, I tried to update cmake but it is untested.

llvm-svn: 67606

Again, I tried to update cmake but it is untested.

llvm-svn: 67605

llvm-svn: 67604

llvm-svn: 67603

Tests and drivers updated, still need to shuffle dirs.

llvm-svn: 67602

llvm-svn: 67601

llvm-svn: 67598

llvm-svn: 67596

llvm-svn: 67595

class C {
  void g(C c);

  virtual void f() = 0;
};

In this case, C is not known to be abstract when doing semantic analysis on g. This is done by recursively traversing the abstract class and checking the types of member functions. 

llvm-svn: 67594

llvm-svn: 67593

llvm-svn: 67592

executables (e.g., clang).
 - This matches the clang-driver behavior.

llvm-svn: 67590

to be returned in DL. LLVM's multiple-return-value support is
not ABI-conforming; front-ends that wish to have code emitted
that conforms to an ABI are currently expected to make
arrangements for this on their own rather than assuming that
multiple-return-values will automatically do the right thing.
This commit doesn't fundamentally change this situation.

llvm-svn: 67588

canClobberPhysRegDefs if the successor node doesn't
clobber any physical registers.

llvm-svn: 67587

help out the register pressure reduction heuristics in the case of
nodes with multiple uses. Currently this uses very conservative
heuristics, so it doesn't have a broad impact, but in cases where it
does help it can make a big difference.

llvm-svn: 67586

llvm-svn: 67585

llvm-svn: 67584

ccc due to the different way we handle output arguments).

llvm-svn: 67583