llvm-svn: 43751

llvm-svn: 43749

llvm-svn: 43745

llvm-svn: 43744

llvm-svn: 43743

Thanks for the suggestions Bill :-)

llvm-svn: 43742

Added detection of end-of-stream in deserializer.

llvm-svn: 43736

parameters.  Rename ValueRefList to ParamList
in AsmParser, since its only use is for parameters.

llvm-svn: 43734

llvm-svn: 43732

If a value is incoming from outside the loop then the value does not need remapping and the value is never tracked through  LastValueMap.

llvm-svn: 43728

static __thread struct {
    int a;
    int b;
} teste = {0, 0};

llvm-svn: 43722

size for the field we get ABI padding automatically, so
no need to put it in again when we emit the field.

llvm-svn: 43720

register coalescer interface: RegisterCoalescing.

llvm-svn: 43714

less than 16. This is a temporary solution until dynamic stack alignment is
implemented.

llvm-svn: 43703

llvm-svn: 43700

defined on the same instruction. This fixes PR1767.

llvm-svn: 43699

Removed all macro code for PIC (goodbye "la").
Support tested with shootout bench.

llvm-svn: 43697

llvm-svn: 43694

llvm-svn: 43692

that there is no padding.

llvm-svn: 43691

should only effect x86 when using long double.  Now
12/16 bytes are output for long double globals (the
exact amount depends on the alignment).  This brings
globals in line with the rest of LLVM: the space
reserved for an object is now always the ABI size.
One tricky point is that only 10 bytes should be
output for long double if it is a field in a packed
struct, which is the reason for the additional
argument to EmitGlobalConstant.

llvm-svn: 43688

llvm-svn: 43684

llvm-svn: 43683

Evan, please review this.

llvm-svn: 43680

llvm-svn: 43676

Also cleaned up some comments in source files.

llvm-svn: 43674

or getTypeSizeInBits as appropriate in ScalarReplAggregates.
The right change to make was not always obvious, so it would
be good to have an sroa guru review this.  While there I noticed
some bugs, and fixed them: (1) arrays of x86 long double have
holes due to alignment padding, but this wasn't being spotted
by HasStructPadding (renamed to HasPadding).  The same goes
for arrays of oddly sized ints.  Vectors also suffer from this,
in fact the problem for vectors is much worse because basic
vector assumptions seem to be broken by vectors of type with
alignment padding.   I didn't try to fix any of these vector
problems.  (2) The code for extracting smaller integers from
larger ones (in the "int union" case) was wrong on big-endian
machines for integers with size not a multiple of 8, like i1.
Probably this is impossible to hit via llvm-gcc, but I fixed
it anyway while there and added a testcase.  I also got rid of
some trailing whitespace and changed a function name which
had an obvious typo in it.

llvm-svn: 43672

If an interval is being undone clear its preference as well since the source interval may have been undone as well.

llvm-svn: 43670

regs on x86-64.

llvm-svn: 43669

metric is way off for these in general, and this works around
buggy code like that in PR1764.  we'll see if there is a big
performance impact of this.  If so, I'll revert it tomorrow.

llvm-svn: 43668

can be eliminated by the allocator is the destination and source targets the
same register. The most common case is when the source and destination registers
are in different class. For example, on x86 mov32to32_ targets GR32_ which
contains a subset of the registers in GR32.

The allocator can do 2 things:
1. Set the preferred allocation for the destination of a copy to that of its source.
2. After allocation is done, change the allocation of a copy destination (if
   legal) so the copy can be eliminated.

This eliminates 443 extra moves from 403.gcc.

llvm-svn: 43662

llvm-svn: 43652

llvm-svn: 43651

llvm-svn: 43646

llvm-svn: 43644

llvm-svn: 43642

llvm-svn: 43639

Restore an assertion that arithmetic can be performed on this format.

llvm-svn: 43638

llvm-svn: 43630

llvm-svn: 43627