GS Engineering

Building Blocks for Tool Independent ESL SystemC

Company infomation
Information about the company (if relevant)


Documentation:

  • GreenSocs version numbers are of the form: x.y.z

    x= Interface version number (if the interfaces change, the version number must increase)

    y= Feature (if features are added, the version number must increase)

    z= Bug (if a bug is fixed, the version number must increase)

    Train Releases

  • This page should be expanded to include some best coding practices.

    Changes to run with Microsoft Visual C++

  • See a guide how to release on pages

    Release Quality

    Releases can be made as follows:
    • Untested - they have not been through this procedure
    • Tested - they have been through this procedure
    • S
  • Regression tests is the GreenSocs projects

    For all projects we should have regression tests.

    Regression tests shall ensure that updates and bug fixes to any feature do not break anything which was working fine before. They shall also test as much cases as possible to a) have compiled each code line and b) to have executed each code line.

    • Directory:
      • The best is having a sub di
  • The GreenSocs Development Environment is some Makefile tricks to avoid changing the Makefiles by hand.

    The Problem

    Many Makefiles in the GreenSocs projects hardcode the paths for the projects. All these paths points to home directories or directories that are not available in all machines.
  • <nowiki><pre>


    GreenSocs 4.2.0 (2010-09-07, r3814)

      * GreenControl
      ** minor updates to command_if signatures (GC_Logger)
      ** Added Extension mechanism to Services (gc_service_ID_extension)
      ** Added gc_port constructor getting extended Service ID
      ** Added extension example
    

    GreenSocs 4.1.1 (2010-09-07, r3810)

Mail List: 
This group has an email list, all issues will be sent to all members of the group