llvm-svn: 21885

llvm-svn: 21884

llvm-svn: 21883

llvm-svn: 21882

now codegen'd as this:

        addi r2, r3, -1
        andc r2, r2, r3
        cntlzw r2, r2
        subfic r3, r2, 32
        blr

llvm-svn: 21881

1. Teach LegalizeDAG how to better legalize CTTZ if the target doesn't have
   CTPOP, but does have CTLZ
2. Teach PPC32 how to do sub x, const -> add x, -const for valid consts
3. Teach PPC32 how to do and (xor a, -1) b -> andc b, a
4. Teach PPC32 that ISD::CTLZ -> PPC::CNTLZW

llvm-svn: 21880

llvm-svn: 21879

llvm-svn: 21878

llvm-svn: 21877

instructions.
Review of this commit would be greatly appreciated.

llvm-svn: 21876

with the CBE

llvm-svn: 21875

llvm-svn: 21874

looks completely untested. :(

llvm-svn: 21873

from the simple isel to the pattern isel.  This forces inserted libcalls
to serialize against other function calls, which was breaking
UnitTests/2005-05-12-Int64ToFP.  Hopefully this will fix issues on other
targets as well.

llvm-svn: 21872

llvm-svn: 21871

llvm-svn: 21870

llvm-svn: 21869

llvm-svn: 21868

This is bad.  It is generated if you are ctlz a type that is not
legal for the arch (aka ctlz of bytes on alpha legalize fine).

llvm-svn: 21867

should now pass (the "LLVM" and "REF" results should be identical)

llvm-svn: 21866

llvm-svn: 21863

llvm-svn: 21862

llvm-svn: 21861

the primary user of this will probably end up being find-first-set-bit/find-
last-set-bit, which i'll get around to...

llvm-svn: 21860

llvm-svn: 21859

llvm-svn: 21858

llvm-svn: 21857

llvm-svn: 21856

llvm-svn: 21855

llvm-svn: 21854

llvm-svn: 21853

llvm-svn: 21852

llvm-svn: 21850

llvm-svn: 21849

llvm-svn: 21848

llvm-svn: 21847

stand out as code

llvm-svn: 21846

llvm-svn: 21845

* Remove trailing whitespace
* Wrap long lines

llvm-svn: 21844

llvm-svn: 21841