llvm-svn: 81923

llvm-svn: 81915

Intel tables, where the source operand is
specified by the R/M field and the destination
operand by the Reg field.

llvm-svn: 81914

 - As best I can tell, we have eliminated all the code which used to require a
   larger buffer size.

llvm-svn: 81912

llvm-svn: 81911

llvm-svn: 81910

llvm-svn: 81909

is a site configuration.

llvm-svn: 81902

Better solution for tracking both the original alignment of the access, and the current alignment based
on the source value offset.  This avoids increasing the size of mem nodes. 

llvm-svn: 81897

llvm-svn: 81896

to the Intel register table.
Added 16- and 64-bit MOVs to and from the segment
registers to the Intel instruction tables.

llvm-svn: 81895

interrupt instruction, which shouldn't arise any other way).  0xcd is
also used by JITMemoryManager to initialize the buffer to garbage,
which means it could appear following a noreturn call even when
that is not a stub, confusing X86CompilationCallback2.  PR 4929.

llvm-svn: 81888

values to machineinstrs.

llvm-svn: 81886

llvm-svn: 81884

llvm-svn: 81882

llvm-svn: 81881

VLDM/VSTM instructions, and without this check, the code assumes that an
offset is allowed, as it would be with VLDR/VSTR.  The asm printer,
however, silently drops the offset, producing incorrect code.  Since the
address register in this case is either the stack or frame pointer, the
spill location ends up conflicting with some other stack slot or with
outgoing arguments on the stack.

llvm-svn: 81879

llvm-svn: 81878

and PIC codegen.  Patch by Venkatraman Govindaraju!

llvm-svn: 81877

not folded in the constant folder because the constant folder doesn't
simplify ConstantExpr operands.

llvm-svn: 81864

llvm-svn: 81862

instead of cloning and RAUWing it.

 - Make AbstractTypeUser a friend of Value so that it can offer
   its subclasses a way to update a Value's type in place. This
   is better than a universally visible setType method on Value,
   and it's sufficient for the immediate need.

 - Eliminate the constant "convert" functions. This eliminates a
   lot of logic duplication, and fixes a complicated bug where a
   constant can't actually be cloned during the type refinement
   process because some of the types that its folder needs are
   half-destroyed, being in the middle of refinement themselves.

 - Move the getValType functions from being static overloaded
   functions in Constants.cpp to be members of class template
   specializations in ConstantsContext.h. This means that the
   code ends up getting instantiated twice, however it also
   makes it possible to eliminate all "convert" functions, so
   it's not a big net code size increase. And if desired, the
   duplicate instantiations could be eliminated with some
   reorganization.

llvm-svn: 81861

llvm-svn: 81860

llvm-svn: 81859

llvm-svn: 81858

llvm-svn: 81857

llvm-svn: 81856

llvm-svn: 81851

llvm-svn: 81850

Another try at early partial coalescing. Identity phi source copies (their sources are defined by phi join def) are coalesced. And the phi join copy is backward copy propagated into the other copies.

Still miscompiling some tests. :-(

llvm-svn: 81849

llvm-svn: 81848

While I'm there, change code that does:
  SomeTy == Type::getFooType(Context)
into:
  SomeTy->getTypeID() == FooTyID
to decrease the amount of useless type creation which may involve locking, etc.

llvm-svn: 81846

an unpacked one.

llvm-svn: 81845

argpromote to avoid invalidating an iterator.  This fixes PR4977.
All clang tests now pass with expensive checking (on my system 
at least).

llvm-svn: 81843

llvm-svn: 81840

are in the SCC for each execution of a CGSCC pass.

llvm-svn: 81838

llvm-svn: 81836

llvm-svn: 81834

llvm-svn: 81833

llvm-svn: 81827