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
  • Texture.cpp
Find file
BlameHistoryPermalink
  • Geoff Lang's avatar
    Textures that have bound surfaces are always renderable. · ab95a449
    Geoff Lang authored Jul 20, 2020
    Chrome still tends to use ES2 contexts for most rasterization. This is a
    problem when trying to use FP16 IOSurfaces for rendering HDR because
    GL_RGBA16F is not renderable in ES2. Since a surface is always
    renderable, allow rendering to any textures with a bound surface.
    
    Update the tests to verify that ES3 formats can be used with ES2
    contexts.
    
    Add tests for RGBA16F IOSurfaces.
    
    BUG: chromium:1103112
    Change-Id: I9e8c082fc97a0e072289b097e71fc944988d4872
    Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2307454Reviewed-by: 's avatarJonah Ryan-Davis <jonahr@google.com>
    Reviewed-by: 's avatarGeoff Lang <geofflang@chromium.org>
    Commit-Queue: Geoff Lang <geofflang@chromium.org>
    ab95a449
Texture.cpp 67.1 KB
EditWeb IDE
×

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