The object-size sanitizer is redundant to -Warray-bounds, and inappropriately performs its checks at run-time when all information needed for the evaluation is available at compile-time, making it quite difficult to use: https://bugzilla.kernel.org/show_bug.cgi?id=214861 With -Warray-bounds almost enabled globally, it doesn't make sense to keep this around.
Showing the changes to scripts (1 of 3 files). Show all
Unified · Split
| @@ -8,7 +8,6 @@ ubsan-cflags-$(CONFIG_UBSAN_LOCAL_BOUNDS) += -fsanitize=local-bounds · 7 unmodified lines | |||
| 8 | ubsan-cflags-$(CONFIG_UBSAN_SHIFT) += -fsanitize=shift | 8 | ubsan-cflags-$(CONFIG_UBSAN_SHIFT) += -fsanitize=shift |
| 9 | ubsan-cflags-$(CONFIG_UBSAN_DIV_ZERO) += -fsanitize=integer-divide-by-zero | 9 | ubsan-cflags-$(CONFIG_UBSAN_DIV_ZERO) += -fsanitize=integer-divide-by-zero |
| 10 | ubsan-cflags-$(CONFIG_UBSAN_UNREACHABLE) += -fsanitize=unreachable | 10 | ubsan-cflags-$(CONFIG_UBSAN_UNREACHABLE) += -fsanitize=unreachable |
| 11 | ubsan-cflags-$(CONFIG_UBSAN_OBJECT_SIZE) += -fsanitize=object-size | ||
| 12 | ubsan-cflags-$(CONFIG_UBSAN_BOOL) += -fsanitize=bool | 11 | ubsan-cflags-$(CONFIG_UBSAN_BOOL) += -fsanitize=bool |
| 13 | ubsan-cflags-$(CONFIG_UBSAN_ENUM) += -fsanitize=enum | 12 | ubsan-cflags-$(CONFIG_UBSAN_ENUM) += -fsanitize=enum |
| 14 | ubsan-cflags-$(CONFIG_UBSAN_TRAP) += -fsanitize-undefined-trap-on-error | 13 | ubsan-cflags-$(CONFIG_UBSAN_TRAP) += -fsanitize-undefined-trap-on-error |