llvm-svn: 24662

llvm-svn: 24661

llvm-svn: 24660

llvm-svn: 24659

FP select improvements (and likely breakage), oh and crazy people might want to *return* floating point values.  Don't see why myself

llvm-svn: 24658

them in the PPC backend, to simplify some logic out of Select and
SelectAddr.

llvm-svn: 24657

llvm-svn: 24656

llvm-svn: 24655

* Added X86 dec patterns.

llvm-svn: 24654

llvm-svn: 24653

llvm-svn: 24652

hopefully use patterns in the near future.

llvm-svn: 24651

must be a pointer.  This removes a type check out of the code generated by
tblgen for load matching.

llvm-svn: 24650

the same type as the pointer type for a target.

llvm-svn: 24649

llvm-svn: 24648

  it has more than one real use (non-chain uses).
* Record folded chain producing node in CodeGenMap.
* Do not fold a chain producing node if it has already been selected as an
  operand of a chain use.

llvm-svn: 24647

llvm-svn: 24646

linking the entire program into one bc file.

llvm-svn: 24645

out to me.

llvm-svn: 24644

llvm-svn: 24643

functions can return false and causing the instruction pattern match to fail.
* Code clean up.

llvm-svn: 24642

llvm-svn: 24641

1. Only forward subst offsets into loads and stores, not into arbitrary
   things, where it will likely become a load.
2. If the source is a cast from pointer, forward subst the cast as well,
   allowing us to fold the cast away (improving cases when the cast is
   from an alloca or global).

This hasn't been fully tested, but does appear to further reduce register
pressure and improve code.  Lets let the testers grind on it a bit. :)

llvm-svn: 24640

llvm-svn: 24639

llvm-svn: 24638

llvm-svn: 24637

* Renamed MatchingNodes to RootNodes.

llvm-svn: 24636

false if the match is not profitable. e.g. leal 1(%eax), %eax.
* Added patterns for X86 integer loads and LEA32.

llvm-svn: 24635

matching code that is not currently auto-generated by tblgen, e.g. X86
addressing mode. Selection routines for complex patterns can return multiple operands, e.g. X86 addressing mode returns 4.

llvm-svn: 24634

type when the target did not support them.  Also teach Legalize how to
expand ConstantVecs.

This allows us to generate

_test:
        lwz r2, 12(r3)
        lwz r4, 8(r3)
        lwz r5, 4(r3)
        lwz r6, 0(r3)
        addi r2, r2, 4
        addi r4, r4, 3
        addi r5, r5, 2
        addi r6, r6, 1
        stw r2, 12(r3)
        stw r4, 8(r3)
        stw r5, 4(r3)
        stw r6, 0(r3)
        blr

For:

void %test(%v4i *%P) {
        %T = load %v4i* %P
        %S = add %v4i %T, <int 1, int 2, int 3, int 4>
        store %v4i %S, %v4i * %P
        ret void
}

On PowerPC.

llvm-svn: 24633

if the target supports the resultant sextinreg

llvm-svn: 24632

llvm-svn: 24631

when the types match up.  This allows the X86 backend to compile:

sbyte %toggle_value(sbyte* %tmp.1) {
        %tmp.2 = load sbyte* %tmp.1
        ret sbyte %tmp.2
}

to this:

_toggle_value:
        mov %EAX, DWORD PTR [%ESP + 4]
        movsx %EAX, BYTE PTR [%EAX]
        ret

instead of this:

_toggle_value:
        mov %EAX, DWORD PTR [%ESP + 4]
        movsx %EAX, BYTE PTR [%EAX]
        movsx %EAX, %AL
        ret

noticed in Shootout/objinst.

-Chris

llvm-svn: 24630

llvm-svn: 24629

llvm-svn: 24628

llvm-svn: 24627

This solves the problem of the CBE renaming symbols that start with . but the assembly side still trying to reference them by their old names.  Should be safe untill we hit a language front end that lets you specify such a name.

llvm-svn: 24626

more decent branches for FP.  I might have to make some intermediate nodes to actually be able to use the DAG for FPcmp

llvm-svn: 24625

llvm-svn: 24624

llvm-svn: 24623