and provides fairly efficient removal of arbitrary elements. Switch
ScheduleDAGRRList from std::set to this new priority queue.

llvm-svn: 52582

llvm-svn: 52581

Patch by David Chisnall with objc rewriter and stmtdumper updates from me.

llvm-svn: 52580

since handling this correctly is quite complex, and on some platforms  
requires additional -D options and on some implies linking against a  
different libc, but this works better than just ignoring the option.

The other change passes the -x option across to clang, which allows  
compiling .c files as Objective-C and so on.  For some reason a lot of  
configure scripts seem to be under the misguided impression that this  
is a sensible thing to do."

Patch by David Chisnall!

llvm-svn: 52579

llvm-svn: 52578

don't know if a truncating store is possible here,
but added support for it anyway.

llvm-svn: 52577

to DenseMap<SDNode*, SUnit*>, and adjust the way cloned SUnit nodes are
handled so that only the original node needs to be in the map.
This speeds up llc on 447.dealII.llvm.bc by about 2%.

llvm-svn: 52576

llvm-svn: 52575

llvm-svn: 52574

llvm-svn: 52572

llvm-svn: 52571

llvm-svn: 52570

llvm-svn: 52569

llvm-svn: 52568

When using the dead-stores checker with the BugReporter class, properly capture the diagnostic associated with a specific warning and emit it.

llvm-svn: 52565

  http://lists.cs.uiuc.edu/pipermail/llvmdev/2008-June/015446.html

llvm-svn: 52564

llvm-svn: 52563

llvm-svn: 52560

llvm-svn: 52559

llvm-svn: 52556

1) Check if a dead store appears as a subexpression.  For such cases, we emit
   a verbose diagnostic so that users aren't confused.  This addresses:
   
   <rdar://problem/5968508> checker gives misleading report for dead store in loop
   
2) Don't emit a dead store warning when assigning a null value to a pointer.
   This is a common form of defensive programming.  We may wish to make
   this an option to the the checker one day.
   
   This addresses the feature request in the following email:
   
   http://lists.cs.uiuc.edu/pipermail/cfe-dev/2008-June/001978.html

llvm-svn: 52555

Enhanced heuristic to determine the *best* register to spill. Instead of picking the register with the lowest spill weight. Consider (up to) 2 additional registers with spill weights that are close to the lowest spill weight. The one with fewest defs and uses that conflicts with the current interval (weighted by loop depth) is the spill candidate.

This is not always a win, but there are much more wins than loses and wins tend to be more noticeable.

llvm-svn: 52554

llvm-svn: 52553

Added "Decl::getCodyBody()", a virtual method that returns the root AST node (Stmt*) that the Decl wraps (if any).  Currently this only returns a non-null value for FunctionDecl and ObjCMethodDecl.

llvm-svn: 52552

llvm-svn: 52551

llvm-svn: 52550

llvm-svn: 52549

float expansion (and sometimes vector splitting too).

llvm-svn: 52548

store, like the methods for loads (and neaten
those up a bit while there).

llvm-svn: 52547

integer of the same type.  Before it was "promotion",
but this is confusing because it is quite different
to promotion of integers.  Call it "softening" instead,
inspired by "soft float".

llvm-svn: 52546

llvm-svn: 52545

llvm-svn: 52544

getInsertedValueOperand accessors. Thanks Matthijs!

llvm-svn: 52543

instructions. Thanks to Matthijs Kooijman for pointing this out!

llvm-svn: 52542

llvm-svn: 52541

llvm-svn: 52540

llvm-svn: 52539

type wasn't changed.

llvm-svn: 52538

into T) when no return values are actually dead.

llvm-svn: 52537

DeadArgumentElimination and assert that the function type does not change if
nothing was changed. This should catch subtle changes in function type that are
not intended.

llvm-svn: 52536