Table of Contents

Previous Chapter

36 The Master Library

• It describes the structure of the source code of the SDT Master Library
  
• It describes the runtime model used for the programs generated by the SDT C Code Generator. It also describes the data structures for representing the various SDL objects
  
• The structure of the generated code is discussed
  
• The memory requirements for applications is described
  
• Information about how to make a customized Master Library is provided
  
• The compilation switches which affect the properties of the Master Library are documented.
  

Introduction

1. The sections "File Structure" on page 2128, "The Symbol Table" on page 2131, and "The SDL Model" on page 2157 describe the runtime model for programs generated by the SDT C Code Generator.
   Mainly it is the data structure used to represent various SDL objects that is discussed, both from the static point of view (the type definitions), and from the dynamic point of view (what information it represents and how it is initialized, changed, and used).
   The full runtime model that is used during simulations (with the monitor) is described. From this model, an optimization is made to obtain an application (not using the monitor). The optimization is discussed under "Compilation Switches" on page 2269.
   
2. The section "Structure of Generated Code" on page 2199 contains information about the code generated by the C Code Generator. The generated code is described in detail (although some details are omitted).
   There are explanations and examples showing what the generated code looks like, but not why it looks like it does. There are also some comments indicating in what circumstances different generated objects (functions, types, variables, and so on) are used.
   
3. In the sections "Compilation Switches" on page 2269, "Creating a New Library" on page 2289, and "Adaption to Compilers" on page 2295, different aspects on how to make new versions of the runtime library are discussed.
   The compilation switches treated in the section "Compilation Switches" on page 2269 are used to determine the properties of the runtime library and the generated C code, while section "Creating a New Library" on page 2289 shows how to make new versions of the runtime library using for example new combinations of compilation switches.
   In the section "Adaption to Compilers" on page 2295, porting issues are discussed.
   

File Structure

• scttypes.h
  
• sctlocal.h
  
• sctpred.h
  
• sctsdl.c
  
• sctpred.c
  
• sctutil.c
  
• sctmon.c
  
• sctpost.c
  
• sctos.c
  
• sctworld.o
  
• post.h, sdt.h, and post.o
  

Description of Files

scttypes.h

sctlocal.h

sctpred.h

sctsdt.c

• Handling and reporting SDL dynamic errors
  
• SDL operations, such as Output, Create, Stop, Nextstate, Set, Reset, together with help functions for these activities
  
• Initialization and the main loop (the scheduler).
  

sctpred.c

sctutil.c

sctmon.c

sctpost.c

sctos.c

The basic functions necessary for an application are a function to read the clock and a function to allocate memory.

To move a generated C program plus the runtime library to a new platform (including a new compiler), the major changes are to be made in this file, together with writing a new section in scttypes.h to describe the properties of the new compiler.

sctworld.o

A pre-linked file gives a faster link operation when generating an application. This file is of course only present if the hardware platform supports pre-linking.

post.h and sdt.h

post.o

Table of Contents

Next Chapter