mirror of
https://github.com/bytecodealliance/wasm-micro-runtime.git
synced 2026-03-14 15:48:46 +00:00
9e4aa9c850
* fix: disable unsigned integer overflow sanitization in build configurations
FYI: from https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html
`-fsanitize=unsigned-integer-overflow`: Unsigned integer overflow, where the result of an unsigned integer computation cannot be represented in its type. Unlike signed integer overflow, this is not undefined behavior, but it is often unintentional. This sanitizer does not check for lossy implicit conversions performed before such a computation.
It brings a more common question: which is better, pre-additional-check or post-additional-check to fix a potential unsigned integer overflow? A pre-additional-check involves using a check to prevent integer overflow from the very beginning. A post-additional-check involves using a check after addition to see if there is an overflow.
In this project, post-additional-checking is widely used. let's follow the routine.
for performance sensitive logic, use __builtin_add_overflow etc. provide something like
|
||
|---|---|---|
| .. | ||
| benchmarks | ||
| fuzz/wasm-mutator-fuzz | ||
| malformed | ||
| regression/ba-issues | ||
| requirement-engineering | ||
| standalone | ||
| unit | ||
| wamr-compiler | ||
| wamr-test-suites | ||