[PATCH] Fix build of jitterentropy-base.c with clang v2

[Stephan Mueller]

Am Montag, den 23.11.2020, 16:58 -0800 schrieb Tom Stellard via Gcrypt-devel:
> On 8/3/20 2:35 AM, Werner Koch wrote:
> > Hi!

Hi,
> > 
> > Thanbks for the patch.  However the problem is that it is too easy to
> > build with optimization - there really should be an #error in case
> > optimization is accidently enabled (broken pragma etc.).  Do you know a
> > macro or other mechanism in Clang so that we can check that optimization
> > has been disabled?
> > 
> 
> I don't know of any other way to check if optimizations are disabled. 
> Is the goal with the check to prevent someone accidentally removing the 
> pragma?

Just as a side note: I am in the process of finishing up version 3.0 of the
Jitter RNG code base. This now is able to run with full optimizations and has
a fallback if no high-res timer is available.

It is also SP800-90B compliant.

Ciao
Stephan
> 
> -Tom
> 
> > 
> > Shalom-Salam,
> > 
> >     Werner
> > 
> 
> 
> _______________________________________________
> Gcrypt-devel mailing list
> Gcrypt-devel at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gcrypt-devel