:orphan: .. title:: CONFIG_OUTPUT_PRINT_MEMORY_USAGE .. kconfig:: CONFIG_OUTPUT_PRINT_MEMORY_USAGE CONFIG_OUTPUT_PRINT_MEMORY_USAGE ################################ *Print memory usage to stdout* Type: ``bool`` Help ==== .. code-block:: none 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 ``/posix/native_posix/Kconfig.defconfig:11`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:22`` Menu path: (Top) .. code-block:: kconfig config OUTPUT_PRINT_MEMORY_USAGE bool default n depends on BOARD_NATIVE_POSIX ---- At ``/posix/nrf52_bsim/Kconfig.defconfig:11`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:22`` Menu path: (Top) .. code-block:: kconfig config OUTPUT_PRINT_MEMORY_USAGE bool default n depends on BOARD_NRF52_BSIM ---- At ``Kconfig.zephyr:387`` Included via ``Kconfig:8`` Menu path: (Top) → Build and Link Features → Build Options .. code-block:: kconfig 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.)*