> $ ./config -fsanitize=undefined Sanitized builds might have to be complemented with -DPEDANTIC. Quoting Configure:
# ... Incidentally -DPEDANTIC has # to be used even in sanitized builds, because sanitizer too is # supposed to and does take notice of non-standard behaviour. Similar rule applies to cases when you try to pass harder standard compliance flags like you discussed in other RTs. Bottom line is that while it's possible to pass additional compiler flags to ./config, it doesn't mean that arbitrary combination is guaranteed to work. Sanitized builds are exercised through travis-ci.org and you can find find the flags in .travis.yml. > ... > $ make test HARNESS_VERBOSE=yes > ... > > ../test/recipes/05-test_cast.t ............ > 1..1 > crypto/cast/c_enc.c:78:5: runtime error: shift exponent 32 is too > large for 32-bit type 'unsigned int' Though this particular code was modified to pass sanitized independent on -DPEDANTIC. I'm closing this ticket. -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4463 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
