| Issue |
123947
|
| Summary |
Finalise setup of buildbot for RISC-V RVA23 EVL tail folding
|
| Labels |
backend:RISC-V
|
| Assignees |
|
| Reporter |
asb
|
This requires a builder with:
`-march=rva23u64 -mllvm -force-tail-folding-style=data-with-evl -mllvm -prefer-predicate-over-epilogue=predicate-else-scalar-epilogue'` and ideally qemu settings `rvv_ta_all_1s=true,rvv_ma_all_1s=true,rvv_vl_half_avl=true` to maximise the chance of finding bugs. This will be done using the same cross-compile and then execute under qemu-system setup used for the RVA20 bot. Not all items below are specific to the RVA23 bot.
This requires:
* [x] Update to QEMU 9.2.0 and check for no regressions
* [x] Redeploy x86-64 host with appropriate config
* [x] Resolve sporadic failures due to running out of disk space.
* Bumping the size of llvm-project.img worked. Issues were sporadic seemingly due to varying test order meaning disk size limits were sometimes reached with temporary files but sometimes not.
* [x] Get a working local debug flow for subsets of the LLVM tests (`ninja check-llvm-executionengine` for instance fails to work due to llvm-lit being invoked from a different subdirectory and lit-on-qemu not handling this)
* [x] Investigate and fix failures for MCJIT/ExecutionEngine tests
* Issue was a failure to set `-DLLVM_HOST_TRIPLE=riscv64-linux-gnu` leading to a confusing compilation flow for mcjit/executionengine
* [x] Resolve issues with host python3 path not matching the one under qemu-system (e.g. when using pip on the host)
* Explicitly passing `-DPython3_EXECUTABLE=/usr/bin/python3` resolves this
* [x] Resolve issues with buildbot running under python3.13 on the host
* Manual fix for pipes.quote usage and depend on legacy-cgi installed via pip
* [ ] (non-blocking issue) Document Python 3.13 workarounds in docs on local builder testing
* [ ] Resolve test failures for small subset of tests that try to use lit-on-qemu (set through `-DLLVM_EXTERNAL_LIT`) internally. Seems to primarily be the update_test_checks tests.
* Could potentially mask these tests, or alternatively find a way to override the lit path for just these tests, or set up lit-on-qemu in the correct path under qemu-system that just forwards to lit.
* [ ] (non-blocking issue) Figure out why MCJIT/ExecutionEngine tests aren't running with e.g. `ninja check-llvm-executionengine` (marked as 'unsupported', even the RISC-V ones).
* [ ] Receive review on PR to switch over rva23 evl builder https://github.com/llvm/llvm-zorg/pull/358
* [ ] Finalise x86-64 host deployment for rva23 evl builder once llvm-zorg#358 lands
* [ ] Test enabling the test suite locally and resolve any issues
* [ ] Enable the running of the test suite on rva23 evl builder
* [ ] Evaluate what other LLVM subprojects can/should be enabled in this setup (and expand this list to cover that work)
![]()
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
