Fix RAM usage by splitting deeply nested expressions #783
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.
Fix #777
TREE_VISITEDon theADDR_EXPRinplayback::function::get_addressand theADDR_EXPRinplayback::lvalue::get_address. (edit: doesn't work)I was able to build
cargowith 5-10 GB RAM while it used to take +64 GB.This function would generate deeply nested expressions which made GCC use huge amount of RAM.