CONFIG_ZSL_BOUNDS_CHECKS

Enable bounds checking in functions.

Type: bool

Help

Enabling this option will cause common functions to ensure that requested
data is within the bounds of the vector, matrix, etc. object. This should
generally always be enabled for safety reasons, but you may wish to
disable it in exceptional circumstances for performance reasons.

Note that the performance gains from enabling inline functions will
generally be greater than the benefit of disabling bounds checks, and
with far less risk associated with the decision.

EXTREME CARE should be taken when disabling this option since it can
easily lead to stack corruption and critical firmware failures. This
should only be disabled as a final option, and only on known-good
and thoroughly tested code.

Direct dependencies

ZSL

(Includes any dependencies from ifs and menus.)

Default

y

Kconfig definition

At /home/runner/work/sdk-nrf/sdk-nrf/ncs/modules/lib/zscilib/Kconfig.zscilib:60

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:33 → <Zephyr>/modules/Kconfig:6 → <nRF>/doc/_build/kconfig/Kconfig.modules:86

Menu path: (Top) → Modules → zscilib (/home/runner/work/sdk-nrf/sdk-nrf/ncs/modules/lib/zscilib) → Zephyr scientific library support

config ZSL_BOUNDS_CHECKS
    bool "Enable bounds checking in functions."
    default y
    depends on ZSL
    help
      Enabling this option will cause common functions to ensure that requested
      data is within the bounds of the vector, matrix, etc. object. This should
      generally always be enabled for safety reasons, but you may wish to
      disable it in exceptional circumstances for performance reasons.

      Note that the performance gains from enabling inline functions will
      generally be greater than the benefit of disabling bounds checks, and
      with far less risk associated with the decision.

      EXTREME CARE should be taken when disabling this option since it can
      easily lead to stack corruption and critical firmware failures. This
      should only be disabled as a final option, and only on known-good
      and thoroughly tested code.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)