LekKit

Test `rv64mi-p-illegal` now passes. There are other new tests in my forked tree, which fail because there isn't an extension implemented which they are testing (Bitmanip, Zicbom, etc). So now...

As it turns out `u-boot/include/configs/sunxi-common.h` is pretty messed up in respect to RISC-V systems: - Doesn't think that RISC-V systems need compressed kernels? (`kernel_comp_addr_r` is under `#ifdef ARM64`) - Doesn't...

So apparently the repo kernel crashes because `initrd` overlaps some FDT memory region and it all goes wonky (This is after all U-Boot issues are sorted out). Likely fixable soon....

> regarding the `iwd` issue, can it be that you missed loading modules? (does `iwd` load them on its own??). Looking at the config, all listed config entries are included...

> `pinctrl` failes this is probably (very) bad. You mentioned to suspect the DTB somewhere, which one are you using? AFAIR it comes from uboot? At least it is supplied...

See https://lekkit.github.io/test/index.html and type doom X) Although, that WASM demo doesn't have a JIT, and overall is disgustingly slow, so 'ere are the firmware/kernel/drive images to replicate that setup locally...

Also this 👀, although the mod has stagnated sinсe february 2022 for... well you might have an idea why https://user-images.githubusercontent.com/50500857/222955992-0441835d-d245-468e-8030-c76849254cc3.mp4

Any update?)

> Tried on win11, no tweaking with -smp and -jitcache helps affecting doom performance, any reason why? what can be a bottleneck? Option `-jitcache` sets an upper bound on JIT...

Tried setting `-jitcache 64M`, `-jitcache 16M`, `-jitcache 4M`, `-jitcache 1M` with that Doom demo - no perf/CPU usage difference on a Linux host. CPU use is at ~10% of one...