If sac2c runs out of main memory, things just get worse!
|Created on||Aug 05, 2006 22:15|
|Resolved on||Aug 07, 2006 15:57|
If sac2c runs out memory, as it does when I try to compile shallow.sac on a machine w/ 1.5GB main memory (while a few other things are happening), I get this: ABORT: System failure while trying to execute shell command. ABORT: (e.g. out of memory). *** Compilation failed *** *** Exit code 6 (Running type inference system) *** 15845 Error(s), 0 Warning(s) over and over and over again! As much as I appreciate sac2c's diligence in attempting to retry after such a fault, things get worse, because the loop never terminates. So, EVENTUALLY, the session log fills up the hard drive. Then things get really bad! I'd suggest giving up after about a 100 repeated failures of this sort. Or maybe just 3.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information