Mystery memory-eater in for loop?
| Bugzilla Link | 200 |
| Created on | Jan 31, 2006 00:18 |
| Resolution | FIXED |
| Resolved on | Feb 02, 2006 17:00 |
| Version | 1.00beta |
| OS | Linux |
| Architecture | PC |
| Attachments | rle.sac, mdiv.sac, crud5.sac, sliii.sac |
Extended Description
I'm not sure what's going on with the attached, but it dies at run-time, apparently in the middle of what looks like an innocent FOR loop, unable to allocate about 1 MB of memory, or so says the SAC run-time. The function slIII is the apparent villain, with sac2c -O3. Compiling with -check tb -noOPT fails in a similar way, but the system gets in a memory thrash (1.3 GB and rising) before the FOR loop completes. The slIII function starts, but never finishes, if the embedded print statements are to be believed.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information