Lower mutable scalar globals through Whale tracked global storage

Abierto
  • ¿Algo no está bien?
#1,033 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
32/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
rust
Área
compilers

Línea de trabajo

Start by reading whale/src/codegen/mod.rs and the upstream ir/src/global_storage.rs API, then discuss the unresolved semantics with @LunaStev before implementing anything. Confirm how frontend types and initializers map to tracked module-owned storage, including execution lifetime and uninitialized, readonly, and memory-budget behavior. Done means multiple functions share the same initialized global while immutable constants, local shadowing, and unsupported globals remain unchanged.

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

Descripción

discussion enhancement help wanted

Motivation

LLVM accepts a mutable static X and X+=1, while Whale rejects mutable global storage. Official Whale a48f74ad now has addressable GlobalStorage distinct from compile-time constants, with initialization and readonly validation. Wave still locks the older API.

Starting point: whale/src/codegen/mod.rs:23.

Validation

Audited canonical Wave 540728c2eb6cc12f5c69c3fb3fdb96e07ba059a4 (0.0.1-alpha-dev), whose tree matches the local checkout. Validation: Executed mutable-global capability probe and inspected official GlobalStorage API. Executed compiler probes use the matching checkout-built compiler and std on Linux amd64 (Rust 1.89.0 / LLVM 21.1.8). Source/header or mocked checks are not native execution on another OS.

Official GlobalStorage API.

Scope

After #996, map the approved scalar global subset to tracked module-owned storage. Use frontend types/initializers and clarify per-execution lifetime/state expectations before implementation.

Related: #996, #874. These links do not claim those broader or completed scopes are unfinished.

Design discussion required

This issue records a proposal or an unresolved contract; it is not approval to choose new semantics. Please mention @LunaStev to discuss the design before starting implementation.

Completion criteria

  • Multiple functions observe the same initialized global within an execution.
  • Uninitialized/readonly/memory-budget behavior follows verified upstream semantics.
  • Immutable constants, local shadowing and unsupported globals retain existing behavior.
Lenguaje dominante
Rust
Estrellas
56
Forks
21
Merge medio
23 h 20 min
PR fusionados (30 d)
45

Preparar el entorno

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 wavefnd/Wave

Todos los issues de wavefnd/Wave

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.