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
  • #2174
Closed
Open
Created May 11, 2010 by Robert Bernecky@rbeDeveloper

Livermore Loop 13 SAC vs. C code not equivalent

Bugzilla Link 708
Created on May 11, 2010 19:19
Version unspecified
OS Linux
Architecture PC

Extended Description

The repository copy of SAC Loop 13 code reads its input from a file;
the C version has the input hard-coded into the source program.
The entire SAC benchmark executes in about 36msec, and the C
version in 7msec.
One of the benchmarks should be changed, so that they are equivalent.
Until that time, any performance measurements on Loop13 should be considered 
bogus.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking