D3D12 Swin kernels: weight staging stores the last chunk from several threads

Aberta
#118 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
35/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa

Direção de pesquisa

Start in clean/dx12/kernels/swin_block.hlsl, at the weight staging code for the partial row where threads past the last 16-byte chunk write to the same groupshared addresses, and compare it with the HIP version the issue cites. The change is a store guard on the chunk index against the chunk count, with the barrier kept. Done means the guard is in place, the bit-exact checks pass for every kernel built from the template, and the DXIL hash record is regenerated.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

In the D3D12 Swin block template (clean/dx12/kernels/swin_block.hlsl, weight staging), when the number of 16-byte chunks is smaller than the thread count of the group, the threads past the last chunk all store that last chunk to the same groupshared addresses. The stored values are identical, and no wrong output has been observed, but the HIP version has exactly one writer per address and the D3D12 version should match it instead of relying on how the driver treats overlapping stores.

Applies to every channel count, including Model M's shipped kernels and the C = 32 block of Model L (#117).

Fix: in the partial row, store only when the thread's chunk index is below the chunk count; keep the barrier. Because this changes Model M's shader binaries, the change needs the bit-exact checks and the DXIL hash record redone for all kernels built from the template.

Found in review of #117. Refs #89

Linguagem predominante
C++
Estrelas
12
Forks
2
Merge médio
3h 10min
PRs com merge (30d)
171

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de phantoslayer21/wronggpu

Todas as issues de phantoslayer21/wronggpu

Issues semelhantes

Mais issues de C++

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.