KhronosGroup / KhronosGroup/Vulkan-Docs

Not clear if no fragment shader triggers Early Fragment Tests

Open
#1,344 0 comments 0 reactions 1 assignee Claimed by @TomOlson View on GitHub
Resolving Inside Khronos
Dominant language
JavaScript
Stars
3.3k
Forks
549
Avg merge
5d 5h
Merged PRs (30d)
2

Description

It is not clear if no fragment shader triggers Early Fragment Tests. It feels like it should, but the spec says:

> An explicit control is provided to allow fragment shaders to enable early fragment tests. If the fragment shader specifies the `EarlyFragmentTests OpExecutionMode`, additional _per-fragment tests_ are performed prior to fragment shader execution.

And if there is no fragment shader there is no `OpExecutionMode`.

Probably there is no difference, except when using `VkPipelineStageFlagBits` and `VK_PIPELINE_STAGE_EARLY_FRAGMENT_TESTS_BIT` vs `VK_PIPELINE_STAGE_LATE_FRAGMENT_TESTS_BIT` for synchronizing something.

Also the sentence is bit inconsistent. It says "**additional** per-fragment tests". But instead Fragment Operations chapter specifies early tests as just defering fragment shader, and there is nothing "additional".

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.