Re: [Fwd: Inconsistency in ARM support]

2014-11-10 Thread Ard Biesheuvel
On 8 November 2014 17:56, Andy Polyakov ap...@openssl.org wrote: arm-linux-gnueabi-gcc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -D__ARM_MAX_ARCH__=8 -DTERMIO -O3 -Wall -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m

Re: [Fwd: Inconsistency in ARM support]

2014-11-10 Thread Ard Biesheuvel
On 10 November 2014 17:12, Andy Polyakov ap...@openssl.org wrote: Attached is promised patch that reworks interworking logic. As mentioned earlier idea is to use __ARM_ARCH__=5 || !defined(__thumb__). Rationale is that load to pc does interworking since ARMv5, but without __thumb__ it does

Re: [Fwd: Inconsistency in ARM support]

2014-11-06 Thread Ard Biesheuvel
On 3 November 2014 18:36, Andy Polyakov ap...@openssl.org wrote: Anyway. As nobody seems to be objecting, it sounds like we are going for combination of both alternatives? I.e. those who specify specific -march lower than armv7 would be excused from capability detection and run-time switch,

Re: [Fwd: Inconsistency in ARM support]

2014-11-04 Thread Ard Biesheuvel
On 31 October 2014 18:12, Andy Polyakov ap...@openssl.org wrote: Anyway. As nobody seems to be objecting, it sounds like we are going for combination of both alternatives? I.e. those who specify specific -march lower than armv7 would be excused from capability detection and run-time switch,

Re: [Fwd: Inconsistency in ARM support]

2014-10-28 Thread Ard Biesheuvel
On 27 October 2014 21:42, Andy Polyakov ap...@openssl.org wrote: OK, that sounds doable. But if -Wa is going to be used as a matter of course to pass arch/fpu options, we should get rid of all #ifdef's against things like __thumb2__, as they can be out of sync. First of all users would have

Re: [Fwd: Inconsistency in ARM support]

2014-10-27 Thread Ard Biesheuvel
On 26 October 2014 22:43, Andy Polyakov ap...@openssl.org wrote: Hi, There is inconsistency in ARM support and I'd like to gather some opinions on how to resolve it. Circulate this to ARM people near you. At some point an inconsistency of following nature was introduced and then just grew.

Re: [Fwd: Inconsistency in ARM support]

2014-10-27 Thread Ard Biesheuvel
On 27 October 2014 15:11, Andy Polyakov ap...@openssl.org wrote: I want to remind that question is *not* about removing run-time switch as concept, but rather about distinguishing pre-ARMv7 and ARMv=7. I.e. NEON/cryto switch will stay, the only question if it's worth imposing it on pre-ARMv7

Re: [Fwd: Inconsistency in ARM support]

2014-10-26 Thread Ard Biesheuvel
On 24 October 2014 19:17, Andy Polyakov ap...@openssl.org wrote: There is inconsistency in ARM support and I'd like to gather some opinions on how to resolve it. Circulate this to ARM people near you. At some point an inconsistency of following nature was introduced and then just grew.