Repository navigation
shader: complete native task/mesh translation - #1
Merged
Merged
Conversation
Ampere opcode 0x923 mode 0xb800 reads the task payload written through opcode 0x927 mode 0xb800. Keep this view distinct from the mesh stage's task-input view and cover it with a hand-encoded TaskEXT fixture whose loaded word controls OpEmitMeshTasksEXT.
This was referenced Nov 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
F2IP.U8byte packing0xb8payload outputThis PR is based on the public Switch 2 native foundation commit
96cc0e883c80117e51342c60facfae2f0e600b9a. The repository currentmainis a newer Android/Mac fork that does not contain that foundation, so this explicit base keeps the GPL translator delta small and reviewable.Checks
test_dmsh_ampere_mesh.py: 11/11 synthetic fixtures passtest_dmsh_raw_reuse.py: 3/3 hint/cache/loop/vector fixtures pass, including the vector-end guardspirv-val --target-env vulkan1.3t_vk_meshpassed4c7d6be5a7717c8d: raw SPIR-V 615,692 -> 476,064 bytes and integer helper calls 529 -> 166 versus the checked per-access fallbackM1 Pro hardware evidence
The pre-guard vector build
ab421bce, chain5ab967c9784e, ran the same guarded Link-house idle route with an image identical to baseline:7d7af71bba3: frame 40.18 ms, GPU 35.93 ms9cc3e7c7497: frame 34.62 ms, GPU 30.54 ms~25 -> ~29 fps)Triangle lowering is byte-identical between the two Mesa commits, so the comparison is valid. The final
d83d66abguard was then confirmed on the same hardware route with an identical image at 35.13 ms frame / 31.02 ms GPU; its 12 recompiled producers had maximum 117,873 and p50 54,088 instructions, with 410 top spills. This is evidence for the bounded idle route, not Vulkan conformance or full playability.