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
  • Surface.cpp
Find file
BlameHistoryPermalink
  • Jamie Madill's avatar
    Surface: Don't use a BindingPointer for BindTexImage. · e8cc4a64
    Jamie Madill authored Jul 09, 2018
    The BindingPointer pattern isn't necessary. Every time we delete a
    Texture we call ReleaseTexImage internally. There shouldn't be any time
    that we keep an orphaned Texture is Surface.
    
    This cleans up one place where we were using the ProxyContext.
    
    Bug: angleproject:2714
    Change-Id: I3b0fd2125d02ea7545922ec6da7f487451bed871
    Reviewed-on: https://chromium-review.googlesource.com/1128925
    Commit-Queue: Jamie Madill <jmadill@chromium.org>
    Reviewed-by: 's avatarGeoff Lang <geofflang@chromium.org>
    Reviewed-by: 's avatarFrank Henigman <fjhenigman@chromium.org>
    e8cc4a64
Surface.cpp 13.4 KB
EditWeb IDE
×

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