n integral constant appropriate for your platform.
There's really no need for it to be floating-point. Oh well.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
On 8/11/2016 11:20 AM, Short, Todd wrote:
In such a case, I suggest #ifdef’ing out the code that you don’t care
about, and making it into a configuration option, the submitting a patch
for it.
I wouldn't go near deciding what "I don't care about". There is history
to non-experts #ifdef'ing
The -Ddouble=long hack might very well cause problems with standard headers.
I’m assuming you are not talking about x86 or any other platform for which
there is assembly support.
In such a case, I suggest #ifdef’ing out the code that you don’t care about,
and making it into a configuration
(Top posting for consistency in this part of the thread)
Note, however that emulated floating point tends to add code
size and startup overhead even when not called.
Hence the need to compile with an option to not use floating
point at all, at least on platforms that don't have platform-
This is compiler-dependent, and because you didn't specify what platform
you're targeting or what compiler you're using, there's no way for us to
provide an answer. Check your compiler's documentation. GCC, for example,
provides software-emulated floating point for platforms without hardware
that uses an alternative to floating
> point?
-Ddouble=long
? :)
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
We have a platform that does not support floating point operations. We
discovered that openssl uses floating point in the random number
generator.
Is there any build or compile time flag that uses an alternative to
floating point?
--
Ken Goldman kgold...@us.ibm.com
914-945-2415 (862-2415)
