3 ms·
I heard that gcc didn't free() memory because compilation speed is important and the compiler process was expected to be short-lived. I don't know if that is (s
by cpeterso 7y ago
I heard that gcc didn't free() memory because compilation speed is important and the compiler process was expected to be short-lived. I don't know if that is (still) true, but it sounds reasonable to me.
- ben-schaaf 7y agoD doesn't do this (there's a flag now, not sure how well it works), if you've got a lot of compile time functions running the compiler process will rack up GBs of memory pretty quickly, especially if you're compiling in parallel. I upgraded to 32GB of RAM so I wouldn't hit swap when compiling.