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 400
    • Issues 400
    • 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
  • #1678
Closed
Open
Created Aug 26, 2006 by Robert Bernecky@rbeDeveloper

GCC-generated code slower than Solaris-generated code ive vs ive1

Bugzilla Link 288
Created on Aug 26, 2006 22:54
Resolution DUPLICATE
Resolved on Oct 03, 2006 21:19
Version svn
OS Linux
Architecture PC

Extended Description

I thought we had a bug report on this, but I don't see it, so here's another,
with some more info:
sac2c -O3 buildv.sac
runs about 15% slower under GCC than
sac2c -O3 -ive 1 buildv.sac
Under Solaris, they're about the same, or perhaps the ive1 code is a tad slower.
With histop.sac, where ive 1 is much slower than ive, 
the relative speed of ive1/ive is about 4.2 on asterix running SUN C, \
and about 3.5 on my AMD Linux box w/gcc.
I don't think we can do much about this, but it's noteworthy.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking