Changes between Version 10 and Version 11 of Projects/TinyRTEMS


Ignore:
Timestamp:
Jan 3, 2016, 7:18:32 PM (4 years ago)
Author:
Ralph Holmes
Comment:

Fix spelling and/or grammar.

Legend:

Unmodified
Added
Removed
Modified
  • Projects/TinyRTEMS

    v10 v11  
    1212 *  safety critical applications which need to eliminate all unused code
    1313
    14 The last point is '''VERY''' important and often lost in the discussions.  RTEMS is often used in safety-critical applications where every line of code in the deployed software must be analysed.  Removing unused and unneeded code reduces the validation effort.
     14The last point is '''VERY''' important and often lost in the discussions.  RTEMS is often used in safety-critical applications where every line of code in the deployed software must be analyzed.  Removing unused and unneeded code reduces the validation effort.
    1515
    1616This effort is a series of individual tasks which appear unrelated but all somehow drop code or data that is unused in a particular RTEMS application configuration. It is a combination of code and file refactoring, Makefile.am changes, RTEMS configure time options, application time configuration, application link time and alternative algorithms that together shrink the footprint of RTEMS.
    1717
    18 As part of this effort, use of int in the code is being heavily analysed and there is a general movement to C99 types like int32_t.  Also there is a push to reduce cohesion between files and object modules.  For example, if an application and the libraries it depends upon does not require a particular function, there is no reason it should be in the execuable.
     18As part of this effort, use of int in the code is being heavily analyzed and there is a general movement to C99 types like int32_t.  Also there is a push to reduce cohesion between files and object modules.  For example, if an application and the libraries it depends upon does not require a particular function, there is no reason it should be in the execuable.
    1919
    2020RTEMS itself has a lot of features and many of these can be tailored or disabled to reduce both code and data space usage.  Historically, RTEMS minimum footprint provides a full-featured baseline and thus includes features which can not be used by low memory profile systems.  We want RTEMS to support those systems.  Some of this can be done at application configuration time, while other parts must be done at configure and compile time.