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
  • #5038
Closed
Open
Issue created Aug 04, 2021 by Derek Bruening@derekbrueningContributor

Instruction cache coherence transparency

If an application on an explicitly-coherent-vs-data-cache architecture like AArch64 dynamically generates code into memory and fails to flush the icache, it will cause potential problems of stale values when that code is executed. However, under DR, there will never be a problem since DR will read the app's code as data and execute copies in its code caches which are correctly synchronized. This is a transparency violation as DR does not reproduce the app's original behavior.

This is likely not high priority and unless there is a simple solution we will probably just live with it. Xref related issues like NX transparency (#329) though that is easily solvable.

Assignee
Assign to
Time tracking