[llvm-commits] CVS: llvm/lib/Target/X86/README.txt

[Evan Cheng]

Changes in directory llvm/lib/Target/X86:

README.txt updated: 1.76 -> 1.77
---
Log message:

Update

---
Diffs of the changes:  (+2 -23)

 README.txt |   25 ++-----------------------
 1 files changed, 2 insertions(+), 23 deletions(-)


Index: llvm/lib/Target/X86/README.txt
diff -u llvm/lib/Target/X86/README.txt:1.76 llvm/lib/Target/X86/README.txt:1.77
--- llvm/lib/Target/X86/README.txt:1.76	Mon Mar 27 20:49:12 2006
+++ llvm/lib/Target/X86/README.txt	Tue Mar 28 00:55:45 2006
@@ -665,26 +665,5 @@
 
 //===---------------------------------------------------------------------===//
 
-Is it really a good idea to use movlhps to move 1 double-precision FP value from
-low quadword of source to high quadword of destination?
-
-e.g.
-
-void test2 (v2sd *b, double X, double Y) {
-  v2sd a = (v2sd) {X, X*Y};
-  *b = a;
-}
-
-	movsd 8(%esp), %xmm0
-	movapd %xmm0, %xmm1
-	mulsd 16(%esp), %xmm1
-	movlhps %xmm1, %xmm0
-	movl 4(%esp), %eax
-	movapd %xmm0, (%eax)
-	ret
-
-icc uses unpcklpd instead.
-
-//===---------------------------------------------------------------------===//
-
-Use movhps and movlhps to update upper 64-bits of a v4sf value.
+Use movhps to update upper 64-bits of a v4sf value. Also movlps on lower half
+of a v4sf value.