Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
A
angle
  • Project
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Chen Yisong
  • angle
  • Repository

Switch branch/tag
  • angle
  • src
  • tests
  • gl_tests
  • ShaderStorageBufferTest.cpp
Find file
BlameHistoryPermalink
  • Kimmo Kinnunen's avatar
    Fix ShaderStorageBufferTest31.LoadAndStoreBooleanVarAndArray to be more correct · 7270a6d5
    Kimmo Kinnunen authored Aug 06, 2019
    The test contained bugs which made it fail on multiple platforms.
    After mapping SSBO, access the data with GLuint instead of GLboolean.
    The elements in the SSBO are 4 machine units, even though the SSB
    talks about bools.
    
    A bvec2 declared after bool in the SSB has alignment requirements.
    
    The test asserts that a shader written result is zero. In this case
    it needs to initialize the result buffer to non-zero in order to
    prove that the shader put the zero there.
    
    Bug: angleproject:3749, angleproject:1951
    Change-Id: Iad8301be7f9e9df6bbed6b390d9c415d4e437c1a
    Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1738909
    Commit-Queue: Kimmo Kinnunen FI <kkinnunen@nvidia.com>
    Reviewed-by: 's avatarYuly Novikov <ynovikov@chromium.org>
    7270a6d5
ShaderStorageBufferTest.cpp 78.4 KB
EditWeb IDE
×

Replace ShaderStorageBufferTest.cpp

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.