sumit_tuwien

Thanks

Hello All, I have a question. If I want to create a signal tracing database which uses hdf5 format and add sc_hdf5_trace.*, how much approximate effort it will need? Does anybody have any estimation? Regards, Sumit

Thanks @Bas Arts , Thanks for checking. Seems either the compiler or the system has some issues. Regards, Sumit

Hi @David Black, Following is the reduced version of the class: # ifndef BLAH_H_ # define BLAH_H_ class Blah final : sc_core::sc_module { private : double ThisOneWillAlsoNotLetWrite { 0.0 } ; public : sc_core::sc_signal < double > IWillNotLetYouWrite { "IWillNotLetYouWrite" } ; SC_HAS_PROCESS (Blah) ; explicit Blah(const sc_core::sc_module_name& ModuleName_) : sc_core::sc_module { ModuleName_ } {} ~Blah() final = default ; Blah& operator=(const Blah& other) = delete ; Blah(const Blah& other) = delete ; Blah operator=(Blah&& other) = delete ; Blah(Blah&& other) = delete ; void LetsWrite() { IWillNotLetYouWrite.write(1.0); } void ThisOneFailsToo() { ThisOneWillAlsoNotLetWrite = 1.0 ; } }; # endif ~ # Yes, -Wall -Wextra was turned ON. --std=c++14. # SystemC version : 2.3.3 # Compiler gcc-9.3.0 Regards, Sumit

Possibly not. It even cannot write a simple double public member variable.

Hello All, I have a module, which have a public member function which when called will write some values in a signal declared within the module. I can write into the signal from within the module. But if I try to access member function from outside the module instance, I get a crash. When I am trying to debug it, I find the following message: Program received signal SIGSEGV, Segmentation fault. t0x00000000080869c6 in sc_core::sc_signal_t<double, (sc_core::sc_writer_policy)0>::write (this=0xe8, value_=@0x7ffffea1ff00: 1) at /blah/systemc-2.3.3/include/sysc/communication/sc_signal.h:292 292 bool value_changed = !( m_new_val == value_ ); I am using gcc-9.3.0. Any help will be appreciated. Regards, Sumit

Hello, Is gcc 9.3.0 a version for which SystemC library has been tested? Regards, Sumit

I guess SC_USE_PTHREADS needs to be defined. Regards, Sumit

Hi @AmeyaVS I am not building it, rather including these in my code base. Do you have any idea how to do in this case ? Regards, Sumit

Hello! If I import the SystemC library into my codebase instead of compiling it separately, then, is there any compiler define or switch I can turn on to use pthreads ? Regards, Sumit

Your simulation was stuck because it was not proceeding with time ...

valgrind can be used as a profiler here. the tool is callgrind. kcachegrind comes with kde is a nice viewer.

Hello, Please use -fdelayed-template-parsing to bypass this bug for the time being. Regards, Sumit

Thanks Phillip. Regards, Sumit

Hello Philipp, Would it be possible to bypass the bug by explicitly deleting the destructor [public : ~mclass() = delete;] if the the chosen c++ standard is at or above c++11 ? It started hurting now. Regards, Sumit