• Show log

    Commit

  • Hash : 585e3555
    Author : Xinyi He
    Date : 2020-05-14T10:49:48

    Vulkan: Remove GL_BGRX8_ANGLEX from configurations
    
    It doesn't need to expose an emulated RGB format any
    longer. Skip ClearTestRGB.DefaultFramebufferRGB test
    if GPUs don't support RGB format back buffer.
    
    Bug: angleproject:4631
    Change-Id: Ifa2d2ed6f863dcb698f7eea3e752a8cd5d5e0ced
    Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2198888
    Reviewed-by: Geoff Lang <geofflang@chromium.org>
    Reviewed-by: Jamie Madill <jmadill@chromium.org>
    Commit-Queue: Geoff Lang <geofflang@chromium.org>
    

  • Properties

  • Git HTTP https://git.kmx.io/kc3-lang/angle.git
    Git SSH git@git.kmx.io:kc3-lang/angle.git
    Public access ? public
    Description

    A conformant OpenGL ES implementation for Windows, Mac, Linux, iOS and Android.

    Homepage

    Github

    Users
    thodg_m kc3_lang_org thodg_w www_kmx_io thodg thodg_l
    Tags

  • README.md

  • ANGLE: Vulkan Back-end

    ANGLE’s Vulkan back-end implementation lives in this folder.

    Vulkan is an explicit graphics API. It has a lot in common with other explicit APIs such as Microsoft’s D3D12 and Apple’s Metal. Compared to APIs like OpenGL or D3D11 explicit APIs can offer a number of significant benefits:

    • Lower API call CPU overhead.
    • A smaller API surface with more direct hardware control.
    • Better support for multi-core programming.
    • Vulkan in particular has open-source tooling and tests.

    Back-end Design

    The RendererVk class represents an EGLDisplay. RendererVk owns shared global resources like the VkDevice, VkQueue, the Vulkan format tables and internal Vulkan shaders. The ContextVk class implements the back-end of a front-end OpenGL Context. ContextVk processes state changes and handles action commands like glDrawArrays and glDrawElements.

    Command recording

    The back-end records commands into command buffers via the the following ContextVk APIs:

    • endRenderPassAndGetCommandBuffer: returns a secondary command buffer outside a RenderPass instance.
    • flushAndBeginRenderPass: returns a secondary command buffer inside a RenderPass instance.
    • flushAndGetPrimaryCommandBuffer: returns the primary command buffer. You should rarely need this API.

    Note: All of these commands may write out (aka flush) prior pending commands into a primary command buffer. When a RenderPass is open endRenderPassAndGetCommandBuffer will flush the pending RenderPass commands. flushAndBeginRenderPass will flush out pending commands outside a RenderPass to a primary buffer. On submit ANGLE submits the primary command buffer to a VkQueue.

    If you need to record inside a RenderPass, use flushAndBeginRenderPass. Otherwise, use endRenderPassAndGetCommandBuffer. You should rarely need to call flushAndGetPrimaryCommandBuffer. It’s there for commands like debug labels, barriers and queries that need to be recorded serially on the primary command buffer.

    The back-end usually records Image and Buffer barriers through additional ContextVk APIs:

    • onBufferTransferRead/onBufferComputeShaderRead and onBufferTransferWrite/onBufferComputeShaderWrite accumulate VkBuffer barriers.
    • onImageRead and onImageWrite accumulate VkImage barriers.
    • onRenderPassImageWrite is a special API for write barriers inside a RenderPass instance.

    After the back-end records commands to the primary buffer we flush (e.g. on swap) or when we call ContextVk::finishToSerial.

    See the code for more details.

    Simple command recording example

    In this example we’ll be recording a buffer copy command:

        # Ensure that ANGLE sets proper read and write barriers for the Buffers.
        ANGLE_TRY(contextVk->onBufferTransferWrite(destBuffer));
        ANGLE_TRY(contextVk->onBufferTransferRead(srcBuffer));
    
        # Get a pointer to a secondary command buffer for command recording. May "flush" the RP.
        vk::CommandBuffer *commandBuffer;
        ANGLE_TRY(contextVk->endRenderPassAndGetCommandBuffer(&commandBuffer));
    
        # Record the copy command into the secondary buffer. We're done!
        commandBuffer->copyBuffer(srcBuffer->getBuffer(), destBuffer->getBuffer(), copyCount, copies);

    Additional Reading

    More implementation details can be found in the doc directory: