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
  • #3874
Closed
Open
Issue created Oct 06, 2019 by John F.X. Galea@johnfxgaleaContributor

Support reg_is_vector_simd()

MMX registers are completely separate registers in relation to SSE's XMM registers. The latter were expanded to larger sizes, namely YMM and ZMM.

Often, we want to test whether a register is a SIMD extension register but not an MMX register. This issue relates to providing this functionality, i.e., it checks whether the register is either an XMM, YMM or ZMM.

Looking at the API, I have a hunch that the now deprecated function reg_is_xmm() was intended to provide this requested functionality. In fact, the deprecated function currently checks whether a register is either an XMM or YMM. The name of the function just confuses matters.

Assignee
Assign to
Time tracking