0.6.6: follow-ups from the Model K softmax self-check review (#254)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- cpp
- Área
- backend, performance
Línea de trabajo
Start by reading the review follow-ups in this issue and the implementation and tests for the create-time self-check introduced in #254. Trace preparation, embedded manifest and shader loading, digest generation, and the game-path executor's runtime creation. Done means the five listed gaps are addressed, with negative controls and boundary shapes tested and end-to-end creation measured on supported devices.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Follow-ups from the review rounds of #254 (Model K softmax weight rounding in one mixed-precision FMA, with a create-time self-check). None of them changes the output of a frame that passes the self-check. They are tracked here for 0.6.6.
1. Shape coverage beyond the sampled sizes
The self-check runs each selectable softmax stage at the window offsets the frames use, but only at sampled output sizes (for example, the m stage only at one large base). A defect that depends on the map size, such as a small m map or partial windows at an edge, could pass the check. Add shape-dependent negative controls, and cover boundary and partial-window shapes, or verify the compiled data flow independently of the sampled sizes.
2. Preparation that silently skips a port
The create-time preparation step returns success for a manifest entry whose variant does not match or whose root signature is unsupported, while the launch path later refuses the same entry. Such an entry, even with a corrupt shader, then passes create and fails on the first frame. Make preparation fail on these cases, and test them.
3. Stale embedded manifest and shader pairs
The manifest and each shader fall back to the embedded copies independently. A runtime built from a reused output folder could embed an old, matching pair, which then passes the integrity check when the loose files are absent. The fixed-weight stages are not in the output-hash self-check. Bind the embedded artifacts to the intended build's sources (the new per-entry source digests are a start), and refuse stale ones before embedding.
4. Self-check digest inputs and reference provenance
The digest that binds the reference header to its sources does not yet include the stage table and layout helpers, the FP16 conversion used to make the synthetic inputs, or the separately compiled probe. The header generator also stamps the current digest onto a reference build without checking that build's own provenance. Include those inputs, and verify the reference build before stamping.
5. Create time
Native create with the self-check takes about 1.7 s at 1440p Quality, and the game-path executor creates the runtime twice. Reduce the duplicate check (for example, reuse a verified result safely within one process), and measure end-to-end creation on supported devices.
- Lenguaje dominante
- C++
- Estrellas
- 12
- Forks
- 2
- Merge medio
- 3 h 10 min
- PR fusionados (30 d)
- 171
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de phantoslayer21/wronggpu
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
phantoslayer21/wronggpu#275 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
phantoslayer21/wronggpu#274 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
phantoslayer21/wronggpu#241 ·
Los mantenedores suelen responder en 1 día
-
bug build
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
phantoslayer21/wronggpu#234 ·
Los mantenedores suelen responder en 1 día
-
Launcher tests: "an older record: update available" fakes a version newer than the test buildAbiertobug build
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
phantoslayer21/wronggpu#233 ·
Los mantenedores suelen responder en 1 día
Todos los issues de phantoslayer21/wronggpu
Issues similares
-
ai_p2
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
ClickHouse/ClickHouse#132519 ·
Los mantenedores suelen responder en 1 día
-
[Bug]: VST3 getMidiControllerAssignment reads past midiControllerToParameter for program changeAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
juce-framework/JUCE#1810 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
petercorke/robotics-toolbox-python#952 ·
Los mantenedores suelen responder en 1 día
-
NatronRenderer: a Python error in the script (-t / project script) doesn't change the exit statusAbiertofunc:engine type:bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
NatronGitHub/Natron#1276 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 77/100
Los mantenedores suelen responder en 1 día