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” if BOARD_NATIVE_POSIX
“y”

Kconfig definitions¶

At boards/posix/native_posix/Kconfig.defconfig:10

Included via Kconfig:10 → Kconfig.zephyr:19

Menu path: (top menu)

config OUTPUT_PRINT_MEMORY_USAGE
    bool
    default "n" if BOARD_NATIVE_POSIX
    depends on BOARD_NATIVE_POSIX

At misc/Kconfig:205

Included via Kconfig:10 → Kconfig.zephyr:31

Menu path: (top menu) → Build and Link Features → Build Options

config OUTPUT_PRINT_MEMORY_USAGE
    bool
    prompt "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

(Definitions include propagated dependencies, including from if’s and menus.)