Page MenuHome GnuPG

Disable -O flag munging when the libgcrypt is not compiled with rndjent
Open, LowPublic

Description

The -O flag munging is relevant only if the jitter entropy (jent) is enabled (if I do not miss anything).

When jitter entropy support is disabled at the build time (--disable-jent-support), I would expect it should also disable the o flag munging (--disable-O-flag-munging) as it just confuses the linker and analysis tools that check what part of the binaries were built with what optimization modes.

Details

Version
master

Event Timeline

There is -O flag munging for "tiger.o" in "cipher/Makefile.am", an old workaround for broken compiler I think. IMHO tiger.o case can and should be removed.

werner added a subscriber: werner.

Not for a broken compiler but for several CC versions which consumed lots of memory for unrulling stuff. iirc, this was not only gcc.