Very few in the "README" is up-to-date

[openssl.git] / crypto / bn / asm / README

diff --git a/crypto/bn/asm/README b/crypto/bn/asm/README
index d93fbff77f5feff243558e6d50dac5bd083e3ed7..b0f3a68a06abee1b8cefe83f7a9e31679e449d1a 100644 (file)
--- a/crypto/bn/asm/README
+++ b/crypto/bn/asm/README
@@ -1,5 +1,7 @@
+<OBSOLETE>
+
 All assember in this directory are just version of the file
-crypto/bn/bn_mulw.c.
+crypto/bn/bn_asm.c.
 
 Quite a few of these files are just the assember output from gcc since on 
 quite a few machines they are 2 times faster than the system compiler.
@@ -15,16 +17,11 @@ On the 2 alpha C compilers I had access to, it was not possible to do
 were 64 bits).  So the hand assember gives access to the 128 bit result and
 a 2 times speedup :-).
 
-The x86xxxx.obj files are the assembled version of x86xxxx.asm files.
-I had such a hard time finding a macro assember for Microsoft, I decided to
-include the object file to save others the hassle :-).
+There are 3 versions of assember for the HP PA-RISC.
+
+pa-risc.s is the origional one which works fine and generated using gcc :-)
 
-I have also included uu encoded versions of the .obj incase they get
-trashed.
+pa-risc2W.s and pa-risc2.s are 64 and 32-bit PA-RISC 2.0 implementations
+by Chris Ruemmler from HP (with some help from the HP C compiler).
 
-There are 2 versions of assember for the HP PA-RISC.
-pa-risc.s is the origional one which works fine.
-pa-risc2.s is a new version that often generates warnings but if the
-tests pass, it gives performance that is over 2 times faster than
-pa-risc.s.
-Both were generated using gcc :-)
+</OBSOLETE>