The emulator has fallen behind the RCCE trunk. Are you using the emuator from the trunk? It has known problems dealing with mem copies. The emulator on the latest tag should work but it uses an older version of RCCE.
Resource contraints are preventing a timely update of the emulator. Please don't hesitate if you can help.
Hi,
I use tags/RCCE_V1.0.13.
The problem happans also without using any mem operations or RCCE message passing. Even a simple "Hello World" doesn't run on many (more than 10) cores.
Uri
I think one bug in the current RCCE trunk concerning the emulator is a missing #pragma omp threadprivate (RCCE_flags) within RCCE_lib.h -- please find attached a fixed header file.
Kind regards,
Carsten
Thanks, Carsten. I think another bug has to do with the optimized mem copy (optimized for running on hw). There seems to be more interest in the emulator than I expected.
Thanks. I replaced the file with the attached.
Now I don't meet the problem. I will try to run some other applications to ensure that the issue was solved.
Uri
Uri,
Which emulator are you using ... the one from the latest RCCE tag or the RCCE trunk/
The reason I wanted to check was that Carsten's fix referenced the emulator in the trunk. I had thought the emulator in the latest tag worked fine and was surprised to see a problem. Are you saying that you applied the fix intended for the trunk to the latest tag and that fixed your issue? Note that the tag is quite an old RCCE. My opinion is that we really need to fix the emulator in the trunk, and I will look into that.
Hi,
I found that the problem of non-running cores only happens when a core is calling printf.
Adding a barrier before the first printf solves this issue, so I suspect that after calling printf from a UE, RCCE_init does not work on any other UE.
Uri
