Hi, On Thu, Jan 13, 2005 at 04:56:58PM +0100, Andy Polyakov via RT wrote: > > So indeed, this seems to be a gcc (3.3.3) optimization error. Is there > > a way to make OpenSSL auto-disable "-O3" for specific crypto/... modules > > if its known that they fail on specific platforms? > > No. BTW, if it enough to drop to -O2 or do you have to -O0?
-O2 is not sufficient (-> rmdtest fails). > Can you test if './config -DMD32_REG_T=int' does the trick? Yes! This makes rmdtest work with -O3. > > If yes, the NetBSD > > pkgsrc module could just enable this... > > > > PS: sorry that I forgot "make report" last time, here it is: [..] > > OS (config): sparc64-whatever-netbsd > > Target (default): NetBSD-sparc > > Target: NetBSD-sparc > > Just NetBSD-sparc? When gcc spits out 64-bit objects? You're more than > likely to suffer from http://www.openssl.org/support/faq.html#BUILD11. Uh, well, what shall I say? There are linux-sparc64 and solaris-sparc64 targets, but no NetBSD-sparc64... (and I consider myself mostly "user" on Sparc64 yet). > NetBSD should have contributed NetBSD-sparc64 target with appropriate > flags... A. The NetBSD pkgsrc tree has patch for the netbsd-sparc64 target, but using that failed with interesting MD5-assembly error codes. This is what got me started here - I opened a bug vs. NetBSD, they fixed the MD5 thing, and then we discovered that the upstream sources also have the ripemd problems. The NetBSD pkg maintainer (Jonny Lam) has just commited a new set of patches that fix building on Sparc64 for good :-) - maybe you could just incoprorate them (dunno what the NetBSD patch copyright policy is, though)? gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany [EMAIL PROTECTED] fax: +49-89-35655025 [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [EMAIL PROTECTED]
