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
  • FramebufferMultiviewTest.cpp
Find file
BlameHistoryPermalink
  • Martin Radev's avatar
    GL: Optimize multi-view layered Clear* commands · 61e710b6
    Martin Radev authored Sep 05, 2017
    Until this patch multi-view layered framebuffers used to be cleared by
    attaching a single layer of each attachment to a framebuffer and calling
    the Clear* command for that internal framebuffer.
    According to the GL 4.1+ specifications, Clear* commands clear all of
    the layers of an attached 2D texture array. If all of the layers are
    active for a multi-view layered framebuffer, then we can directly call
    the corresponding Clear* command instead of iterating over each layer
    and clearing it.
    
    BUG=angleproject:2062
    TEST=angle_end2end_tests
    
    Change-Id: Ie4dfd9fff47715b502f358272bfc47c0373c4e91
    Reviewed-on: https://chromium-review.googlesource.com/649209
    Commit-Queue: Martin Radev <mradev@nvidia.com>
    Reviewed-by: 's avatarOlli Etuaho <oetuaho@nvidia.com>
    61e710b6
FramebufferMultiviewTest.cpp 49.6 KB
EditWeb IDE
×

Replace FramebufferMultiviewTest.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.