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,699
    • Issues 2,699
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 910
    • Merge requests 910
  • 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
  • #1459
Closed
Open
Created Sep 25, 2019 by Bugzilla Migration User@bugzilla-migration

i965/fs: Better heuristics on when to drop from SIMD16 to SIMD8, on register spilling

Submitted by Eero Tamminen

Assigned to Matt Turner @mattst88

Link to original bug (#85505)

Description

Currently SIMD16 versions of shaders are dropped on register spilling.

If same (number of) registers are spilled also by SIMD8 version, it most likely makes sense to keep the SIMD16 version.

Version: git

Blocking

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