llvm-svn: 58877

is noticeably worse than previous PPC-specific code.
Since the latter was also wrong in some cases and
correctness is more important than efficiency, I'm
disabling this test temporarily while I fix it.

llvm-svn: 58876

llvm-svn: 58875

llvm-svn: 58874

llvm-svn: 58873

llvm-svn: 58872

This is Chris' patch from the PR, modified to realize that
SETUGT/SETULT occur legitimately with integers, plus
two fixes in LegalizeDAG to pass a valid result type into
LegalizeSetCC.  The argument of TLI.getSetCCResultType is
ignored on PPC, but I think I'm following usage elsewhere.

llvm-svn: 58871

llvm-svn: 58870

llvm-svn: 58869

llvm-svn: 58868

llvm-svn: 58867

-When parsing declarators, don't depend on "CurScope->isCXXClassScope() == true" for constructors/destructors
-For C++ member declarations, don't depend on "Declarator.getContext() == Declarator::MemberContext"

llvm-svn: 58866

exception, like it does for a std::string exception.

llvm-svn: 58865

llvm-svn: 58864

llvm-svn: 58863

llvm-svn: 58862

the condition for a BRCOND, according to what is
returned by getSetCCResultContents.  Since all
targets return the same thing (ZeroOrOneSetCCResult),
this should be harmless!  The point is that all over
the place the result of SETCC is fed directly into
BRCOND.  On machines for which getSetCCResultContents
returns ZeroOrNegativeOneSetCCResult, this is a
sign-extended boolean.  So it seems dangerous to
also feed BRCOND zero-extended booleans in some
circumstances - for example, when promoting the
condition.

llvm-svn: 58861

functions in C++, e.g.,

  struct X {
    operator bool() const;
  };

Note that these conversions don't actually do anything, since we don't
yet have the ability to use them for implicit or explicit conversions.

llvm-svn: 58860

This is a temporary fix for the -print-emitted-asm option, where
errs() is used as the stream, in the case where other code is
using stderr without using errs()' buffer. Hopefully soon we'll
fix errs() to be non-buffered instead. Patch by Preston Gurd.

llvm-svn: 58859

llvm-svn: 58856

Assert that Parser::MaybeParseOperatorFunctionId is called when token is kw_operator, and replace ExpectAndConsume for the 'operator' token with a ConsumeToken.

llvm-svn: 58855

Separate the parsing of type-specifiers from other declaration specifiers, so that we can parse a C++ type-specifier-seq

llvm-svn: 58854

include alloca.h instead of malloc.h. If this doesn't work for everyone we can just declare alloca directly in the file.

llvm-svn: 58853

llvm-svn: 58852

llvm-svn: 58851

When allocating an array for ParamInfo, the "decl->getNumParams()" call was used, but this will return 0 since it checks ParamInfo (which isn't yet defined and is null).
The result was that ParamInfo got an array of zero length to hold the ParmVarDecls.

llvm-svn: 58850

llvm-svn: 58849

llvm-svn: 58848

llvm-svn: 58847

void f() {
   int +; // crash here
}

llvm-svn: 58846

llvm-svn: 58845

llvm-svn: 58844

llvm-svn: 58843

llvm-svn: 58842

llvm-svn: 58841

llvm-svn: 58840

llvm-svn: 58839

llvm-svn: 58838

available, things get much simplified.

One addition is that CompoundLiteralExpr can appear both in rvalue and lvalue
context.

llvm-svn: 58837

llvm-svn: 58836