Materialize module constants in dev run images#10241
Merged
Merged
Conversation
rtfeldman
marked this pull request as ready for review
July 19, 2026 18:47
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Module-level stored composite values were re-materialized at each use in the default dev pipeline because it omitted internal static-data lowering and the dev run image had no complete readonly-data path. This separates host-provided data exports from internal static values, embeds internal materializations and explicit relocations in dev images, and resolves generated-function pointers against image code symbols so constant access shares one immutable runtime value. Fixes #10219.