Jump to content

Vegh, Janos

  • Content Count

  • Joined

  • Last visited

  • Days Won


Vegh, Janos last won the day on June 20 2019

Vegh, Janos had the most liked content!

About Vegh, Janos

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I recently found that graphic shell/extension. Is there any reason, why it was discontinued? (I guess it is not very interesting for automation, verification, etc; but I guess it could be useful for demonstration/education; especially when thinking in non-EDA utilization of SystemC) The idea I liked, and also noticed that both Qt and SystemC versions are outdated. From QT side, it needs a complete rewrite, but possible. Is there some basic change in SystemC that makes that approach (at least partly) unusable? If yes, is there and "porting guide" around?
  2. Yes, this is exactly what I originally wanted to do: just to measure how the _relative_ efficiency changes if wait/next_trigger event handling is utilized. I do not say I want to measure something absolute, like in the case of supercomputers the important parameter is what time is needed for which benchmark. BTW: how the efficiency of the simulation depends on the size of the design, is also important. The preliminary tests say that the large designs eat up the computing resource, and the simulation time strongly increases. I have uploaded the 'benchmark system' to https://github.com
  3. I'll surely do, but this was the first verified (by me) measurement. And, I wanted to know if it can be interesting for this audience. I will clean up the code and upload in the coming days. Although the absolute values of the data are not so meaningful, even I did the measurements in debug mode.
  4. Hello, I saw many times on this list the question about the performance of wait() vs. next_trigger, and in general, I think that when speaking about system performance, it is important to know what execution speed can be expected.I decided to measure the performance, the result see in the attachment. The starting point was the 'next_trigger' example. I slightly modified it to make altogether 10 calls to the respective function, and added an external repetition cycle, i.e. altogether 1000 "actions" are executed by a module. After that I prepared the equivalent functionality using 'wai
  • Create New...