Public bug reported: Verilator v4.028 and newer has a bug (v4.016 works OK) in that it doesn't emit constructor calls for ports when used in SystemC mode. This affects applications that rely on such names and also all SystemC tracing. It breaks some of Xilinx's Open Source QEMU + RTL co-simulation flows.
A fix was recently committed on the master branch: https://github.com/verilator/verilator/pull/2500 Would it be possible to get a backport of this fix into Ubuntu 20.04? I can create the backport if you let me know in what format you'd need it in. Best regards, Edgar ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: verilator 4.028-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 17 12:01:32 2020 InstallationDate: Installed on 2019-12-23 (237 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: verilator UpgradeStatus: Upgraded to focal on 2020-07-31 (16 days ago) ** Affects: verilator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891881 Title: Verilator generates wrong portnames in SystemC mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/verilator/+bug/1891881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
