Jump to content


  • Content count

  • Joined

  • Last visited

  1. I've just found out that SystemC-2.3.2 can be compiled with SC_INCLUDE_EXTRA_STD_HEADERS to include <cstring>. This should be used when configuring, right before make. With this, there is no need to modify SystemC-AMS header files. $ mkdir build $ cd build $ ../configure CXXFLAGS="-DSC_INCLUDE_EXTRA_STD_HEADERS" --prefix=/usr --otheroptions... $ make $ make install Cheers.
  2. Hello, SystemC 2.3.2 has improved support for C++11, but with that update, cstring has been removed from systemc.h header file. This implies in a breakage in systemc-ams build because sca_tdf_ct_ltf_nd_proxy and sca_tdf_ct_vector_ss_proxy uses memset and memcpy. A simple fix would be to include <cstring> to both headers: scams/impl/predefined_moc/tdf/sca_tdf_ct_ltf_nd_proxy.h scams/impl/predefined_moc/tdf/sca_tdf_ct_vector_ss_proxy.h
  3. Thank you for your reply, I've read the license file and there is a clause for redistribution. And yes, there is a notice. But when I run make install none of the documents files get installed, even though the folder /usr/share/doc/systemc-ams gets created. So I guess I'll have to manually copy them right after make install. I will also contact COSEDA to inform them of the package. I think it is a good idea. Thank you for your advice.
  4. Hello all, I've created an automated installation package for users of Archlinux. I've uploaded it to the AUR (Archlinux User Repository). This package can be installed automatically using yaourt or any aur capable tool. If installed, it will pull dependencies automatically, like the systemc package created by the user brookskd. Files will be installed to /usr/include and /usr/lib and will be managed by pacman or yaourt which means that you can uninstall them latter or update the package automatically if there is a new version available. By the way, I still have to update the license info. As far as I know the whole package is protected by Apache license 2.0, right? So it is ok to redistribute like this?
  5. dccafe

    Analog data formats used

    Here you go : +inf and -inf values are usually generated by an unwanted division by zero. If you run the following dummy TDF module, you'll obtain a +inf at the beginning. You can then use the vcd file as an input to your tool in order to reproduce the bug VCD output should be as follows Hope it helps, Daniel.
  6. dccafe

    Analog data formats used

    Hello! I've been using your tool for quite a while now and I'm really pleased with the overall eclipse integration. I have found a small bug though : Apparently, the tool does not interpret float values of -inf or +inf. It fails to print the waveform whenever it finds those symbols. As a solution, I suggest the gtkwave workaround ... It replaces those symbols by a virtual zero and prints the corresponding portion of the wave with a different color. Hope it helps, Cheers,