Uh oh!
There was an error while loading. Please reload this page.
Free intermediate translation results as soon as possible - #8092
Conversation
alexcrichton
commented
Jul 28, 2013
Could you add a comment above it to explain why it looks a bit silly? Otherwise r+! |
This fixes the recently introduced peak memory usage regression by freeing the intermediate results as soon as they're not required anymore instead of keeping them around for the whole compilation process. Refs rust-lang#8077
This fixes the recently introduced peak memory usage regression by freeing the intermediate results as soon as they're not required anymore instead of keeping them around for the whole compilation process. Refs #8077
thestinger
commented
Jul 28, 2013
@dotdash: it might be clearer to use |
dotdash
commented
Jul 28, 2013
Does that work with @-ptrs? Looks like it would just cause an inc + dec on the refcount. |
alexcrichton
commented
Jul 28, 2013
Sadly I think it does refcount business with |
thestinger
commented
Jul 28, 2013
Ah, didn't realize these were managed pointers. Although, these should really be |
graydon
commented
Jul 29, 2013
Doh! I actually had it written this way but in a later commit in the wip branch I was working on this, because I was trying (and failing, due to too many @ boxes in the session) to put the earlier phases in a task and dump it (freeing the whole AST) before running LLVM passes. Thanks. |
This fixes the recently introduced peak memory usage regression by
freeing the intermediate results as soon as they're not required
anymore instead of keeping them around for the whole compilation
process.
Refs #8077