llvm-svn: 155307

names. This saves collecting types we normally don't care about.

llvm-svn: 155300

StringRef::getAsInteger

llvm-svn: 155298

llvm-svn: 155297

llvm-svn: 155296

llvm-svn: 155294

llvm-svn: 155291

It set NumLowBitAvailable = 3 which may not be true on all platforms.  We only
ever use 2 bits (the default) so this assumption can be safely removed

Should fix PR12612.

llvm-svn: 155288

Thanks to Andy Gibbs, to report the issue.

llvm-svn: 155287

llvm-svn: 155286

llvm-svn: 155285

llvm-svn: 155284

llvm-svn: 155283

llvm-svn: 155281

No functionality change.

llvm-svn: 155280

llvm-svn: 155270

VMUL and VEXT.

llvm-svn: 155258

The X86 target is editing the selection DAG while isel is selecting
nodes following a topological ordering. When the DAG hacking triggers
CSE, nodes can be deleted and bad things happen.

llvm-svn: 155257

llvm-svn: 155254

llvm-svn: 155253

Now that multiple DAGUpdateListeners can be active at the same time,
ISelPosition can become a local variable in DoInstructionSelection.

We simply register an ISelUpdater with CurDAG while ISelPosition exists.

llvm-svn: 155249

Instead of passing listener pointers to RAUW, let SelectionDAG itself
keep a linked list of interested listeners.

This makes it possible to have multiple listeners active at once, like
RAUWUpdateListener was already doing. It also makes it possible to
register listeners up the call stack without controlling all RAUW calls
below.

DAGUpdateListener uses an RAII pattern to add itself to the SelectionDAG
list of active listeners.

llvm-svn: 155248

llvm-svn: 155247

process any more Values.

llvm-svn: 155241

The <undef> flag on a def operand only applies to partial register
redefinitions. Only print the flag when relevant, and print it as
<def,read-undef> to make it clearer what it means.

llvm-svn: 155239

llvm-svn: 155235

llvm-svn: 155234

llvm-svn: 155230

llvm-svn: 155229

This nicely handles the most common case of virtual register sets, but
also handles anticipated cases where we will map pointers to IDs.

The goal is not to develop a completely generic SparseSet
template. Instead we want to handle the expected uses within llvm
without any template antics in the client code. I'm adding a bit of
template nastiness here, and some assumption about expected usage in
order to make the client code very clean.

The expected common uses cases I'm designing for:
- integer keys that need to be reindexed, and may map to additional
  data
- densely numbered objects where we want pointer keys because no
  number->object map exists.

llvm-svn: 155227

llvm-svn: 155226

llvm-svn: 155225

build system generate this file with the proper version.

llvm-svn: 155221

llvm-svn: 155213

llvm-svn: 155211

Use the new TwoOperandAliasConstraint to handle lots of the two-operand aliases
for NEON instructions. There's still more to go, but this is a good chunk of
them.

llvm-svn: 155210

Add debugging hints for when bugpoint does not suffice, specifically for instcombine and TargetLowering

llvm-svn: 155209

 - Also, drop the lines.gif background from doxygen, this URL was wrong on the
   llvm.org server anyway.

llvm-svn: 155208

llvm-svn: 155206

llvm-svn: 155203