The GNUmakefile now has the following logic. It warns if it finds CRYPTOPP_NO_UNALIGNED_DATA_ACCESS in the config file and its commented out.
Disabling or not allowing unaligned data access ensures we don't introduce C/C++ undefined behavior or violate GCC's aliasing rules. However, its a somewhat drastic change. To remediate the warning: * uncomment CRYPTOPP_NO_UNALIGNED_DATA_ACCESS * delete "// #define CRYPTOPP_NO_UNALIGNED_DATA_ACCESS" I'm fairly certain its important that we warn about it *if* we are not going to fix it. However, the option to delete the comment altogether to suppress the warning gives the user a choice. That is, they can dispatch the warning and run with the undefined behavior, if they choose. ################################################################# # Public service announcement # Do not warn for some targets NO_WARN = GNUmakefile.deps dist install install-strip uninstall remove clean distclean ifeq ($(findstring $(MAKECMDGOALS),$(NO_WARN)),) UNALIGNED_ACCESS = $(shell $(EGREP) -c "^// \#define CRYPTOPP_NO_UNALIGNED_DATA_ACCESS" config.h) ifneq ($(UNALIGNED_ACCESS),0) $(info WARNING: CRYPTOPP_NO_UNALIGNED_DATA_ACCESS is not defined in config.h) endif endif # NO_WARN -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
