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
  • Framebuffer.cpp
Find file
BlameHistoryPermalink
  • Tim Van Patten's avatar
    Vulkan: Implement framebuffers without attachments · 626a7280
    Tim Van Patten authored Jul 08, 2019
    It is possible to render to a framebuffer object that has no
    attachments.   However, the rasterization of primitives is always
    based on the area and characteristics of the bound framebuffer.
    These characteristics (size, number of samples, etc.) would normally be
    defined by the attached images. If no images are attached, these
    characteristics are defined by their default values.
    
    Bug: angleproject:3579
    Test: dEQP-GLES31.functional.fbo.*no_attachments*
    Test: dEQP-GLES31.functional.state_query.framebuffer_default.*
    Change-Id: I9580b924ac810db573cd8df96273fbb01bbb1f73
    Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1690688Reviewed-by: 's avatarTim Van Patten <timvp@google.com>
    Reviewed-by: 's avatarCourtney Goeltzenleuchter <courtneygo@google.com>
    Commit-Queue: Tim Van Patten <timvp@google.com>
    626a7280
Framebuffer.cpp 77.9 KB
EditWeb IDE
×

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