> You asked when, specifically, Purify stretches code. > > Best case (on SPARC) is that we insert two instructions before each load > or store.
In other words all the time. > Regarding the patch you referred to > (http://cvs.openssl.org/chngview?cn=17898): I'm sorry to say Purify is not > as flexible as you might want. http://cvs.openssl.org/chngview?cn=17902. > Thanks for working with us on this. Let me know if you have more thoughts > or questions. Are there any similar issues to be aware of on other platforms? Presumably there hardly are problems with x86[_64], but what about PPC? In particular could you examine http://cvs.openssl.org/fileview?f=openssl/crypto/aes/asm/aes-ppc.pl&v=1.8 and http://cvs.openssl.org/fileview?f=openssl/crypto/sha/asm/sha512-ppc.pl&v=1.6. In former there are LAES_Te and LAES_Td subroutines in the beginning and in latter - LPICmeup closer to the end. A lot of thanks in advance. A. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
