Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • mesa mesa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 3.2k
    • Issues 3.2k
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1k
    • Merge requests 1k
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • MesaMesa
  • mesamesa
  • Issues
  • #1514
Closed
Open
Issue created Sep 25, 2019 by Bugzilla Migration User@bugzilla-migration

Blits from GL_TEXTURE_2D_MULTISAMPLE GL_INT or GL_UINT surfaces are not handled correctly

Submitted by Ian Romanick

Assigned to Ian Romanick

Link to original bug (#94142)

Description

Created attachment 121740 Assertion that also shows the problem.

For reference, use 'git blame src/mesa/drivers/common/meta_blit.c 9e30d66b'. Assume the blit is an MSAA-MSAA blit from a GL_TEXTURE_2D_MULTISAMPLE surface with base type GL_INT.

Line 294 sets dst_is_msaa true.

Line 313 sets shader_index to BLIT_MSAA_SHADER_2D_MULTISAMPLE_COPY.

Line 339 increments shader_index by 5, and it is now BLIT_1X_MSAA_SHADER_2D_MULTISAMPLE_ARRAY_RESOLVE.

Similar problems exist for GL_TEXTURE_2D_MULTISAMPLE_ARRAY blits. You really only notice this problem is a blit of one kind is followed by a blit of a kind that conflicts.

We should have piglit tests for this.

I noticed this because, while I was making other changes, I added an assertion like the one in the attachment. Surely dst_is_msaa must be false when doing a resolve blit. Alas.

Attachment 121740, "Assertion that also shows the problem.":
dst-not-msaa-for-resolve.patch

Version: git

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