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 394
    • Issues 394
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sac-group
  • sac2csac2c
  • Issues
  • #2050
Closed
Open
Created May 18, 2017 by Robert Bernecky@rbeDeveloper

SAACFchaseMinMax() gives wrong result for AVIS_MAX when arg_node is AKV

Bugzilla Link 1193
Created on May 18, 2017 22:07
Resolution FIXED
Resolved on May 18, 2017 23:13
Version svn
OS Linux
Architecture PC

Extended Description

This is a long-standing bug in CF that apparently has never
hit anyone who noticed it.
Basically, any CF calls that care about AVIS_MAX will give the
wrong answer when the argument node is AKV.
Instead of returning AVIS_MAX( arg_node), it returns a constant
built from arg_node. It SHOULD return 1+arg_node, because AVIS_MAX
is normalized, just as GENERATOR_BOUND2 is normalized.
sac2c -V
sac2c 1.2-beta-BlackForest-507-g4f66f-dirty
build-type: DEBUG
built-by: "sac" at 2017-05-18T16:24:11
I have a fix for it in bob-sac2cpogo4.
Bob
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking