When a live interval is being spilled, rather than creating short, non-spillable
intervals for every def / use, split the interval at BB boundaries. That is, for
every BB where the live interval is defined or used, create a new interval that
covers all the defs and uses in the BB.

This is designed to eliminate one common problem: multiple reloads of the same
value in a single basic block. Note, it does *not* decrease the number of spills
since no copies are inserted so the split intervals are *connected* through
spill and reloads (or rematerialization). The newly created intervals can be
spilled again, in that case, since it does not span multiple basic blocks, it's
spilled in the usual manner. However, it can reuse the same stack slot as the
previously split interval.

This is currently controlled by -split-intervals-at-bb.

llvm-svn: 44198

llvm-svn: 44197

llvm-svn: 44196

orthogonal to the main problem there)

llvm-svn: 44194

llvm-svn: 44193

own the decl they reference if it is a FunctionDecl.  Note that his
ownership property is still considered a hack, and should be fixed.

llvm-svn: 44192

query for the number of parameters for FunctionDecls that had type
FunctionTypeNoProto.

llvm-svn: 44191

This fixes a bug reported by Seo Sanghyeon.

This was meant to be committed yesterday, but the commit failed.  doh.

llvm-svn: 44190

llvm-svn: 44189

llvm-svn: 44188

llvm-svn: 44187

llvm-svn: 44183

Codegen bits and llvm-gcc support will follow.

llvm-svn: 44182

llvm-svn: 44181

llvm-svn: 44180

llvm-svn: 44179

llvm-svn: 44178

llvm-svn: 44177

Some FunctionDecls do not appear at the top-level or are owned by a DeclStmt.
In calls to implicitly defined functions, a FunctionDecl is created, but only
the DeclRefExprs reference them. Since an implicitly defined function may be
called multiple times, there is no clear ownership model for such objects.

Temporary solution: when serializing out DeclRefExprs, emit an ownership bit
for the Decl. This bit is determined by querying the serializer to see if the
Decl has already been serialized. If it hasn't, emit the Decl as an owned
pointer.

I repeat: this is a hack.  This should be fixed.

llvm-svn: 44176

Added missing deserialization case in Stmt::Create() switch statement.

llvm-svn: 44175

llvm-svn: 44174

No need to forward declare definition of objc_super...

llvm-svn: 44173

Finish up variadic methods/messages.

llvm-svn: 44172

Implement support for variadic methods (work in progress).

llvm-svn: 44171

Extend RewriteTest::RewriteObjCIvarRefExpr() to cope with static typing (when using -> on a type which corresponds to the implementation type).

llvm-svn: 44170

Tweak funky cast to accommodate messaging 'super'. This removes any spurious warnings.

llvm-svn: 44169

Rewrite for messaging 'super'.

The code gen. results in some spurious warnings...a cast is forthcoming.

llvm-svn: 44168

llvm-svn: 44167

llvm-svn: 44166

llvm-svn: 44164

is disabled in the sense that it will refuse to create one from a UDiv
instruction, until the code is better tested.

llvm-svn: 44163

Thanks to him for his detailed analysis of the problem.

llvm-svn: 44162

Cédric Venet.

llvm-svn: 44161

llvm-svn: 44160

This fixes code like "if((bool)x) {}" for example.

Patch by Nate Begeman.

llvm-svn: 44159

llvm-svn: 44158

llvm-svn: 44157

- Implement ivar rewrite (patch by Fariborz).
- RewriteMessageExpr()...make implicit casts explicit with synthesizing call (removing warnings when calling objc_msgSend()).

llvm-svn: 44156

llvm-svn: 44154

llvm-svn: 44153