Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

ILP32 gate examines TUs as they are AFTER the recipe, not as the recording call saw them

Cerrado
  • ¿Algo no está bien?
#1,257 0 comentarios 0 reacciones 0 asignados Ver en GitHub

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
38/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c
Área
compilers

Línea de trabajo

Start with the retained reproducer at /tmp/critic-astra-r6-plants/2-temporal-source/tools/ilp32_syntax_check.sh and trace the recording stand-in through examine_tus and compile_tu. Ensure each recorded call uses its own input-TU snapshot rather than the later sandbox contents, then verify the reproducer catches the first invocation's fault.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:gates found-by:critic kind:gate-defect

Stated residual from PR #1225 round 7 (item 10; Astra's rank 3 on head 1b5c64d).

examine_tus reads each translation unit from the sandbox after the whole recipe has finished, not from a snapshot taken at the call that recorded it. So a recipe that writes #error into a unit, compiles it, then overwrites that same path with valid C before a later call is examined on the later bytes and passes, while the real first invocation saw the fault.

Reproducer (Astra, retained): bash /tmp/critic-astra-r6-plants/2-temporal-source/tools/ilp32_syntax_check.sh — the standalone gate passes 24 TUs; the actual frontend rejects the first call. A full-runner escape was not claimed for this shape.

Closing it means the recording stand-in copies (or hashes and copies) each call's own input TUs into that call's record directory, and examine_tus/compile_tu read the snapshot rather than the live sandbox path. That is a recorder redesign, not a local edit, which is why round 7 stated it instead of rushing it after the flags work (#1232) needed two follow-up fixes of its own.

Same family as #1232: the gate's compilation context must be the recipe's context, in time as well as in flags.

Refs #1165 #1225 #1232.

Lenguaje dominante
C
Estrellas
3
Forks
7
Merge medio
4 h 5 min
PR fusionados (30 d)
116

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de InauguralSystems/EigenScript

Todos los issues de InauguralSystems/EigenScript

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.