Remove support for linear memory in the cheerp-genericjs target #232
Conversation
This file contains 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
This was always just theoretical, and just a pain to support. The result is mostly a simplification of GDA and the CheerpWriter, that don't have to try and figure out if there is any linear memory used in the module: if the target is cheerp-wasm, there is; otherwise, there isn't. The other main change is in the exceptions ABI, where __cheerp_landingpad is not always in linear memory, but it's genericjs for the cheerp-genericjs target. This required changing the fist field from void* to int32, and casting appropriately. TODO: frontend check to forbid use of the wasm attribute on the cheerp-genericjs target
|
Merged, there was a conflict with the (now unneeded) recent fix for global delete |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.