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
  • #639
Closed
Open
Issue created Nov 28, 2014 by Derek Bruening@derekbrueningContributor

Transparency Issue on Handling YMM registers

From [email protected] on December 15, 2011 15:34:42

xref issue #437 (closed) The first execution of AVX instruction in a thread will change the processor state. So if blindly save and restore YMM register using AVX instruction will cause transparency issue.

One solution is to use and conditional check to decide if YMM is need save or not. However, if using thread-shared code cache, how can we tell if a thread has executed any AVX instruction before?

Original issue: http://code.google.com/p/dynamorio/issues/detail?id=639

Assignee
Assign to
Time tracking