is morphed by AnalyzeNewNode into a previously
processed node, and different result values of
that node are remapped to values with different
nodes, then we could end up using wrong values
here [we were assuming that all results remap
to values with the same underlying node].  This
seems theoretically possible, but I don't have
a testcase.  The meat of the patch is in the
changes to AnalyzeNewNode/AnalyzeNewValue and
ReplaceNodeWith.  While there, I changed names
like RemapNode to RemapValue, since it really
remaps values.  To tell the truth, I would be
much happier if we were only remapping nodes
(it would simplify a bunch of logic, and allow
for some cute speedups) but I haven't yet worked
out how to do that.

llvm-svn: 58372

llvm-svn: 58371

llvm-svn: 58370

- Create and update spill slot live intervals.
- Lots of bug fixes.

llvm-svn: 58367

llvm-svn: 58358

 - No functionality change.

llvm-svn: 58355

Don't force things to be Value * when they're not.

llvm-svn: 58354

 - No functionality change.

llvm-svn: 58352

llvm-svn: 58351

EnableFastISelAbort variables for Release mode instead of
using ifdefs in the code.

llvm-svn: 58350

llvm-svn: 58345

 - One functionality change, '\\' in a name is now printed as a hex
   escape instead of "\\\\". This is consistent with other users of
   PrintEscapedString.

llvm-svn: 58343

llvm-svn: 58340

llvm-svn: 58339

Since the ARM constant pool handling supercedes the standard LLVM constant
pool entirely, the JIT emitter does not allocate space for the constants,
nor initialize the memory. The constant pool is considered part of the 
instruction stream.

Likewise, when resolving relocations into the constant pool, a hook into
the target back end is used to resolve from the constant ID# to the
address where the constant is stored.

For now, the support in the ARM emitter is limited to 32-bit integer. Future
patches will expand this to the full range of constants necessary.

llvm-svn: 58338

  virtual void print(std::ostream &O, const Module *M) const;
instead of
  virtual void print(llvm::OStream &O, const Module *M) const;
as the docs say

llvm-svn: 58337

Avoid calls to setSubgraphColor in release mode. They generate lots of error messages and slow down compilation.

llvm-svn: 58336

llvm-svn: 58335

llvm-svn: 58332

ppcf128 to i32 conversion and expand it into a code
sequence like in LegalizeDAG.  This needs custom
ppc lowering of FP_ROUND_INREG, so turn that on and
make it work with LegalizeTypes.  Probably PPC should
simply custom lower the original conversion.

llvm-svn: 58329

moment, while waiting for a proper solution.

llvm-svn: 58324

id could end up being wrong mostly because of
forgetting to remap new nodes that morphed into
processed nodes through CSE.

llvm-svn: 58323

llvm-svn: 58320

llvm-svn: 58319

llvm-svn: 58318

a memset using 16-byte XMM stores, but where the stack realignment code
didn't work.  Until it does (PR2962) disable use of xmm regs in memcpy
and memset formation for linux and other targets with insufficiently
aligned stacks.

This is part of PR2888

llvm-svn: 58317

llvm-svn: 58316

llvm-svn: 58315

llvm-svn: 58314

llvm-svn: 58312

llvm-svn: 58310

Avoid putting a split past the end of the live range; always shrink wrap live interval in the barrier mbb.

llvm-svn: 58309

- Add VERBOSE=1 flag.
- Specify the LLVM_SUBMIT_VERSION when doing the "make install".
  The libLTO.dylib relies upon this flag during that time.

llvm-svn: 58298

llvm-svn: 58297

Re-apply 55137 with fixes.

llvm-svn: 58296

llvm-svn: 58294

llvm-svn: 58290

Have TableGen emit setSubgraphColor calls under control of a -gen-debug
flag.  Then in a debugger developers can set breakpoints at these calls
to see waht is about to be selected and what the resulting subgraph
looks like.  This really helps when debugging instruction selection.

llvm-svn: 58278

llvm-svn: 58268

llvm-svn: 58263