[PLACEHOLDER] abolish using passes in the compiler; simplify compilation pipeline #21402
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
|
I know that I don't work much with compiler code, but isn't the whole point of compiler passes to simplify and organize its logic? So that you don't have semantic checking, code generation, etc. all mixed together? |
|
It won't be mixed together but the order of the passes will be explicit in the code rather than hidden in an array that is filled at runtime. |
|
As a bonus, the memory consumption seems to reduce a little bit for now. 611.3 MiB => 599.766 MiB peak mem on my platform. |
12 tasks
|
Succeeded by #21444 |
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.
ref nim-lang/RFCs#503
follow up #21379
The
processModuleshould handle all the logics by calling parser, sem, transf, codegen in order.