Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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 336
    • Issues 336
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Infrastructure Registry
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sac-group
  • sac2csac2c
  • Issues
  • #1687

Closed
Open
Created Nov 29, 2006 by Robert Bernecky@rbeDeveloper

memory intensive wrapper type representation

Bugzilla Link 331
Created on Nov 29, 2006 23:48
Resolution REMIND
Resolved on Nov 30, 2006 09:35
Version 1.00beta
OS Linux
Architecture PC

Extended Description

I'm trying to test a fix to IVE performance problems, and tried to compile demos/livermore/loop8p.sac. It eventually used up about 3.5GB of dram, then ran out of system memory. This using standard make options. For such a dinky program, this is not good news...

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking