llvm-svn: 107393

reformulate CallSiteBase::getCallee to adapt to CallInst::ArgOffset, and make it work even if CallInst::op_* are private

llvm-svn: 107392

reformulate CallSite::getCallee to adapt to CallInst::ArgOffset, and make it work even if CallInst::op_* are private

llvm-svn: 107390

doing the work manually.

llvm-svn: 107384

from a Value to a Type, because it doesn't actually care about
the Value.

llvm-svn: 107383

llvm-svn: 107381

available in a register. This is pretty primitive, but it reduces the
number of instructions in common testcases by 4%.

llvm-svn: 107380

llvm-svn: 107377

to SelectionDAG.

llvm-svn: 107376

llvm-svn: 107375

the same address.

llvm-svn: 107373

SelectionDAGBuilder::getValue into a helper function, with fixes to
use DenseMaps safely.

llvm-svn: 107371

value if the search fails.

llvm-svn: 107368

- Add AVX SSE2 Move doubleword and quadword instructions.
- Add encode bits for VEX_W
- All 128-bit SSE 1 & SSE2 instructions that are described
  in the .td file now have a AVX encoded form already working.

llvm-svn: 107365

llvm-svn: 107363

llvm-svn: 107362

llvm-svn: 107361

llvm-svn: 107360

llvm-svn: 107355

llvm-svn: 107351

correct catch-all value. This saves having to iterate through all of the
selectors in the program again.

llvm-svn: 107345

llvm-svn: 107335

llvm-svn: 107334

structs. rdar://8145832

llvm-svn: 107332

llvm-svn: 107323

llvm-svn: 107321

entries associated with the value being erased in the
folding set map.  These entries used to be harmless, because
a SCEVUnknown doesn't store any information about its Value*,
so having a new Value allocated at the old Value's address
wasn't a problem. But now that ScalarEvolution is storing more
information about values, this is no longer safe.

llvm-svn: 107316

llvm-svn: 107308

llvm-svn: 107307

llvm-svn: 107306

LocalRewriter::runOnMachineFunction uses this information to mark dead spill
slots.

This means that InlineSpiller now also works for functions that spill.

llvm-svn: 107302

llvm-svn: 107300

nsw and nuw flags from IR Instructions. On further consideration,
this isn't valid.

llvm-svn: 107298

llvm-svn: 107297

this could break something (but doesn't seem to).

llvm-svn: 107295

llvm-svn: 107293

llvm-svn: 107286

replaced by a bigger array in SmallPtrSet (by overridding it), instead just use a
pointer to the start of the storage, and have SmallPtrSet pass in the value to use.
This has the disadvantage that SmallPtrSet becomes bigger by one pointer.  It has
the advantage that it no longer uses tricky C++ rules, and is clearly correct while
I'm not sure the previous version was.  This was inspired by g++-4.6 pointing out
that SmallPtrSetImpl was writing off the end of SmallArray, which it was.  Since
SmallArray is replaced with a bigger array in SmallPtrSet, the write was still to
valid memory.  But it was writing off the end of the declared array type - sounds
kind of dubious to me, like it sounded dubious to g++-4.6.  Maybe g++-4.6 is wrong
and this construct is perfectly valid and correctly compiled by all compilers, but
I think it is better to avoid the whole can of worms by avoiding this construct.

llvm-svn: 107285

llvm-svn: 107282

llvm-svn: 107280