Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • sac2c sac2c
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 403
    • Issues 403
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sac-group
  • sac2csac2c
  • Issues
  • #1553
Closed
Open
Created Jan 31, 2006 by Robert Bernecky@rbeDeveloper

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
Assignee
Assign to
Time tracking