SystemC common errors

Wrong type	Compile error
Error message	systemc-2.3.1/include/sysc/datatypes/int/sc_uint_base.h:842: undefined reference to `sc_dt::sc_uint_base::to_string systemc-2.3.1/include/sysc/communication/sc_signal_ports.h:1802: undefined reference to `sc_core::sc_in<bool>::add_trace_internal …. collect2: error: ld returned 1 exit status
error analysis	This error occurred , It is probably due to the default of the current environment gcc The version is relatively low , And install systemc The use of gcc Higher version . Results in the current lower version of gcc Unrecognized high version compiled systemc The library files . commonly ubuntu16.04 In the environment , The corresponding is gcc 5.4.0 edition . Modify current default gcc The version number of can refer to https://blog.csdn.net/qq_31175231/article/details/77774971

 

Wrong type	Compile error
Error message	error: ‘std::gets’ has not been declared
error analysis	std::get() By C++11 Deleted , Reference resources https://stackoverflow.com/questions/38352801/systemc-error-with-the-library and https://stackoverflow.com/questions/12893774/what-is-gets-equivalent-in-c11 You can add compilation options -std=c++98 Ubuntu20.04 (gcc version 9.3.0) The default is c++11

 

Wrong type	Compile and pass , The execution is wrong
Error message	Error: (E115) sc_signal<T> cannot have more than one driver:      signal `MyTest.test_sig' (sc_signal)     first driver `MyTest.TestMethod'  (sc_method_process)     second driver `MyTest.TestThread1' (sc_thread_process)     In file: ../../../../src/sysc/communication/sc_signal.cpp:73
error analysis	Reference resources https://blog.csdn.net/zgcjaxj/article/details/106106426 systemc In the rules , The same sc_signal Multiple drives are not allowed , in other words , The same sc_signal, Only in one SC_METHOD or SC_THREAD Middle quilt write assignment

 

 

Wrong type	Compile and pass , The execution is wrong
Error message	Error:  (E109) complete binding failed: port not bound (sc_in) In file: external/sysc/sysc/communication/sc_port.cpp:235 or 231
error analysis	Description yes port/sc_signal/sc_in/sc_out Forgot to bind perhaps Yes, there is port/sc_signal/sc_in/sc_out It is added to the list of static sensitive events before binding , stay simulation It is found that sensitive events cannot be retrieved during the process , Report errors . About the latter , May refer to https://blog.csdn.net/zgcjaxj/article/details/105455330 Generally in end_of_elaboration() Function to add SC_METHOD Function and its sensitive event list

 

Wrong type	Compile and pass , The execution is wrong
Error message	Error:  (E126) sc_export instance already bound: xxxxxxxx In file: external/sysc/sysc/communication/sc_export.h:188
error analysis	Description yes port Repeat binding , And there is a hint of which port/sc_signal

 

 

Wrong type	Compile and pass , The execution is wrong
Error message	Error: (E513) an sc_module_name parameter for your constructor is required In file: external/sysc/sysc/kernel/sc_module.cpp:223
error analysis	One inherited sc_module Class , Must be initialized on the list sc_module Assign a value , It's like MyModule::MyModule(sc_core::sc_module_name name)     : sc_module(name), ….

 

Wrong type	Compile and pass , The execution is wrong
Error message	Error:  (E565) invalid use of sc_(and|or)_event_list: wait() on empty event list not allowed In file: external/sysc/sysc/kernel/sc_wait.cpp:103
error analysis	Still groping