• Show log

    Commit

  • Hash : d0c03ff4
    Author : Shahbaz Youssefi
    Date : 2021-07-22T14:55:51

    Vulkan: SPIR-V Gen: Fix lvalues passed to in/inout parameters
    
    In GLSL, these values are semantically copied when passed to a function
    as an in or inout parameter.  For example in:
    
        bool f(inout vec4 a, inout vec4 b)
        {
            a = vec4(0);
            return all(equal(a, b));
        }
    
        var = vec4(1);
        bool result = f(var, var);
    
    result is expected to be false.  In SPIR-V, every parameter is
    semantically passed by "reference".
    
    glslang conservatively uses temporaries to pass to functions.  An
    optimization in ANGLE didn't create temporaries for unindexed lvalues,
    which did not take into account the above fact.  This optimization is
    limited to out parameters now.
    
    Bug: angleproject:4889
    Change-Id: Ie1b4b1cecba847ba63d5810d01d0856823b89ddc
    Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/3046103
    Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
    Reviewed-by: Tim Van Patten <timvp@google.com>
    Reviewed-by: Jamie Madill <jmadill@chromium.org>
    Commit-Queue: Shahbaz Youssefi <syoussefi@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 following ContextVk APIs:

    • beginNewRenderPass: Writes out (aka flushes) prior pending commands into a primary command buffer, then starts a new render pass. Returns a secondary command buffer inside a render pass instance.
    • getOutsideRenderPassCommandBuffer: May flush prior command buffers and close the render pass if necessary, in addition to issuing the appropriate barriers. Returns a secondary command buffer outside a render pass instance.
    • getStartedRenderPassCommands: Returns a reference to the currently open render pass’ commands buffer.

    The back-end (mostly) records Image and Buffer barriers through additional CommandBufferAccess APIs, the result of which is passed to getOutsideRenderPassCommandBuffer. Note that the barriers are not actually recorded until getOutsideRenderPassCommandBuffer is called:

    • onBufferTransferRead and onBufferComputeShaderRead accumulate VkBuffer read barriers.
    • onBufferTransferWrite and onBufferComputeShaderWrite accumulate VkBuffer write barriers.
    • onBuffferSelfCopy is a special case for VkBuffer self copies. It behaves the same as write.
    • onImageTransferRead and onImageComputerShadeRead accumulate VkImage read barriers.
    • onImageTransferWrite and onImageComputerShadeWrite accumulate VkImage write barriers.
    • onImageRenderPassRead and onImageRenderPassWrite accumulate VkImage barriers inside a started RenderPass.

    After the back-end records commands to the primary buffer and we flush (e.g. on swap) or when we call ContextVk::finishToSerial, ANGLE submits the primary command buffer to a VkQueue.

    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.
        vk::CommandBufferAccess access;
        access.onBufferTransferWrite(destBuffer);
        access.onBufferTransferRead(srcBuffer);
    
        // Get a pointer to a secondary command buffer for command recording.
        vk::CommandBuffer *commandBuffer;
        ANGLE_TRY(contextVk->getOutsideRenderPassCommandBuffer(access, &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: