Initial support for icc appears first in ftp://ftp.openssl.org/snapshot/openssl-SNAP-20030103.tar.gz. To configure run './Configure linux-ia32-icc'. Auto-detection in ./config will be added at some later point.
As already mentioned it's fruitless to count on libimf.a, as it's a floating point library, while OpenSSL toolkit is purely interger intensive. Not even Intel C compiler beats handcoded assembler implementations(*), therefore linux-ia32-icc is naturally assembler empowered. PKI operations on shorter keys do get few percents faster thanks to better optimized bn_mont.c. Intel C generates much better position independent code. In cases when gcc-generated code surrenders almost 50% with -fPIC, icc surrenders maybe 5-10%. But there're no miracles(*). Pretty much as expected... I'm closing this ticket. If anybody feels like discussing the matter in more details, subscribe and post to <[EMAIL PROTECTED]>. A. (*) There is an exception. icc manages to generate faster SHA-1 code, faster than handcoded assmembler that is. This means that SHA-1 assembler implementation needs a "face lift." Volunteers:-) ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
