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
  • #2577
Closed
Open
Issue created Jul 31, 2017 by Derek Bruening@derekbrueningContributor

tracing tools should not include loads/stores skipped due to x86 conditional execution or synch primitives

Today drmemtrace inside drcachesim predicates its data trace instrumentation for app loads and stores that are predicated on ARM, but it does not do so for x86 for instructions like OP_cmovcc and OP_bs{r,f}. This issue covers addressing that in drmemtrace, as well as in the sample tracing clients.

Other x86 "predicated" loads/stores will be more complex to handle: OP_getsec, OP_xend, OP_vpmaskmov{d,q}, OP_vpmaskmovp{s,d}, OP_{,v}maskmovdqu.

We can ignore OP_fmovcc as it does not touch memory.

Assignee
Assign to
Time tracking