| commit | 501bddf177275d87a46f7a659aa3a0b0d85ee4c8 | |
| author | Olly Betts <olly@survex.com> | |
| Wed, 16 Aug 2023 04:51:11 +0000 (16 16:51 +1200) | ||
| committer | Olly Betts <olly@survex.com> | |
| Wed, 16 Aug 2023 04:57:43 +0000 (16 16:57 +1200) | ||
| tree | add98b89bf15d1e4f5e09e69d26f324cfacd8a9e | treesnapshot (tar.gz zip) |
| parent | c75952cf14b3943c94315c4887223c750cd923cd | commitdiff |
Allow using UBSan's unsigned-overflow check
In C and C++ unsigned overflow has defined behaviour (unlike signed
overflow) but in many cases it happening is not intended and indicates
a bug.
UBSan supports an unsigned-overflow check (at least the clang version
does - currently the GCC version doesn't seem to) so I've annotated the
few places in the code where we deliberately rely on unsigned overflow
(and eliminated a few cases where we can easily not rely on it) and
added this check to the clang-sanitisers job.
In C and C++ unsigned overflow has defined behaviour (unlike signed
overflow) but in many cases it happening is not intended and indicates
a bug.
UBSan supports an unsigned-overflow check (at least the clang version
does - currently the GCC version doesn't seem to) so I've annotated the
few places in the code where we deliberately rely on unsigned overflow
(and eliminated a few cases where we can easily not rely on it) and
added this check to the clang-sanitisers job.
41 files changed: