deps: backport V8 LLE alias fix to 26.x and 24.x
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- JavaScript
- Estrellas
- 122k
- Forks
- 37.4k
- Merge medio
- 4 d 2 h
- PR fusionados (30 d)
- 283
Descripción
Summary
Please backport V8 commit b44239fe / V8 bug 554421904, "Turboshaft LLE: non-writing calls can create aliases", to the active Node.js 26.x and 24.x release lines.
This is the same upstream V8 miscompilation tracked in #66083 for 26.x, but 24.x is also affected by default: Node 24 ships V8 13.6 with Turboshaft load elimination enabled by default, and the minimized reproducer returns the wrong value there too.
Version
Reproduced locally with:
v26.9.0/ V814.6.202.34-node.32v24.18.0/ V813.6.233.17-node.50
Source check after fetching current tags/branches:
upstream/v26.xandupstream/v26.x-staging: V814.6.202.34, noregress-554421904testupstream/v24.xandupstream/v24.x-staging: V813.6.233.17, noregress-554421904test
Platform
macOS arm64
This appears to be a compiler optimization bug rather than platform-specific behavior.
Subsystem
V8 / deps
What steps will reproduce the bug?
Run the minimized reproducer from #66083 with native syntax enabled:
node --allow-natives-syntax v8-lle-poc.js
I also checked the relevant runtime flag defaults:
26.x:--turboshaft-load-eliminationis enabled by default24.x:--turboshaft-load-eliminationis enabled by default22.x:--turboshaft-load-eliminationis disabled by default, so this request is intentionally limited to26.xand24.x
How often does it reproduce? Is there a required condition?
It reproduced consistently for me on both default-affected lines listed above.
The reproducer requires optimized code and the Turboshaft load-elimination pass. That pass is enabled by default on the Node 26 and Node 24 builds tested.
What is the expected behavior? Why is that the expected behavior?
The store to staleArray[7] should be preserved, so the returned array slot should contain 1.1:
staleArray[7]: 1.1 | expected: 1.1 | OK
RESULT: NOT TRIGGERED on this build
What do you see instead?
Node 26:
v26.9.0 V8 14.6.202.34-node.32
staleArray[7]: undefined | expected: 1.1 | WRONG!
RESULT: BUG TRIGGERED — Turboshaft LLE eliminated a valid store
Node 24:
v24.18.0 V8 13.6.233.17-node.50
staleArray[7]: undefined | expected: 1.1 | WRONG!
RESULT: BUG TRIGGERED — Turboshaft LLE eliminated a valid store
Additional information
The upstream fix is small and directly addresses the alias invalidation ordering in Turboshaft late load elimination:
- Fix: https://chromium.googlesource.com/v8/v8/+/b44239fe
- Review: https://chromium-review.googlesource.com/c/v8/v8/+/8345010
- V8 bug: 554421904
The current 26.x and 24.x V8 snapshots still have the vulnerable early !op.Effects().can_write() bailout before invalidating non-aliasing inputs in deps/v8/src/compiler/turboshaft/late-load-elimination-reducer.cc.
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.
Línea de trabajo
Comienza con deps/v8/src/compiler/turboshaft/late-load-elimination-reducer.cc y compara los snapshots activos de V8 26.x y 24.x con el commit upstream b44239fe. Ejecuta v8-lle-poc.js usando node --allow-natives-syntax en ambas líneas de release y verifica después que el fix upstream y la cobertura de regress-554421904 están presentes y que el reproductor devuelve 1.1.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- javascript
- Área
- compilers, release
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Activo
- Claridad
- Bien especificado
- Aptitud para principiantes
- 52/100