From: Nate Begeman Date: Fri, 9 Feb 2007 04:19:54 +0000 (+0000) Subject: Remove fixed item X-Git-Url: http://plrg.eecs.uci.edu/git/?a=commitdiff_plain;h=8c541bcc56fd7327f3d8d74653ae6df25921250e;p=oota-llvm.git Remove fixed item git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@34081 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/lib/Target/PowerPC/README.txt b/lib/Target/PowerPC/README.txt index 2114fde89a1..a615b7ef6df 100644 --- a/lib/Target/PowerPC/README.txt +++ b/lib/Target/PowerPC/README.txt @@ -265,32 +265,6 @@ This could be done in the dag combiner, by swapping a BR_CC when a SETCC of the same operands (but backwards) exists. In this case, this wouldn't save us anything though, because the compares still wouldn't be shared. -===-------------------------------------------------------------------------=== - -The legalizer should lower this: - -bool %test(ulong %x) { - %tmp = setlt ulong %x, 4294967296 - ret bool %tmp -} - -into "if x.high == 0", not: - -_test: - cntlzw r2, r3 - xori r3, r3, 1 - cmplwi cr0, r3, 0 - srwi r2, r2, 5 - li r3, 0 - beq cr0, LBB1_2 ;entry -LBB1_1: ;entry - mr r3, r2 -LBB1_2: ;entry - blr - -noticed in 2005-05-11-Popcount-ffs-fls.c. - - ===-------------------------------------------------------------------------=== We should custom expand setcc instead of pretending that we have it. That