You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The toolchain is running on stable-x86_64-unknown-linux-gnu but the target is thumbv7em-none-eabihf (I would said the target is more important to know than the host architecture)
@@ Breakdown per crate @@ should probably be @@ Breakdown per function @@ if the function mode is enabled
It only lists the first two functions?
While the total file size might be interesting every now and the really interesting metric here is the code (or .text) size, the complete file size also contains debugging information and other data which may not even end up in memory when running the binary
The text was updated successfully, but these errors were encountered:
Taken from @therealprof in #147 (comment)
The issues noted here can be seen from: stm32-rs/stm32f4xx-hal#159 (comment)
It doesn't quite yield the expected output though. ;)
This is the human-readable output:
Few things of note:
@@ Breakdown per crate @@
should probably be@@ Breakdown per function @@
if the function mode is enabledThe text was updated successfully, but these errors were encountered: