Proposal: run WrongGPU's D3D12 and launcher tests on Linux under Wine with a Proton install

未關閉
#51 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
35/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
cpp, linux, numpy, python
領域
testing, tooling

研究方向

Start by reviewing the proposed runner in clean/linux/run_wine_tests.py and the changes it requires in clean/runtime/interop/tests/run-tests.sh; the issue says an implementation already exists on a fork. Check how it runs the four named test groups and whether the documented Proton setup and results are reproducible. Done means the runner reports PASS, FAIL, or SKIP for each test and the required interop script changes work as described.

由索引模型根據 Issue 內容生成。

描述

area: build-ci area: linux build

Why

Under Proton, WrongGPU meets a different D3D12 stack: vkd3d-proton with dxil-spirv on RADV, DXVK's DXGI, and Wine's d3dcompiler_47. #7 (Wine's shader compiler) and the AGS matrix-instruction translation (dxil-spirv PR #362) only show up there.

A small runner makes those checks repeatable on any Linux machine with an RX 9000 card and a Proton install. That includes your retest request in #7.

What I have (clean/linux/, Python with NumPy plus MinGW-w64; on my fork as test/linux-wine-runner, two commits on main)

clean/linux/run_wine_tests.py --proton <Proton folder> [--vkd3d <self-built vkd3d-proton folder>] [--runtime <wronggpu_runtime.dll>] sets up a Wine prefix the way Proton sets up a game's: vkd3d-proton, DXVK's dxgi and Wine's vkd3d libraries. It then runs four tests, each reporting PASS, FAIL or SKIP:

  • interop: the existing clean/runtime/interop/tests/run-tests.sh, 31 tests, compiled against Wine's own d3dcompiler_47;
  • rr-leak: the RR test host's tagloop job from #11, with the 256 MiB limit of the Windows end-to-end test;
  • ags-layout: wg_ags.hlsli's WMMA and conversion helpers on fixed register values, against a CPU reference of the gfx12 register layout (that's what dxil-spirv's translation has to preserve);
  • launcher: the launcher's four unit-test programs, a WRONGGPU_TESTING MinGW build run under Wine.

run-tests.sh needs two small changes: -fms-extensions for clang-based MinGW (the __try in descriptor_publish.h), and a way to pick Proton's wine over a system wine64.

Results on current main (a8500cb), RX 9070 XT, RADV, synthetic data only, with a vkd3d-proton built from vkd3d-proton 5b1089c8 plus #362's three code commits:

  • All four tests pass under GE-Proton 11-11: interop 31/31, rr-leak +37 MiB, ags-layout 7/7, launcher 71/225/186/18 checks.
  • interop, ags-layout and rr-leak also pass under Proton Experimental 11.0-20261105c, Proton-CachyOS 11.0-20260703, DW-Proton 11.0-15 and Proton 11.0.
  • #7 retest: interop passes 31/31 on main under all five. Before #12 it was 29/31, with "Unknown modifier globallycoherent".
  • #14 under Proton: your native_probe_test (MinGW build, run under Wine) passes on the RX 9070 XT with that vkd3d-proton under all five Protons. With WG_TEST_DRIVER_PROBE_FAIL=1 it reports "probe mismatch at float 7". With Proton's stock vkd3d-proton the probe kernel fails at CreateComputePipelineState, as expected without #362. test_wmma_probe.cpp also passes with Linux clang.

Each test fails on what it targets:

  • rr-leak: +2636 MiB with a runtime from before #11;
  • ags-layout: fails on stock vkd3d-proton, and rejects lane-swapped and half-swapped results;
  • launcher: fails when a check is broken on purpose.

Nothing in it runs on Windows or in CI.

If you'd like it in the repository, I can open a PR from that branch.

One more Linux note: tools/ci/run_python_tests.py fails 18 emulator and vector-table modules on Linux, the same on unchanged main. Most come from compiling the HIP kernels with Linux's clang, which lacks the AMD GPU builtins (__builtin_amdgcn_readfirstlane, the "+s" asm constraint). One test also writes a file called nul. That may be useful for #4.

Related: #7, #10, #14.

主要語言
C++
星號
12
分支
2
平均合併
3 小時 10 分鐘
30 天內合併 PR
171

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

phantoslayer21/wronggpu 的其他 Issue

查看 phantoslayer21/wronggpu 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。