Philipp van Kempen

@JoGei Make sure to squash the commits when merging the PR.

> It seems the linter check in the GitHub Actions pipeline is failing. Is the cause of the failure this warning: `Warning: lambda capture 'instr' is not used`? I could...

@JoGei build matrix changes broke the merge requirements again. Let me know if i should update them (other prs will need a rebase after this is merged)

@JoGei Ubuntu 24.04 does not have binary distributions for LLVM11 anymore. We are using some deprecated API in our LLVMJIT and I couldn’t yet manage to port it to newer...

can we just rewrite this to use `if (int i = start; …)` and pass `start=1/0` via an optional argument? Alternatively, there should probably another constructor which starts at 0.

@JoGei my priority would be to drop the need for LLVM 11 which is not available for Ubuntu 24.04+. Looking into performance improvements has minor relevance, at LLVMJIT is rarely...

Adding an LLVM-IR based ETISS JIT would be indeed interesting but I have doubts that it would help a lot. Before anybody invest X months into it, we should first...

One minor comment: C/C++-Programs usually have `signed int` exit codes from main. The semihosting handles them as `etiss_uint32`. On the POSIX-side (program exit codes) all codes are truncated to `uint8`...

**New:** - Implemented `SYS_EXIT_EXTENDED` support - Expose exit-code related settings via bare_etiss_processor: - `vp.print_exit_status`: Print status after simulation (default: `true`) - `vp.check_exit_status`: ETISS should return a non-zero exit code if...

Target SW side changes: https://github.com/tum-ei-eda/etiss_riscv_examples/pull/10/commits/ba7ff7a43627ca59eb8dc01198dc7f7f86eb4072