It's possible that because no one had a PPC machine running BSD to test the asm paths they were left disabled.
There may be other reasons, but make tests should at least show any gross problems.
The only subtle problem I can think of that might be there in recent code is use of 64 bit registers in 32 bit code, if the kernel doesn't preserve the upper halves of registers you can get clobbered during signal handling. I don't know enough about current BSD to know if that's a problem or not.
Peter
-----owner-openssl-...@openssl.org wrote: -----
To: openssl-dev <openssl-dev@openssl.org>
From: Kevin Fowler
Sent by: owner-openssl-...@openssl.org
Date: 08/04/2012 01:04AM
Subject: ppc32_asm for BSD targets
For the BSD-generic32 target, which gets used for *bsd on ppc cpu, Configure script uses ${no_asm}. Other OS's (linux, darwin, AIX) on ppc cpu use ${ppc32_asm}.
From: Kevin Fowler
Sent by: owner-openssl-...@openssl.org
Date: 08/04/2012 01:04AM
Subject: ppc32_asm for BSD targets
For the BSD-generic32 target, which gets used for *bsd on ppc cpu, Configure script uses ${no_asm}. Other OS's (linux, darwin, AIX) on ppc cpu use ${ppc32_asm}.
Are the ppc asm routines not valid for *bsd OS? If so, what about BSD invalidates them?
Thanks,
Kevin
