Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • C cpython
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • cpython
  • Repository
  • cpython
  • Python
  • peephole.c
Find file BlameHistoryPermalink
  • Gregory P. Smith's avatar
    bpo-35193: Fix an off by one error in the RETURN_VALUE case. (GH-10418) · 49fa4a9f
    Gregory P. Smith authored Nov 08, 2018
    Fix an off by one error in the peephole optimizer when checking for unreachable code beyond a return.
    
    Do a bounds check within find_op so it can return before going past the end as a safety measure.
    
    https://github.com/python/cpython/commit/7db3c488335168993689ddae5914a28e16188447#diff-a33329ae6ae0bb295d742f0caf93c137
    introduced this off by one error while fixing another one nearby.
    
    This bug was shipped in all Python 3.6 and 3.7 releases.
    
    The included unittest won't fail unless you do a clang msan build.
    49fa4a9f
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7