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
  • Tim Van Patten's avatar
    Use Subject/Observer pattern for Programs/Executables in PPOs · 80d7725d
    Tim Van Patten authored Jul 15, 2020
    This CL updates the frontend to use the subject/observer pattern for
    Programs and ProgramExecutables in PPOs.
    
    This allows us to remove the hack that iterated through all PPOs and
    marking them all dirty when a Program is re-linked. Instead, just the
    PPOs the Program is bound to are signalled, and only when the Program
    is in a PPO.
    
    Additionally the necessary PPOs are signalled when an Executable's
    textures are updated, rather than iterating through all PPOs and
    signalling them.
    
    Bug: angleproject:4559
    Test: CQ
    Change-Id: Iaefb88c64c13259e921c8dfe95cf640247d17f85
    Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2300705
    Commit-Queue: Tim Van Patten <timvp@google.com>
    Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org>
    Reviewed-by: 's avatarCharlie Lao <cclao@google.com>
    80d7725d
State.cpp 111 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.