RAM map: direct-page layout per mode for struct storage #14

New issue

Open

opened 2026-10-29 10:17:14 +00:00 by Gatchan · 0 comments

Gatchan commented

2026-10-29 10:17:14 +00:00

Owner

Open question from the RAM map slice 1 (refs #7, docs/ram_map.md).

The direct page $00-$FF is described as one [[var]] per concept with mode = [...]. That is fine for the wram storage phase (accessors read the emulated WRAM). When a subsystem switches to storage = "struct", the generator must emit one C structure per mode and a projection back to WRAM. Decide then whether the map gets one region/struct per mode (dp_field, dp_battle, dp_btlgfx ...) or whether the generator groups the vars by mode.

To do with the first subsystem that switches to struct storage.

Open question from the RAM map slice 1 (refs #7, `docs/ram_map.md`). The direct page `$00-$FF` is described as one `[[var]]` per concept with `mode = [...]`. That is fine for the `wram` storage phase (accessors read the emulated WRAM). When a subsystem switches to `storage = "struct"`, the generator must emit one C structure per mode and a projection back to WRAM. Decide then whether the map gets one region/struct per mode (`dp_field`, `dp_battle`, `dp_btlgfx` ...) or whether the generator groups the vars by `mode`. To do with the first subsystem that switches to struct storage.

Gatchan added the

task

tools

labels

2026-10-29 10:17:14 +00:00

Gatchan referenced this issue from a commit

2026-10-29 10:20:20 +00:00

docs: RAM map slice 1 in re/ram_map.toml, format and decisions in docs/ram_map.md (refs #7)

Gatchan referenced this issue

2026-10-29 10:37:17 +00:00

RAM map slice 1, generated state accessors, peek/poke by name #18

Gatchan referenced this issue