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
  • #1217
Closed
Open
Created Aug 21, 2011 by Clemens Grelck@cgDeveloper

LIR ineffective in opt cycles

Bugzilla Link 860
Created on Aug 21, 2011 09:44
Version svn
OS Linux
Architecture PC
Attachments lir.sac

Extended Description

When compiling the unit test testsuite/optimizations/al/lir.sac
AL identifies the loop invariant variables in the first opt cycle
and rearranges the multi-operand expression accordingly. 
However, none of the LIRs in the two opt cycles actually removed the
loop invariant expression and, hence, it is identified again and again
by AL. Only the final off-cycle application of LIR does its job. In a
less trivial example that, of course, would be too late for other
optimisations to benefit.
Funny enough, despite the fact that lir and wlir go together (as they
should not) the similar wlir.sac unit test works fine.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking