Tiago Gomes

Hi @nfrancque, I have dealt with some of your issues without changing VUnit source files and only using per-existing VUnit functionalities. > 1. Command line argument to select simulator, in...

I do have a Makefile on top of all of this, with some switches that allows me to easily start VUnit with any simulator from the console. The Makefile then...

@eschmidscs that approach will solve the 50% duty cycle behavior by providing 100% instead. But I am more concerned with the fact that different simulators have different behavior (modelsim vs...

@eschmidscs Thanks for the reply. I think we are in sync. Ideally the pop function should allow 100% throttle, but if that is not possible, I would then force TREADY...

@tgingold I was just about to report the same issue. Similar situation where a Xilinx library component is simulated using GHDL. The error is exactly the same as described above....

@tgingold In case it helps I also write down here the llvm version used for the working case vs failing case. Crashing one: ``` $ llvm-link.exe --version LLVM (http://llvm.org/): LLVM...

@tgingold I had to setup a new workstation with GHDL today (that uses an old CPU) and for my surprise I was able to run the simulation without crashing using...

Well, I think I found what really triggers the error... and it is not the GHDL version, LLVM version or CPU version... it is actually the Vivado version. If I...

FYI I upgraded to GHDL 3.0.0.r147 / LLVM 16.0.2: ``` $ ghdl --version GHDL 4.0.0-dev (3.0.0.r147.g6c56631a7) [Dunoon edition] Compiled with GNAT Version: 13.1.0 llvm 16.0.2 code generator Written by Tristan...

This 3-step flow would also solve this issue https://github.com/VUnit/vunit/issues/877