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

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

llvm-svn: 107295

llvm-svn: 107293

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

llvm-svn: 107279

llvm-svn: 107278

llvm-svn: 107277

llvm-svn: 107276

llvm-svn: 107275

llvm-svn: 107273

llvm-svn: 107272

llvm-svn: 107271

llvm-svn: 107270

llvm-svn: 107269

llvm-svn: 107257

the old one instead of replacing it, to be more precise.

llvm-svn: 107256

on ScalarEvolution successfully folding and preserving
range information for both A-B and B-A. Now, if it gets
either one, it's sufficient.

llvm-svn: 107249

llvm-svn: 107248

llvm-svn: 107246

llvm-svn: 107245

llvm-svn: 107244

llvm-svn: 107243

llvm-svn: 107241

llvm-svn: 107240

- Add VEX encoding bits to x86 MRM0r-MRM7r

llvm-svn: 107238

llvm-svn: 107237

llvm-svn: 107234

llvm-svn: 107233

Add variables into a scope before constructing scope DIE otherwise variables won't be included DIE tree. 

llvm-svn: 107228