Under some circumstances, Musashi uses too large bit-shift values. This results in undefined behaviour.
This is what the UndefinedBehaviorSanitizer (which is part of clang) reports:
The problem with undefined behaviour shouldn't be underestimated, because some modern compilers (such as clang) make use of it to aggressively optimise code. Code with undefined behaviour can behave differently when compiled with "clang -O0" or "clang -O1", respectively (even on the same machine).
Under some circumstances, Musashi uses too large bit-shift values. This results in undefined behaviour.
This is what the UndefinedBehaviorSanitizer (which is part of clang) reports:
The problem with undefined behaviour shouldn't be underestimated, because some modern compilers (such as clang) make use of it to aggressively optimise code. Code with undefined behaviour can behave differently when compiled with "clang -O0" or "clang -O1", respectively (even on the same machine).