Which ghdl (llvm/gcc) and which VUnit are a known good combination? - ghdl

Question

I'm trying to get into the VUnit stuff and have been playing around with some tutorials which worked nicely so far. So, I became curious and found the example array_axis_vcs inside the VUnit GitHub repo. First things first, I cloned the VUnit nightly (02/13/23) and tested the example without any changes to it, using GHDL V1.0.0 which is the Ubuntu 22.04 default version. The result is that the example fails on execution of run.py *.test with the following output:
Starting lib.tb_axis_loop.test Output file: /home/me/vunit/examples/vhdl/array_axis_vcs/vunit_out/test_output/lib.tb_axis_loop.test_260bb5c8c675e898eca5dc9024a4420ede12c0bc/output.txt
******************** GHDL Bug occurred ***************************
Please report this bug on https://github.com/ghdl/ghdl/issues
GHDL release: 1.0.0 (Ubuntu 1.0.0+dfsg-6) [Dunoon edition]
Compiled with GNAT Version: 10.3.1 20211117
Target: x86_64-linux-gnu
/home/me/vunit/examples/vhdl/array_axis_vcs/
Command line: /usr/bin/ghdl-mcode --elab-run --std=08 --work=lib
--workdir=/home/me/vunit/examples/vhdl/array_axis_vcs/vunit_out/ghdl/libraries/lib
-P/home/me/vunit/examples/vhdl/array_axis_vcs/vunit_out/ghdl/libraries/vunit_lib
-P/home/me/vunit/examples/vhdl/array_axis_vcs/vunit_out/ghdl/libraries/osvvm
-P/home/me/vunit/examples/vhdl/array_axis_vcs/vunit_out/ghdl/libraries/lib tb_axis_loop tb
-gtb_path=/home/me/vunit/examples/vhdl/array_axis_vcs/src/test/
-grunner_cfg=active python runner : true,enabled_test_cases : test,output path : /home/me/vunit/examples/vhdl/array_axis_vcs/vunit_out/test_output/lib.tb_axis_loop.test_260bb5c8c675e898eca5dc9024a4420ede12c0bc/,tb path : home/me/vunit/examples/vhdl/array_axis_vcs/src/test/,use_color : true --assert-level=error Exception SYSTEM.ASSERTIONS.ASSERT_FAILURE raised Exception information: raised SYSTEM.ASSERTIONS.ASSERT_FAILURE :
ortho_code-x86-emits.adb:1724 Call stack traceback locations:
0x7f1b6d0c1542 0x5605bde1ce35 0x5605bde1ede4 0x5605bde1ff55 0x5605bde15a9f 0x5605bde15c4f 0x5605bde08ef8 0x5605bde214df 0x5605be0d0c82 0x5605be0e3957 0x5605be078bd5 0x5605be0e39b2 0x5605be0d1bef 0x5605be0bc882 0x5605be0cddbe 0x5605be0c80a0 0x5605be10db55 0x5605be04c250 0x5605bdf8469e 0x5605be1114b3 0x5605bdd3cb07 0x7f1b6cc43d8e 0x7f1b6cc43e3e 0x5605bdd3b243 0xfffffffffffffffe
******************************************************************
Ok, maybe the pretty outdated GHDL Version is a problem here? Let's try the latest GHDL nightly. Perhaps it's already solved there. That's what I thought and downloaded the latest GHDL nightly to a clean testVM and also downloaded the latest VUnit there.
Different setup, different (more interesting) issues.
VUnit appears to be unable to identify the LLVM backend of ghdl:
me#testVM:~\testprj$ python run.py *test
ERROR - Could not detect known LLVM backend by parsing 'ghdl --version' Expected to find one of dict_keys(['mcode code generator', 'llvm code generator', 'GCC back-end code generator'])
== Output of 'ghdl --version'============================================================
GHDL 3.0.0-dev (2.0.0.r1367.g803edb716) [Dunoon edition]
Compiled with GNAT Version: 10.4.0
llvm 14.0.0 code generator
Written by Tristan Gingold.
Copyright (C) 2003 - 2022 Tristan Gingold.
GHDL is free software, covered by the GNU General Public License.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. =========================================================================================
For my current work, I'll go and try a prebuild docker container now, but I'm still interested in solving this issue. Any ideas? Anybody tried the actual VUnit build against the actual ghdl build? I would be interested if it is a concern on my machine or a more general difficulty. 
Greets Stefan