Unai Martinez-Corral

> But since it seems like 5.0 is upcoming, this may be something to consider. We cannot deprecate gtkwave arguments in the next release. We need to first release a...

Can someone with access to Riviera-PRO test this change/enhancement?

Storage is not critical, because CI environments are removed after execution, so we can generate them unconditionally in CI and then decide explicitly whether we want to keep the waveforms....

@sckoarn since VHDL does not have built-in or canonical build and test execution management features (for context, see https://gitlab.com/IEEE-P1076/VHDL-Issues/-/issues/13), additional code is required. With VHDL 2019, a solution might be...

@bpadalino I understand the theory, but I find it to fall short in practice. What solution would replace the functionality that VUnit provides? VUnit requires 5 lines of VHDL code...

See https://github.com/VHDL/Compliance-Tests/blob/main/run.py#L14-L18. That allows to detect when we are using GHDL and conditionally do `check_call(['ulimit', '-m', ...])`.

@bpadalino I think it does. It needs refactoring, as discussed above, but the additional tests introduced in this PR are not covered in the master|main branch yet.

@bpadalino merged #19 and #21 and updated #22. I'm unsure about #20, since we might want to discuss what to do in such cases (tools implementing features differently). With regard...

See #1674.

Since gtkwave is a GitHub organisation now (see https://github.com/gtkwave/gtkwave/issues/3) it would be straightforward to move the waveform utils/libs (https://github.com/gtkwave/gtkwave/tree/master/lib and https://github.com/gtkwave/gtkwave/tree/master/contrib) to a sibling repo and have it submoduled in...