Opened on 06/13/18 at 07:52:21
Closed on 06/15/18 at 05:15:50
#3451 closed task (fixed)
Remove size_rtems script
Reported by: | Sebastian Huber | Owned by: | Sebastian Huber |
---|---|---|---|
Priority: | normal | Milestone: | 5.1 |
Component: | tool | Version: | 5 |
Severity: | normal | Keywords: | |
Cc: | Blocked By: | ||
Blocking: |
Description
This script is horribly out of date. A new version could be placed in RTEMS tools if necessary.
Change History (2)
comment:1 Changed on 06/13/18 at 08:17:24 by Joel Sherrill
comment:2 Changed on 06/15/18 at 05:15:50 by Sebastian Huber <sebastian.huber@…>
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
In 9eb1494f/rtems:
Note: See
TracTickets for help on using
tickets.
I don't disagree with removing this. The question this script is trying to answer is "what's the code space requirement for RTEMS?" This is usually asked as "How big is RTEMS?" The answer is that it depends.
This script produced a report similar to some other RTOS when it was written. Buy I evolved to think that the linked size of sample reference applications like base_sp, minimum, hello, minimum networking, etc.
A real application will vary in size based on the set of services it uses. Often those services depends on things that add code which we wouldn't consider part of RTEMS. A C++ application with megabytes of code from the C++ Standard Library is large but may use a very small but of code from RTEMS itself. The Qt demos were similar.
Also size varies by architecture, optimization level, gcc version, function section linking, etc.
There is no single answer and no standard guides. So we need to decide what we think is useful, explain it, and watch it.