Searched refs:BOUND_CHECKS (Results 1 – 5 of 5) sorted by relevance
414 # BOUND_CHECKS controls the support for the bounds-safety features.416 # - On other platforms, explicitly setting BOUND_CHECKS=0429 # be accompanied with BOUND_CHECKS, a developer is allowed to use430 # BOUND_CHECKS_SOFT=1 as a shortcut for BOUND_CHECKS=1 BOUND_CHECKS_SOFT=1431 # The combination BOUND_CHECKS_SOFT=1 BOUND_CHECKS=0 is not supported.434 ifndef BOUND_CHECKS436 BOUND_CHECKS := 1438 BOUND_CHECKS := 0440 export BOUND_CHECKS441 endif # ifndef BOUND_CHECKS[all …]
91 #define BOUND_CHECKS 0x10 /* build with -fbounds-safety */ macro
387 f_flags |= BOUND_CHECKS; in read_files()540 f_flags |= BOUND_CHECKS; in read_files()858 case BOUND_CHECKS: in do_rules()
1175 #if KERNEL && !BOUND_CHECKS && !__has_ptrcheck
107 * $ make BOUND_CHECKS=0 # disable -fbound-attributes for this build