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 17
    • Merge requests 17
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sac-group
  • sac2csac2c
  • Issues
  • #1228
Closed
Open
Created Sep 17, 2010 by Sven-Bodo Scholz@sbsOwner

how to deal with array constructors and selections

Bugzilla Link 747
Created on Sep 17, 2010 07:43
Version svn
OS All
Architecture PC

Extended Description

This bug relates to bug 746 but is of a more specific nature.
The overall question is:
- when to lift an array constructor out of loops/conditionals
- when to push it in
and
- how to steer that behaviour advantageously
Naively, one might argue that arrays should always be lifted as far as possible.
Unfortunately, that does not hold for index vectors that are used in selections or
modarray operations. There, it is often (not always!) advantageous to propagate them
down as they may avoid a vect2offset.
A thorough analysis of the situation is asked for.....
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking