IEEE 1666-2005 pdf download IEEE Standard SystemC ® Language Reference Manual
1.Overview
1.1 Scope
1This standard defines SystemCas an ANSI standard C++ class library for system and hardware design.
1.2 Purpose
The general purpose of SystemC is to provide a C++-based standard for designers and architects who needto address complex systems that are a hybrid between hardware and software.
The specific purpose of this standard is to provide a precise and complete definition of the SystemC classlibrary so that a SystemC implementation can be developed with reference to this standard alone. Thisstandard is not intended to serve as a users’ guide or to provide an introduction to SystemC, but does containuseful information for end users.
1.3 Subsets
It is anticipated that tool vendors will create implementations that support only a subset of this standard orthat impose further constraints on the use of this standard. Such implementations are not fully compliantwith this standard but may nevertheless claim partial compliance with this standard and may use the nameSystemC.
1.4 Relationship with C++
This standard is closely related to the C++ programming language and adheres to the terminology used inISO/IEC 14882:2003. This standard does not seek to restrict the usage of the C++ programming language; aSystemC application may use any of the facilities provided by C++, which in turn may use any of thefacilities provided by C. However, where the facilities provided by this standard are used, they shall be usedin accordance with the rules and constraints set out in this standard.
This standard defines the public interface to the SystemC class library and the constraints on how thoscclasses may be used. The SystemC class library may be implemented in any manner whatsoever, providedonly that the obligations imposed by this standard are honored.
A C++ class library may be extended using the mechanisms provided by the C++ language. Implementorsand users are free to extend SystemC in this way, provided that they do not violate this standard.
NOTE–It is possible to create a well-formed C++ program that is legal according to the C++ programming languagestandard but that violates this standard. An implementation is not obliged to detect every violation of this standard.”
1.5 Guidance for readers
Readers who are not entirely familiar with SystemC should start with Annex A. “Inroduction to SystemC.which provides a brief inforal summary of the subject intended to aid in the understanding of thenormative definitions. Such readers may also find it helpful to scan the examples embedded in the normativedefinitions and to see Annex B“Glossary.”
Readers should pay close attention to Clause 3, “Terminology and conventions used in this standard.” Anunderstanding of the terminology defined in Clause 3 is necessary for a precise interpretation of thisstandard.
Clause 4.“Elaboration and simulation semantics.” defines the behavior of the SystemC kernel and is centralto an understanding of SystemC, The semantic definitions given in the subsequent clauses detailing theindividual classes are built upon the foundations laid in Clause 4.
The clauses from Clause 5 onward define the public interface to the SystemC class library. The followinginformation is listed for each class:
A C++ source code listing of the class definitiona
A statement of any constraints on the use of the class and its members
A statement of the semantics of the class and its members
For certain classes, a description of functions, typedefs, and macros associated with the class.
eInformative examples illustrating both typical and atypical uses of the class
Readers should bear in mind that the primary obligation of a tool vendor is to implement the abstractsemantics defined in Clause 4, using the framework and constraints provided by the class definitions startingin Clause 5.
IEEE 1666-2005 pdf download
PS:Thank you for your support!
