SystemC | Accellera SystemC Releases and Patches | Compiler library

From INSTALL file shipped with SystemC

SystemC 2.3 includes a fixed-point package that is always built. When compiling your applications with fixed-point types, you still have to use compiler flag -DSC_INCLUDE_FX. Note that compile times increase significantly when using this compiler flag.

Using your code as an example

The port "a" is an input port so cannot be written to. If you make it an output port then you can write to it. Also, the port is not bound so you will also get an error for that so I have bound a signal to it just so it compiles.

Deleting the executable file and recompiling the code helped me out.

I just removed the folder build:

rm -r build

then I built the gem5 again:

scons build/ARM/gem5.opt

It worked for me.

For SystemC, the kernel and the model need to be compiled with the same set of modern C++ features enabled, see the RELEASENOTES and INSTALL files in the package. By default, the currently selected C++ standard of the compiler is used by SystemC (i.e. from -std=c++17).

To build SystemC for use across different C++ standard settings, explicitly define the preprocessor flag SC_CPLUSPLUS to the minimum version you need when building both, the kernel and your models.

For example

• build SystemC with -std=c++11 (aka SC_CPLUSPLUS=201103L)
• build your model with a newer C++ standard as you like, but add -DSC_CPLUSPLUS=201103L to your compiler flags.

Supported values for SC_CPLUSPLUS are:

• 199711L (C++03, ISO/IEC 14882:1998, 14882:2003)
• 201103L (C++11, ISO/IEC 14882:2011)
• 201402L (C++14, ISO/IEC 14882:2014)
• 201703L (C++17, ISO/IEC 14882:2017)

If SystemC 2.3.3 does not work with some version/configuration of the Xcode Clang compiler, you can consider opening an issue at https://github.com/accellera-official/systemc.

I suppose it is caused by the standard option behavior of the gtest package. These are the default options of gtest 1.10:

Is there a way i can enable an automatic warning for my SystemC simulation whenever a fixed point variable overflows?

Not in a centralized, standard way.

If you want to monitor a fixed set of variables, you may be able to use the sc_fxnum_observer extension available in some SystemC implementations.

To use it, you have to #define SC_ENABLE_OBSERVERS before including SystemC (ideally from your compiler command-line). The allows you to "attach" an observer to your sc_fixed<...> (and related) classes, which is notified upon the following events:

Ports in SystemC are not wires, but smart pointers. Unlike regular C++ pointers, SystemC ports are safe and support hierarchical binding. Similarly to a regular pointers, by default, you can't connect port to 2 channels simultaneously.

While this may be inconvenient for low-level modeling, this allows to use ports with any kind of high-level channels, like FIFOs or TLM channels.

Looks like you need something like broadcast port : when you write to such a port message should be written to all connected channels.

To create a port that can be binded to a multiple channels, use second template parameter N of sc_port :

You cannot drive your unconnected ports in the Memory_Controller constructor. If you want to explicitly drive these ports during startup, move these calls to a start_of_simulation callback: