Changes between Version 4 and Version 5 of Release/4.10


Ignore:
Timestamp:
Sep 17, 2008, 11:34:42 PM (11 years ago)
Author:
JoelSherrill
Comment:

Move CONFIGURE_UNIFIED_WORK_AREAS to Configuration Changes section and add TACK_CHECKER_ON renamed to CONFIGURE_STACK_CHECKER_ENABLED.

Legend:

Unmodified
Added
Removed
Modified
  • Release/4.10

    v4 v5  
    4848  *  double_precision, rtems_double (use double, instead)
    4949
    50  *  The capability to have RTEMS operate with the RTEMS Workspace and C Program Heap as a combined pool.  Historically, RTEMS has had separate memory pools for the RTEMS Workspace and C Program Heap.  Having separate pools does have some advantages in the event a task blows a stack or writes outside its memory area. However, in low memory systems the overhead of the two pools plus the potential for unused memory in either pool is very undesirable.
    51 Similarly, in high memory environments, this is desirable when you want to use the RTEMS "unlimited" objects option.  You will be able to create objects until you run out of all available memory rather then just until you run out of RTEMS Workspace.  Define CONFIGURE_UNIFIED_WORK_AREAS to enable this configuration.
    52 
    5350 *  All BSPs have been modified to use the BSP Framework to allocate memory to RTEMS and the C Program Heap.  It is now assumed that each BSP will provide an implementation of bsp_get_work_area() and it is HIGHLY encouraged that you use the shared one in libbsp/shared.
    5451
     
    6057 *  TBD
    6158= Configuration Changes =
     59
     60 *  The capability to have RTEMS operate with the RTEMS Workspace and C Program Heap as a combined pool.  Historically, RTEMS has had separate memory pools for the RTEMS Workspace and C Program Heap.  Having separate pools does have some advantages in the event a task blows a stack or writes outside its memory area. However, in low memory systems the overhead of the two pools plus the potential for unused memory in either pool is very undesirable. Similarly, in high memory environments, this is desirable when you want to use the RTEMS "unlimited" objects option.  You will be able to create objects until you run out of all available memory rather then just until you run out of RTEMS Workspace.  Define CONFIGURE_UNIFIED_WORK_AREAS to enable this configuration.
     61
     62 *  STACK_CHECKER_ON renamed to CONFIGURE_STACK_CHECKER_ENABLED.
    6263
    6364 *  TBD