llvm-svn: 103831

llvm-svn: 103830

replace the check with the appropriate predicate. Modify the testcase to reflect
the correct code. (It should be saving callee-saved registers on the stack
allocated by the calling fuction.)

llvm-svn: 103829

llvm-svn: 103828

llvm-svn: 103827

llvm-svn: 103826

of "has calls". That's probably wrong, but it needs further
investigation. Revert to the original behavior until this is settled.

llvm-svn: 103824

llvm-svn: 103823

llvm-svn: 103822

llvm-svn: 103821

llvm-svn: 103820

stack.

llvm-svn: 103813

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

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

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

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

llvm-svn: 103784

llvm-svn: 103778

control barriers, not memory ordering barriers.

llvm-svn: 103777

llvm-svn: 103776

isn't doing lazy streaming. This also fixes a missing doFinalization call.

llvm-svn: 103774

FunctionPassManager or regular PassManager.

llvm-svn: 103773

subgraph views.

llvm-svn: 103772

-filetype=obj test, and -filetype=obj leaks a few objects. Added a FIXME, we
need to sort out the ownership model for the various MC objects.

llvm-svn: 103769

Get rid of the bit twiddling to read / set OpActions and ValueTypeActions. The small saving in memory isn't worth the increase in runtime and code complexity in my opinion.

llvm-svn: 103768

 - This is a hack, but I can't decide the best place to handle this. Chris?

llvm-svn: 103765

llvm-svn: 103764

llvm-svn: 103760

Nothing uses this yet.

llvm-svn: 103757

llvm-svn: 103756

llvm-svn: 103755