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 403
    • Issues 403
    • 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
  • #2014
Closed
Open
Created Dec 29, 2009 by Robert Bernecky@rbeDeveloper

Missing CF code causes AWLFI to produce unresolvable mesh_VxVxV() computation

Bugzilla Link 643
Created on Dec 29, 2009 17:58
Resolution FIXED
Resolved on Dec 30, 2009 22:10
Version svn
OS Linux
Architecture PC

Extended Description

I think this bug arose out of Loch Ness work, but am not completely sure,
not that it matters...
The basic problem is that AWLFI produces an expression of the form:
   _add_VxS_( [0], scalar)
but CF (symbolic_constant_simplification.c) never got support 
written to handle those cases.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking