CONFIG_OUTPUT_PRINT_MEMORY_USAGE

Print memory usage to stdout

Type: bool

Help

If the toolchain supports it, this option will pass
--print-memory-region to the linker when it is doing it's first
linker pass. Note that the memory regions are symbolic concepts
defined by the linker scripts and do not necessarily map
directly to the real physical address space. Take also note that
some platforms do two passes of the linker so the results do not
match exactly to the final elf file. See also rom_report,
ram_report and
https://sourceware.org/binutils/docs/ld/MEMORY.html

Defaults

• n

• n

• y

Kconfig definitions

At <Zephyr>/boards/posix/native_posix/Kconfig.defconfig:11

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:22

Menu path: (Top)

config OUTPUT_PRINT_MEMORY_USAGE
    bool
    default n
    depends on BOARD_NATIVE_POSIX

---

At <Zephyr>/boards/posix/nrf52_bsim/Kconfig.defconfig:11

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:22

Menu path: (Top)

config OUTPUT_PRINT_MEMORY_USAGE
    bool
    default n
    depends on BOARD_NRF52_BSIM

---

At <Zephyr>/Kconfig.zephyr:385

Included via <Zephyr>/Kconfig:8

Menu path: (Top) → Build and Link Features → Build Options

config OUTPUT_PRINT_MEMORY_USAGE
    bool "Print memory usage to stdout"
    default y
    help
      If the toolchain supports it, this option will pass
      --print-memory-region to the linker when it is doing it's first
      linker pass. Note that the memory regions are symbolic concepts
      defined by the linker scripts and do not necessarily map
      directly to the real physical address space. Take also note that
      some platforms do two passes of the linker so the results do not
      match exactly to the final elf file. See also rom_report,
      ram_report and
      https://sourceware.org/binutils/docs/ld/MEMORY.html

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