Changes between Version 88 and Version 89 of Developer/OpenProjects


Ignore:
Timestamp:
Jan 8, 2009, 4:39:56 AM (11 years ago)
Author:
JoelSherrill
Comment:

/* Automated GNU Tools Testing */ Update

Legend:

Unmodified
Added
Removed
Modified
  • Developer/OpenProjects

    v88 v89  
    501501  *  not knowing we add specific CPU options which prevent generating expected instructions on "scan assembly" tests
    502502  *  not generating profile files
     503  *  missing instructions in simulators
    503504 *  Want to eventually run on multiple BSPs inside a single target architecture to cover more code generation possibilities.
    504505
    505506
    506507This project broadly consists of doing whatever is required to automate testing of GNU tools on RTEMS targets.  The first steps are to be able
    507 to automate the building of binutils, gcc/newlib, and gdb from sourcevusing either released versions of the tools or the development version
    508 checked out and updated from the source code control repositories of those projects.
    509 
    510 Since there are approximately a dozen active RTEMS targets, this effort will have to be able to support all targets.  Some of the targets
    511 have simulators.  If there are executable tests, then the project will have to address being able to run those executable tests on the simulators
    512 capturing the output and verifying tests do not run too long.
    513 
    514 The RTEMS Project hasaccess to the GCC Compile Farm for the purpose of testing GNU tools and providing automated reports.  This
    515 is a collection of high power servers and our intent is to do as much of the automated tools testing as possible on those machines.  But the
    516 scripting needed to drive this will be portable to other environments.
     508to automate the building of binutils, gcc/newlib, and gdb from source using either released versions of the tools or the development version
     509checked out and updated from the source code control repositories of those projects.  This step is largely complete with the test scripts
     510in the CVS module ''gcc-testing''.
     511
     512Since there are approximately a dozen active RTEMS targets, this ultimate goal of this effort is to be able to test at least one BSP on all targets.  Some of the targets
     513have simulators.  If there are executable tests, then the project will have to address being able to run those executable tests on the simulators capturing the output and
     514verifying tests do not run too long.
     515
     516The volume of test data generated is very high with GCC having over 60,000 tests.  We need to be able to generate deviation reports which highlight changes between subsequent test runs.  We believe a script to do this exists although the integration of that into the overall test system needs to occur.  Also the deviation report should be emailed to the RTEMS Tool Test Results mailing list (http://www.rtems.org/pipermail/rtems-tooltestresults).
     517
     518The RTEMS Project has access to the GCC Compile Farm for the purpose of testing GNU tools and providing automated reports.  This is a collection of high power servers and our intent is to do as much of the automated tools testing as possible on those machines.  But the scripting needed to drive this will be portable to other environments.
    517519
    518520The RTEMS Project has a lab or test hardware hosted at OAR Corporation which includes multiple target boards and infrastructure to remotely