Lower mutable scalar globals through Whale tracked global storage

Aperta
  • Qualcosa non va?
#1,033 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
32/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
compilers

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
Rust
Stelle
56
Fork
21
Merge medio
23h 20m
PR unite (30g)
45

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di wavefnd/Wave

Tutte le issue di wavefnd/Wave

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.