Whole program js #196
Merged
Whole program js #196
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
…, where we do not care.
|
Update: I am done homogenizing the different backends. This should make it slightly easier for Machine (LLVM, JIT) and mlton to generate code. More importantly. Aggregating all dependencies into a single file is now performed in ONE location. This is important since this way all backends can rely on this fact and do not have to deal with imports anymore. Even more importantly, we can perform whole program optimizations once for all backends (@fritzladwig). |
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.
WIP.
Idea: also use whole program compilation in JS. We do need to support some form of separate compilation for the website (for performance reasons and to avoid calling
evalover and over again -- which results in a quadratic explosion).However, I first want to make the JS backend conform with all the other backends and THEN think about how to support the website again. Maybe this results in a design that works better in the common case.
For example, it would be fine to not run optimizations on the code generated for the website (so optimizations can be whole-program).