SC_CTHREAD slows down simulation

[Meir]

Hey all.

i am a novice user of SystemC, and couldn't find an answer to the following question?

ive noticed that when ever i tried using SC_CTHREAD(proc_name, clk.pos()) -> the simulation time was increased significantly (to a level where it appeared to be stuck).

what is the right use of SC_CTHREAD so that it doesnt jam the simulation?

i am adding an example of what i did:

SC_CTHREAD(monitor_intr_in, clk.pos());

...

void TMG_helper::monitor_intr_in() {

   while(true) {
        cout << "i am here" << endl;
    }
}

 

thank you in advance !

[David Black]

You are missing at minimum a single wait() in the infinite loop. SystemC is an event driven simulator and as such concurrency is modeled using co-operative multi-tasking. An infinite loop is an infinite loop. No pre-emption.

[Meir]

hey.

thanks for replying.

the code that i posted was a snippet.

it did include the wait() statement.

so my questions still remains:

1. what is the right use case for SC_CTHREAD ?

2. why in my give example the simulation gets "stuck" ?

 

thanks

[Meir]

hey.

any chance getting a reply ?

 

thank you !!

[Roman Popov]

In general, you can use profiler tool to understand where hotspots are. 

Your code snippet is incomplete, so it is impossible to say anything.

[Timur Kelin]

Hi Roman

Could you please recommend a multi-threaded profiler for SC. I tried making use of gprof but with no success. 

Thank you

16 hours ago, Roman Popov said:

In general, you can use profiler tool to understand where hotspots are. 

 

[Roman Popov]

6 hours ago, Timur Kelin said:

Hi Roman

Could you please recommend a multi-threaded profiler for SC. I tried making use of gprof but with no success. 

Many commercial SystemC tools have SystemC-specific profilers measuring runtimes of SC processes. On Windows I usually use Visual Studio built-in profiler. I don't have experience with profiling on Linux.

[sumit_tuwien]

On 1/21/2020 at 11:54 AM, Timur Kelin said:

Hi Roman

Could you please recommend a multi-threaded profiler for SC. I tried making use of gprof but with no success. 

Thank you

 

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

[sumit_tuwien]

On 1/16/2020 at 9:44 AM, Meir said:

hey.

thanks for replying.

the code that i posted was a snippet.

it did include the wait() statement.

so my questions still remains:

1. what is the right use case for SC_CTHREAD ?

2. why in my give example the simulation gets "stuck" ?

 

thanks

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