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
  • libANGLE
  • State.cpp
Find file
BlameHistoryPermalink
  • Jamie Madill's avatar
    Don't always sync all dirty object state on update. · ad9f24e1
    Jamie Madill authored Feb 12, 2016
    This leads to a problem where we're synching objects out of order. For
    instance, when we call SetImage, we need to sync the pack state. But
    SetImage can affect the FBO state, so we need to sync the FBO only
    after we've finished with SetImage.
    
    Fix this by using a mask of dirty objects to sync instead of all of
    them, always. This also has the side effect of deferring some syncs
    that don't have to be processed immediately.
    
    BUG=angleproject:1260
    
    Change-Id: I5678d8f967930d11b42a4309d209215be2bae963
    Reviewed-on: https://chromium-review.googlesource.com/327259Reviewed-by: 's avatarCorentin Wallez <cwallez@chromium.org>
    Reviewed-by: 's avatarGeoff Lang <geofflang@chromium.org>
    Commit-Queue: Jamie Madill <jmadill@chromium.org>
    ad9f24e1
State.cpp 53.4 KB
EditWeb IDE
×

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