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
  • #1673

Closed
Open
Created Jul 23, 2006 by Robert Bernecky@rbeDeveloper

excessive inlining kills the compiler

Bugzilla Link 243
Created on Jul 23, 2006 04:20
Resolution LATER
Resolved on Oct 24, 2006 14:51
Version 1.00beta
OS Linux
Architecture PC
Attachments UTDScalarB.sac, logd.slow.sac

Extended Description

The attached short unit test runs for about 7 decades on my machine, then decides to print garbage on the screen until it fills the hard drive. I think this is wrong. Both parts of it.

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