Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • M mu-impl-fast
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 40
    • Issues 40
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

GitLab will continue to be upgraded on 3 Feb 2023 from 2.00 pm (AEDT) to 3.00 pm (AEDT). During the update, GitLab and Mattermost services will not be available. If you have any concerns with this, please talk to us at N110 (b) CSIT building.

  • mu
  • mu-impl-fast
  • Merge requests
  • !27

Merged
Created Aug 31, 2017 by Yi Lin@u4776528Owner

Issue82 inf loop in peephole

  • Overview 0
  • Commits 4
  • Changes 6

Our peephole optimisation will remove jump-to-jump cases.

However, for cases such as

L1:
  jmp L2
..
L2:
  jmp L3
..
L3:
  jmp L1

the peephole optimiser will get into an infinite loop as we cannot find the final destination to jump. We need to be able to detect this infinite loop so the compiler won't get into an infinite loop. We do not apply optimisations (it is a busy infinite loop that does nothing, which is meaningless anyway).

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: issue82-inf-loop-in-peephole