Shrink code bloat due to error handling #1584
Comments
athas
added a commit
that referenced
this issue
Feb 4, 2022
Previously, every error point would contain code to free every memory block in scope. This caused significant code duplication. Now they jump to a shared function epilogue that frees all memory blocks. Closes #1584.
athas
added a commit
that referenced
this issue
Feb 4, 2022
Previously, every error point would contain code to free every memory block in scope. This caused significant code duplication. Now they jump to a shared function epilogue that frees all memory blocks. Closes #1584.
athas
added a commit
that referenced
this issue
Feb 4, 2022
Previously, every error point would contain code to free every memory block in scope. This caused significant code duplication. Now they jump to a shared function epilogue that frees all memory blocks. Closes #1584.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The C code generator must take care to avoid leaking memory during program failures, but the way it currently does it is very stupid and leads to code bloat. This should be improved.
The text was updated successfully, but these errors were encountered: