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

Closed
Open
Created Oct 25, 2006 by Sven-Bodo Scholz@sbsOwner

wlsimp does not handle MOP-WLs

Bugzilla Link 314
Created on Oct 25, 2006 15:08
Resolution FIXED
Resolved on May 31, 2007 17:01
Version 1.00beta
OS SunOS
Architecture PC
Attachments foldfix.sac

Extended Description

this leads to an error UTBaseRep.sac (APEX).
There, a break operator is discarded along with a fold operator but the lhs is
NOT adjusted accordingly.
I think we should add full support for MOP-WLs even though, strictly speaking,
that seems not to be required right now. However, since we need to traverse
through a potential chain of operators anyways it should be rather simple to
make wlsimp generally applicable to MOP-WLs.
In case of empty partitions, we could simply create one (or none in case of
break) assignment for each operator and then replace the entire MOP-WL by this
new assignment chain.
(rev15061)
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