fixed: #59095
Update libcall signatures to use multivalue return rather than returning via a pointer
when the multivalue features is enabled in the WebAssembly backend.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
For the description, here's some possible clearer wording:
Update libcall signatures to use multivalue return rather than returning via a pointer when the multivalue features is enabled in the WebAssembly backend.
We also still don't have a stable C calling convention that uses multivalue, so this doesn't seem entirely future-proof, but maybe that's ok.
llvm/docs/ReleaseNotes.rst | ||
---|---|---|
145 | We don't typically add release notes for bug fixes like this (although maybe we should?) | |
llvm/test/CodeGen/WebAssembly/multivalue_libcall.ll | ||
1 | It would be good to use the utils/update_llc_test_checks.py script to automatically produce the test output. | |
4 | Incomplete sentence? | |
21–24 | I don't think the CHECK lines are actually being checked because FileCheck is only run with MULTIVALUE and NO_MULTIVALUE prefixes. |
LGTM besides using the test update script.
llvm/test/CodeGen/WebAssembly/multivalue_libcall.ll | ||
---|---|---|
5 |
Code LGTM, although it looks like there may be some missing cases reported in https://github.com/llvm/llvm-project/issues/59095. Testing the end-to-end integration here might be a good thing to do in cross-project-tests.
We don't typically add release notes for bug fixes like this (although maybe we should?)