> >> sparc.s is one of those gcc-produced files (which is also why
> >> solaris-sparc-gcc does not use it); but crypto/bn/bn_mulw.c is just an
> >
> > gcc hasn't produced better code that Sun's cc for SPARC in eternities. If we
> > want to distribute fast crypto routines, we should either hand-create them,
> > let the compiler do it, or actually benchmark code.
> >
> > The current situation is broken and needs to be fixed.
>
> O.K. Then I propose deleting (rather then recreating) all those
> automatically generated assembler versions, with appropriate changes
> to the configuration script.
i don't get it! has anybody read my posts? does it get through at all?
well, it must, because i myself get my messages echoed back from the
list...
andy.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
