Changes between Version 39 and Version 40 of TBR/UserManual/RTEMS_Coverage_Analysis


Ignore:
Timestamp:
09/16/09 00:53:37 (15 years ago)
Author:
JoelSherrill
Comment:

/* Coverage Profiles */ Add list of code subsets analysed

Legend:

Unmodified
Added
Removed
Modified

  • TBR/UserManual/RTEMS_Coverage_Analysis

    v39 v40  
    7676RTEMS includes a lot of source code and the coverage analysis should focus on improving the test coverage of well-defined code subsets with a trend over time of increasing both the level of coverage (e.g. object to statement to decision to MC/DC) and the amount of source code covered.
    7777
    78 As other support libraries in cpukit is covered, these will be move from the Developmental Profile and added to the '''POSIX Enabled''' and '''Classic API Only''' profiles.
     78As other support libraries in cpukit is covered, these will be move from the Developmental Profile and added to the '''POSIX Enabled''' and '''Classic API Only''' profiles
     79
     80There are four code subsets analysed with the option of using the -O2 or -Os level.
     81
     82 *  Baseline with POSIX Enabled
     83 *  Baseline with POSIX Disabled
     84 *  Developmental with POSIX Enabled
     85 *  Developmental with POSIX Disabled
     86
     87Define baseline and developmental
    7988= Compilation and Configuration Options =
    8089
    … …  
    8796
    8897This is the first profile we tested. This initially focused on the score, sapi, rtems, and posix directories in the cpukit directory.  This profile represents a full tasking and synchronization feature set. 
    89 = Classic API Only (POSIX Disabled)  =
     98= Classic API Only (POSIX Disabled) =
    9099
    91100