arnavsharma990 commented on issue #20414:
URL: https://github.com/apache/nuttx/issues/20414#issuecomment-5938263192
I did a linked-image size investigation on `stm32f103-minimum:nsh`
using `arm-none-eabi-gcc 16.2.0`, `arm-none-eabi-size`, and
`nm --print-size`. Baseline re-verified after each test, tree clean,
all source stubs reverted:
51608 .text / 480 .data / 2952 .bss / 52088 B flash
Isolated flash deltas:
- `CONFIG_DISABLE_MOUNTPOINT=y`: -2812 B (includes removed
mount/NSH commands, not just the dir layer)
- `CONFIG_ARCH_STACKDUMP=n`: -1320 B
- `CONFIG_FDCLONE_STDIO=y`: -24 B
- Temporarily stubbing `fdlist_extend()` to `-EMFILE`: -196 B
(upper bound only, reverted)
- Single-iovec read/write fastpath with compat kept: +36 B
(negative result, reverted)
The interesting discrepancy is that current linked-image results don't match
several historical figures. E.g. the growable FD table is reported as
~1.9 KB, while removing `fdlist_extend()` from the current linked image
changes it by only ~196 B.
Could you share the baseline commit/configuration and size command used
for the historical measurements? I'd like to reproduce the original
deltas under the same conditions and trace which changes account for the
reported growth.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
