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
  • #4070
Closed
Open
Issue created Jan 31, 2020 by Derek Bruening@derekbrueningContributor

Add drwrap call site wrapping feature

drwrap by default handles all the complexities of tailcalls, longjmp, etc. by using a callee and return address wrapping approach. This incurs extra overhead, mostly from flushing when a return address is discovered after it has already been executed (or simultaneously executed in another thread). There are some use cases where missing corner cases of calling conventions is not important and we would prefer to have better performance: we know we're targeting functions that never do anything unusual. This is a feature request to iadd a drwrap mode for this case: wrapping based solely on the call site and ignoring the callee and what actually happens when it returns.

Assignee
Assign to
Time tracking