<az1[m]>
Plus you can target embedded devices with ratatui
adamgreig[m] has joined #rust-embedded
<adamgreig[m]>
ooh, rust 1.97 is out today, which now shows linker messages by default even on successful builds, which means you can now stick println!("cargo::rustc-link-arg=--print-memory-usage"); in your build.rs and get memory usage by region output on each build
M9names[m] has joined #rust-embedded
<M9names[m]>
I'm so glad I can retire the hacks we previously had to use to get that output
<JamesMunns[m]>
what output does that get you?
<JamesMunns[m]>
"by region" sounds like what `size -Ax` gets you?
glitchy has quit [Ping timeout: 248 seconds]
glitchy has joined #rust-embedded
rainbyte has quit [Read error: Connection reset by peer]
rainbyte has joined #rust-embedded
mkj[m] has quit [Quit: Idle timeout reached: 172800s]
glitchy has quit [Ping timeout: 257 seconds]
glitchy has joined #rust-embedded
<dragonn[m]>
<adamgreig[m]> ooh, rust 1.97 is out today, which now shows linker messages by default even on successful builds, which means you can now stick println!("cargo::rustc-link-arg=--print-memory-usage"); in your build.rs and get memory usage by region output on each build
<adamgreig[m]>
which I think is the best: it's like "here's the % of flash and (statically allocated) ram you used"
<adamgreig[m]>
no adding up .vector_table and .text and .rodata or whatever, no knowing you have to read the "dec" column or otherwise add "text" and "data" for flash but "data" and "bss" for ram, etc