llvm-svn: 34302

Change use of "packed" term to "vector" in comments, strings, variable
names, etc.

llvm-svn: 34300

Rename PackedType -> VectorType, ConstantPacked -> ConstantVector, and
PackedTyID -> VectorTyID. No functional changes.

llvm-svn: 34293

llvm-svn: 34272

this doesn't miscompile lots of programs :)

llvm-svn: 34268

Patch by Scott Michel.

llvm-svn: 34266

be supported on 32-bit hosts.

llvm-svn: 34257

llvm-svn: 34256

This will break a dj test until I have time to investigate.

llvm-svn: 34247

llvm-svn: 34244

llvm-svn: 34240

llvm-svn: 34223

registers. Make sure liveinterval analysis is correctly creating live ranges
for them.

llvm-svn: 34217

comparisons.  This fixes an infinite loop on CodeGen/Generic/switch-lower.ll
and PR1197

llvm-svn: 34216

llvm-svn: 34161

llvm-svn: 34157

llvm-svn: 34156

llvm-svn: 34112

llvm-svn: 34111

llvm-svn: 34110

llvm-svn: 34066

llvm-svn: 34065

The code sequence before the spiller is something like:
                 = tMOVrr
        %reg1117 = tMOVrr
        %reg1078 = tLSLri %reg1117, 2

The it starts spilling:
        %r0 = tRestore <fi#5>, 0
        %r1 = tRestore <fi#7>, 0
        %r1 = tMOVrr %r1<kill>
        tSpill %r1, <fi#5>, 0
        %reg1078 = tLSLri %reg1117, 2

It restores the value while processing the first tMOVrr. At this point, the
spiller remembers fi#5 is available in %r0. Next it processes the second move.
It restores the source before the move and spills the result afterwards. The
move becomes a noop and is deleted. However, a spill has been inserted and that
should invalidate reuse of %r0 for fi#5 and add reuse of %r1 for fi#5.
Therefore, %reg1117 (which is also assigned fi#5) should get %r1, not %r0.

llvm-svn: 34039

do some common stuff, then on our own add an object file writer (by calling
a concrete function), and then do some finishing stuff, if need be.

llvm-svn: 34032

llvm-svn: 34031

llvm-svn: 34027

based on the alignment of the symbol and the target data's preferred align
for that type.

Also, rename some arguments for consistency.

llvm-svn: 33984

1. Memset takes an i32 for the value to set, not i8.  This was causing GCC to
   ICE all over the place (PR1183).
2. memcpy/memmove were not properly zext/trunc'ing the size in some cases.

llvm-svn: 33970

llvm-svn: 33957

llvm-svn: 33946

llvm-svn: 33924

llvm-svn: 33888

speeds up the isel pass from 2.5570s to 2.4722s on kc++ (3.4%).

llvm-svn: 33879

their operands with the node itself.  This reduces malloc traffic for operand
lists.  This reduces isel time on kc++ from 2.6164 to 2.5570s, about 2.3%.

llvm-svn: 33878

llvm-svn: 33876

llvm-svn: 33875

no behavior or performance change here.

llvm-svn: 33869

llvm-svn: 33868

llvm-svn: 33867

llvm-svn: 33866