Jump to content

maehne

Members
 View Profile  See their activity

  • Content Count

    307

  • Joined

  • Last visited

  • Days Won

    36

maehne last won the day on January 27

maehne had the most liked content!

Community Reputation

75 Excellent

See reputation activity

4 Followers

About maehne

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    Burgdorf, Switzerland

Recent Profile Visitors

2,245 profile views
  1. maehne started following A few Valgrind issues, sc_set_time_resolution fails due to "sc_time object(s) constructed", 2d array data passing through generic payload and 6 others
  2. maehne
    Maybe your application or one of the libraries it is using creates sc_time objects by initialising some global or static constants/variables?
  3. maehne
    Any multidimensional array can be mapped to linear storage and thus a one-dimensional array. C/C++ uses row-major order. If your 2d array deviates from that, you need to adjust ist explicitly.
  4. maehne
    Your approach is also valid. You simply cannot profit with this approach from the infrastructure provided by SystemC, e.g., tracing the communication between the nodes. Whether this may pose a problem in the future is up to you to decide.
  5.    coderoo reacted to a post in a topic: Split custom bundled signals and connect to individual ports
  6. maehne
    Thanks @Andy Goodrich for your additional analysis. We probably should also take into account the recent feedback from @Runip Gopisetty on the datatypes, where he also mentioned the sc_vpool objects as being problematic making the SystemC datatypes not thread-safe.
  7. maehne
    You'll have to create internal (i.e., private) signals for each member of the bundled class, which you need to connect to sub-blocks. Then, you have to register a SC_METHOD or SC_THREAD, which is sensitive to changes of the bundled input. The method/thread can then assign the correct new values to the internal signals based on the changed bundled input.
  8. maehne
    You don't provide a minimal self-contained code example that exposes your problem. This complicates for an external the analysis of your problem. Also, a plot of the relevant signals would help to understand better, what wrong behaviour you are observing. Anyway, the calculation of the sine argument for x1 and x2 look suspicious to me: The "+" in front of 100 and 200 should probably be a "*" so that it corresponds to the general form of a wave equation x = A * sin(omega * t + phi). Also, it is wasteful to recalculate the amplitudes and frequencies in param_gen at each time step. If freque
  9. maehne
    Thanks @Runip Gopisetty for this detailed feedback on the SystemC datatypes! It is highly appreciated! Feel free to report additional issues and suggestions for improvements!
  10.    maehne reacted to a post in a topic: Seeking Feedback on Datatypes
  11. maehne
    How about connecting all your nodes via the fifos to your communication manager? Then, the communication manager can internally manage how to route data received from the nodes based on your scenario? This would keep the structure of the model static while the actual communication paths change over the course of simulation.
  12.    A_Hoss reacted to a post in a topic: Systemc executable cannot be built
  13. maehne
    Good to read that you got it working now!
  14. maehne
    To fix the issue, you can simply create a symbolic link lib-linux64, which points to lib, inside your SystemC installation directory /home/computation/Desktop/systemc-2.3.3-install using: cd /home/computation/Desktop/systemc-2.3.3-install ln -s lib lib-linux64 The experimental CMake-based build system distributed with SystemC provides to this end the setting INSTALL_LIB_TARGET_ARCH_SYMLINK. If enabled (default is OFF), the symlink is automatically created during installation of the SystemC library. Ideally, all SystemC-related libraries would provide a CMake-based build system, which wo
  15. maehne
    Directly editing the Makefiles generated by the GNU autotools is not recommended. You have to set it prior before doing "configure" to ensure the sources are correctly set up. As C++'11 support is marked as experimental for g++ 5.2.0, it is well possible that its C++ standard library implementation is not complete. I recommend you to try with a more recent C++ compiler, which defaults to C++'11 or later. The accompanying README and INSTALL documents of the libraries list on which platforms the libraries were tested including compiler versions.
  16. maehne
    GCC 5.2.0 is an old compiler that still defaults to C++'98 even though it contains experimental support for C++'11. "std::enable_if" was introduced in C++'11. Therefore, it may work if you recompile all your SystemC-related libraries and applications with explicitly turned on support for C++'11 by adding "-std=gnu++11" as command line argument to the compiler calls. Most reliable is probably by setting the CXX environment variable.
  17. maehne
    Happy new year @Paul Floyd! Thanks for the further analysis and proposed patch! We'll have a look on it.
  18.    maehne reacted to a post in a topic: A few Valgrind issues
  19. maehne
    Thanks @Paul Floyd for this additional information and analysis! It is very helpful to be able to reproduce the issues on our side and to fix them.
  20.    maehne reacted to a post in a topic: A few Valgrind issues
  21.    maehne reacted to a post in a topic: A few Valgrind issues
  22. maehne
    Thanks @Paul Floyd for reporting the issue! I have forwarded it to the SystemC LWG. Could you please provide some more details about your OS environment, compiler/valgrind versions as well as the version of the SystemC library and regression test suite for which you observed the issues?
×
×
  • Create New...