From 3ce148100fc91fd4e2f2d6da5ef60b13574311c0 Mon Sep 17 00:00:00 2001
From: Julian Seward <jseward@acm.org>
Date: Wed, 13 Jun 2012 11:12:49 +0000
Subject: [PATCH] Update with recent notes.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12635
---
 docs/internals/avx-notes.txt | 20 +++++++++++++++++++-
 1 file changed, 19 insertions(+), 1 deletion(-)

diff --git a/docs/internals/avx-notes.txt b/docs/internals/avx-notes.txt
index b86843fa08..dc9f28b7ec 100644
--- a/docs/internals/avx-notes.txt
+++ b/docs/internals/avx-notes.txt
@@ -2,4 +2,22 @@
 Cleanups
 ~~~~~~~~
 
-(none at present)
+* Important: iropt: Make sure XorV128 and XorV256 of identical
+  args gets folded to zero
+
+* add more iteration in test cases
+
+* math_UNPCKxPS_128: use xIsH ? InterleaveHI32x4 : InterleaveLO32x
+  I think this is safe w.r.t. the backend
+
+* math_UNPCKxPD_128: ditto
+
+* math_UNPCKxPD_256: split into 128 bit chunks and use math_UNPCKxPD_128
+
+
+Known limitations
+~~~~~~~~~~~~~~~~~
+
+* for many (all?) of the vector shift-by-imm cases (pre-existing as
+  well as AVX), out of range shifts are not handled properly and only
+  work I think because the host happens to have the same semantics.
-- 
2.47.2