Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D dynamorio
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,467
    • Issues 1,467
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 44
    • Merge requests 44
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • DynamoRIO
  • dynamorio
  • Issues
  • #5352
Closed
Open
Issue created Feb 13, 2022 by Derek Bruening@derekbrueningContributor

Large performance regression on Windows due to indirect branch link breakage

Commit 638fb106 PR #4886 accidentally broke Windows indirect branch table updating. This was discovered by a user: https://groups.google.com/d/msgid/dynamorio-users/CAO1ikSY7Uvgcw_b98H1ifkvFGhDUSYzZe9uatrYNPcETMYix-Q%40mail.gmail.com?utm_medium=email&utm_source=footer

This is pretty bad: this will cause massive slowdowns on some programs. We need to put out an updated 9.1 release.

Performance regression tests are not always simple to set up. Maybe we can more easily have a test that checks the exit stats.

Assignee
Assign to
Time tracking