llvm-svn: 103821

llvm-svn: 103820

llvm-svn: 103819

llvm-svn: 103814

stack.

llvm-svn: 103813

Radar 7923673.

llvm-svn: 103812

part (or possibly all) of PR7132.

llvm-svn: 103810

Clang's representation of the C type system to clients.  It is nowhere near complete, and will
be expanded on demand.

llvm-svn: 103809

llvm-svn: 103808

llvm-svn: 103807

llvm-svn: 103806

while debugging what's mishandled about them in the post-RA pass.

llvm-svn: 103805

llvm-svn: 103804

throw, it should use invoke when needed. The fixes the
Boost.Statechrt failures that motivated PR7132, but there are a few
side issues to tackle as well.

llvm-svn: 103803

the variable actually tracks.

N.B., several back-ends are using "HasCalls" as being synonymous for something
that adjusts the stack. This isn't 100% correct and should be looked into.

llvm-svn: 103802

llvm-svn: 103801

used more than once. If ISel had put a kill flag on one of them,
it's not valid to transfer the kill flag to each new instance.

llvm-svn: 103799

llvm-svn: 103798

- Kill is implicit when use and def registers are identical.
- Only virtual registers can differ.

Add a -verify-fast-regalloc to run the verifier before the fast allocator.

llvm-svn: 103797

llvm-svn: 103796

llvm-svn: 103795

llvm-svn: 103794

llvm-svn: 103793

llvm-svn: 103792

argument, like "int $4", to not get an Assertion error.

llvm-svn: 103791

llvm-svn: 103790

used to replace a normal relocation, not a reference to a GOT entry.

llvm-svn: 103789

llvm-svn: 103788

user directive is needed to force a property implementation.
It is decided based on those propeties which are declared in
the class (or in its protocols) but not those which must be
default implemented by one of its super classes. Implements radar 7923851.

llvm-svn: 103787

llvm-svn: 103785

This adds extra security against using clobbered physregs, and it adds kill
markers to physreg uses.

llvm-svn: 103784

declarator is incorrect.  Not being a typename causes the parser to 
dive down into the K&R identifier list handling stuff, which is almost
never the right thing to do.

Before:

r.c:3:17: error: expected ')'
void bar(intptr y);
                ^
r.c:3:9: note: to match this '('
void bar(intptr y);
        ^
r.c:3:10: error: a parameter list without types is only allowed in a function definition
void bar(intptr y);
         ^

After:

r.c:3:10: error: unknown type name 'intptr'; did you mean 'intptr_t'?
void bar(intptr y);
         ^~~~~~
         intptr_t
r.c:1:13: note: 'intptr_t' declared here
typedef int intptr_t;
            ^

This fixes rdar://7980651 - poor recovery for bad type in the first arg of a C function

llvm-svn: 103783

llvm-svn: 103782

identifier in the identifier list consumed before it is called.
No functionality change.

llvm-svn: 103781

llvm-svn: 103780

Providing linkage name for function static variable confuses gdb, so don't do that.

llvm-svn: 103779

llvm-svn: 103778

control barriers, not memory ordering barriers.

llvm-svn: 103777

llvm-svn: 103776

types.", it is breaking Clang bootstrap.

llvm-svn: 103775