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,701
    • Issues 2,701
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 904
    • Merge requests 904
  • 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
  • #36
Closed
Open
Created Aug 21, 2019 by Kristian H. Kristensen@krhDeveloper

Use out encoding for float immediates

We know the encoding for float immediates, and this is supported now in ir3 asm parser and disasm. We still need to teach ir3_cp() pass to utilize them.

Original description:


There are a number of float immediates built into the instruction set. For example:

	0000[40100005x_28024003x] add.f r1.y, (neg)r0.w, 2

is actually r1.y = 1.0f - r0.w, that is the literal 2 encodes constant 1.0f. We should figure out what all the values are and use this encoding when possible instead of constant registers.

Edited Jan 16, 2021 by Rob Clark
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking