Changes between Version 64 and Version 65 of TBR/UserManual/RTEMS_Coverage_Analysis


Ignore:
Timestamp:
Sep 19, 2009, 12:39:56 AM (10 years ago)
Author:
GlennHumphrey
Comment:

/* Coverage Profiles */ Improved wording

Legend:

Unmodified
Added
Removed
Modified
  • TBR/UserManual/RTEMS_Coverage_Analysis

    v64 v65  
    112112
    113113
    114 RTEMS contains a lot of source code and although the primary focus of coverage analysis is to achieve 100% coverage of well-defined code subsets, we would also like to increase the amount of source code analyzed.  In order to manage the increase in a controlled manner, we defined to basic groups of source code.  The first group is called Baseline and the second group is called Developmental.  The Baseline group contains the source code that has achieved (or nearly achieved) 100% Object Code Coverage.  The Developmental group contains the source code for which there are very few test cases and therefore very poor coverage.
    115 
    116 Initially, the Baseline group included source code from the cpukit.  Specifically the following cpukit directories were included:  score, sapi, rtems and posix.
    117 
    118 The Developmental group includes: libcsupport, libfs/imfs, libmisc/stackchk, libmisc/cpuuse, libmisc/bspcmdline, libmisc/dmpbuf and libmisc/devnull.
     114RTEMS contains a lot of source code and although the primary focus of coverage analysis is to achieve 100% coverage of well-defined code subsets, we would also like to increase the amount of source code analyzed.  In order to manage the increase in a systematic manner, we defined to basic groups of source code.  The first group is called Baseline and the second group is called Developmental.  The Baseline group contains the source code that has achieved (or nearly achieved) 100% Object Code Coverage.  The Developmental group contains the source code for which there are very few test cases and therefore very poor coverage.
     115
     116Initially, the Baseline group included source code from the cpukit.  Specifically the following cpukit directories were included:  score, sapi, rtems and posix.  This group represents a full tasking and synchronization feature set.  What was not in the Baseline group was placed in the Developmental group.  The Developmental group included: libcsupport, libfs/imfs, libmisc/stackchk, libmisc/cpuuse, libmisc/bspcmdline, libmisc/dmpbuf and libmisc/devnull.
     117
     118From the two groups, we recognized the need to analyze each group with POSIX enabled and POSIX disabled.  This produced four sub-groups that we called profiles.  The four profiles are:
     119
     120 *  Baseline (POSIX Enabled)
     121 *  Baseline (POSIX Disabled)
     122 *  Developmental (POSIX Enabled)
     123 *  Developmental (POSIX Disabled)
    119124
    120125As 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
    121126
    122127There are four code subsets analysed with the option of using the -O2 or -Os level.
    123 
    124  *  Baseline with POSIX Enabled
    125  *  Baseline with POSIX Disabled
    126  *  Developmental with POSIX Enabled
    127  *  Developmental with POSIX Disabled
    128 
    129 Define baseline and developmental
    130128= Compilation and Configuration Options =
    131129