llvm-svn: 72600

move to DeclPrinter.cpp, but I haven't quite worked out how best to do 
that.

llvm-svn: 72599

(I have a work-in-progress patch which uses this.)

llvm-svn: 72598

walks through DeclContexts properly, and prints more of the
information available in the AST. The functionality is still available
via -ast-print, -ast-dump, etc., and also via the new member functions
Decl::dump() and Decl::print().

llvm-svn: 72597

llvm-svn: 72594

llvm-svn: 72593

llvm-svn: 72591

printing logic to help customize the output. For now, we use this
rather than a special flag to suppress the "struct" when printing
"struct X" and to print the Boolean type as "bool" in C++ but "_Bool"
in C.

llvm-svn: 72590

llvm-svn: 72589

hadError (suppressing future diagnostics) if we didn't print an 
error.

llvm-svn: 72588

VLAs.

llvm-svn: 72587

invoke results (see the testcases).  Tighten up the checking.

llvm-svn: 72586

actually necessary in some obscure cases.

llvm-svn: 72585

tried other things that might trip, but they all worked.

llvm-svn: 72584

llvm-svn: 72583

template instantiation. This helps reduce our stack footprint when
performing deep template instantiations.

llvm-svn: 72582

handle the construct in question correctly.

llvm-svn: 72581

llvm-svn: 72580

llvm-svn: 72579

llvm-svn: 72578

llvm-svn: 72577

llvm-svn: 72576

a vla is used.

llvm-svn: 72575

llvm-svn: 72574

llvm-svn: 72573

any body can spot codegen bugs with volatile, or knows of any in the
bug database, let me know.

llvm-svn: 72572

llvm-svn: 72571

llvm-svn: 72570

llvm-svn: 72569

instantiation of tags local to member functions of class templates
(and, eventually, function templates) works when the tag is defined as
part of the decl-specifier-seq, e.g.,

  struct S { T x, y; } s1;

Also, make sure that we don't try to default-initialize a dependent
type.

llvm-svn: 72568

is, otherwise we get a <badref>.

llvm-svn: 72567

This is useful when trying to figure out why GVN didn't eliminate redundant
loads.

llvm-svn: 72565

Diagnosis and patch thanks to Jakub Staszak.

llvm-svn: 72562

llvm-svn: 72561

llvm-svn: 72560

to the DeclGroup.

llvm-svn: 72559

llvm-svn: 72558

llvm-svn: 72557

decoding. Essentially, they both map to the same column in the "opcode
extensions for one- and two-byte opcodes" table in the x86 manual. The RawFrm
complicates decoding this.

Instead, use opcode 0x01, prefix 0x01, and form MRM1r. Then have the code
emitter special case these, a la [SML]FENCE.

llvm-svn: 72556

specifier resulted in the creation of a new TagDecl node, which
happens either when the tag specifier was a definition or when the tag
specifier was the first declaration of that tag type. This information
has several uses, the first of which is implemented in this commit:

  1) In C++, one is not allowed to define tag types within a type
  specifier (e.g., static_cast<struct S { int x; } *>(0) is
  ill-formed) or within the result or parameter types of a
  function. We now diagnose this.

  2) We can extend DeclGroups to contain information about any tags
  that are declared/defined within the declaration specifiers of a
  variable, e.g.,

    struct Point { int x, y, z; } p;

  This will help improve AST printing and template instantiation,
  among other things.

  3) For C99, we can keep track of whether a tag type is defined
  within the type of a parameter, to properly cope with cases like,
  e.g.,

    int bar(struct T2 { int x; } y) {
      struct T2 z;
    }

  We can also do similar things wherever there is a type specifier,
  e.g., to keep track of where the definition of S occurs in this
  legal C99 code:

    (struct S { int x, y; } *)0

  

llvm-svn: 72555