Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • B-ASIC - Better ASIC Toolbox B-ASIC - Better ASIC Toolbox
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 64
    • Issues 64
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Computer EngineeringComputer Engineering
  • B-ASIC - Better ASIC ToolboxB-ASIC - Better ASIC Toolbox
  • Issues
  • #95
Closed
Open
Issue created May 29, 2020 by Oscar Gustafsson@oscgu95🚴Owner

Handle delays differently in precedence graph generation

Description of issue:

Right now, the predence graph is drawn in a slightly strange way when there are loops. It should improve if the delay elements are duplicated so that the signal comes from one node at the left (without any inputs to the delay element) and goes to a different node (with the same name) when it is computed.

Assignee
Assign to
Time tracking