0.6.6: follow-ups from the k_approx review (#257)

Ouverte
#262 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
cpp
Domaine
backend, testing

Piste de recherche

Start with the six follow-ups in this issue and inspect the named shader file, clean/k/dx12/hlsl/k_out.hlsli, plus the preparation, executor, mode-line, frame-note, and release-diagnostics code they refer to. First trace how selected variants are prepared and how runtime options reach Model K; then review each item’s tests and evidence requirements. Done means the six gaps are fixed or documented as requested, with focused tests or committed synthetic-data summaries for the relevant claims.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Follow-ups from the review rounds of #257 (Model K: the k_approx opt-in close approximations a1 and a2). They are tracked here for 0.6.6; none of them changes the default (nothing set) output.

1. Preparation of a selected form with an unsupported root signature

An otherwise valid manifest can declare a selected approximate form (for example k_out_pixel_c__a2) with a root signature the native device does not support. The loader accepts it, the create-time preflight checks only the name and code object, and preparation returns success without loading the shader, so create succeeds and the first launch fails. Make preparation fail for an unsupported signature or an unmatched variant, and test that malformed selected entry. (The same preparation gap is item 2 of #261.)

2. Non-vacuous selection tests

The approximation test never asserts the k_out_color__a2 launch: replacing only that selection with the exact colour kernel would still pass. The executor matrix reads back no output bytes. Assert every expected approximate launch and the absence of its exact counterpart, for buffer and direct frames and for each tag on its own. Compare direct-route frames byte for byte where an exact reference applies.

3. Mode line with a very long options variable

If the runtime options environment variable exceeds the interop parser's 4095-character limit, the front end reports that it ignored the value, while Model K reads the full variable independently and enables the approximation. The mode line can then say "exact". Derive the mode line from the runtime's effective selection, or use one options source, and test the long-value case.

4. Claims without committed records

A comment in clean/k/dx12/hlsl/k_out.hlsli states a one-ULP maximum and a difference rate for six seeds, and the PR description cites a shader-identity record and an executor negative-control record. Neither record is in the repository. Commit constructed-data summaries for these (synthetic inputs only), or qualify the claims.

5. Frame-note threading contract

wg_rt_take_frame_note hands over the same per-context note a frame can write, without synchronization. The executor calls it synchronously after a frame, which is safe, but the contract is not written down. Document that frame calls and note calls on one context must not run concurrently, or synchronize them.

6. The k_fill test option in release builds

The k_fill option fills Model K buffers with a test pattern and is accepted in release builds; it predates #257. Limit it to developer builds, as the other test hooks are, and add it to the release diagnostics check.

Langage dominant
C++
Étoiles
12
Forks
2
Merge moyen
3 h 10 min
PR mergées (30 j)
171

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de phantoslayer21/wronggpu

Toutes les issues de phantoslayer21/wronggpu

Issues similaires

Plus d'issues C++

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.