Re: [openssl-dev] Making assembly language optimizations working onCortex-M3

> The BoringSSL works as follows: > > 1. The person building the code passes -DOPENSSL_STATIC_ARMCAP and some > other flags like -DOPENSSL_STATIC_ARMCAP_NEON, to indicate which > features are available on the target. > > 2. When OPENSSL_STATIC_ARMCAP is defined, the runtime detection of >

Re: [openssl-dev] Making assembly language optimizations working onCortex-M3

> That's usually true, but the topic of this thread is about how to get OpenSSL > working well on Cortex-M microcontrollers. In those situations, we cannot > really afford the dynamic detection or the many different implementations of > the same algorithm to exist in the final image. Other

Re: [openssl-dev] Making assembly language optimizations working onCortex-M3

That may not be a good idea. The vast majority of OpenSSL in use isn't targetted at a specific processor variant. It's compiled by an OS vendor and then installed on whatever. IF you are in the situation where you are compiling for a space constrained embedded processor then hopefully your

Re: [openssl-dev] Making assembly language optimizations working onCortex-M3

Peter Waltenberg wrote: > IF you are in the situation where you are compiling for a space > constrained embedded processor then hopefully your engineers also have > enough smarts to fix the code. I'd also point out that a lot of dev. setups > for embedded aren't actually