Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • mesa mesa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2,880
    • Issues 2,880
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 905
    • Merge requests 905
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mesa
  • mesamesa
  • Issues
  • #5215

Closed
Open
Created Aug 10, 2021 by Alyssa Rosenzweig@alyssa💜Developer

Rename nir_op_fpow to nir_op_fpowr

This makes what we do in vtn consistent with the naming in SPIR-V and the IEEE 754 spec. When looking for special case behaviour of nir_op_fpow, you need to look at the powr rules in the IEEE spec, not at the pow rules. Let's rename NIR to make it obvious what's happening.

Actual pow isn't supported in NIR at all, and gets lowered via libclc.

Cc @jekstrand

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking