[PATCH] Fix build of jitterentropy-base.c with clang v2
Tom Stellard
tstellar at redhat.com
Tue Nov 24 01:58:05 CET 2020
On 8/3/20 2:35 AM, Werner Koch wrote:
> 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?
-Tom
>
> Shalom-Salam,
>
> Werner
>
More information about the Gcrypt-devel
mailing list