mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-01-02 00:50:07 +01:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
92550b106c
The scissor planes we were setting up did not actually correspond to scissor with widths / heights being a multiple of full pixels, rather they had an excess width / height of (nearly) half a pixel (at the x0 and y0 edges). (Note it's not an actual scissor as in graphics APIs terms, it's the intersection of fb/viewport/scissor.) Without multisampling that was still fine (since we always test at pixel center) however vk cts complained (for some reason only when using 8 samples (not announced by lavapipe yet) - no idea why it doesn't fail when using 4 samples), in tests such as dEQP-VK.renderpass2.depth_stencil_resolve.image_2d_17_1.samples_8.s8_uint.depth_zero_stencil_zero_testing_stencil_samplemask, which uses scissor and noted that the result for some pixels which are outside the rendering area don't contain the clear color. And actually a llvmpipe test was failing as well. There is in fact no need for separate adjustments for msaa at all, as long as we ensure that x0, y0, x1, y1 all are exactly on their respective plane edges (inclusive for x0/y0, exclusive for x1/y1). So the logic is mostly reverted to what it was before this was adjusted for msaa (albeit the original code then had an excess adjustment of nearly a full pixel at the x0 and y0 edges which is probably why it didn't work for msaa). Fixes a couple cases of clip-and-scissor-blit tests in llvmpipe and various other drivers hitting this indirectly. Interestingly though not quite all cases are fixed and even more odd is that not exactly the same cases are fixed for all drivers, so maybe there's more to it (need to respect bottom_edge_rule or something similar?) Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/37181> |
||
|---|---|---|
| .ci-farms | ||
| .ci-farms-disabled | ||
| .github/workflows | ||
| .gitlab | ||
| .gitlab-ci | ||
| .marge/hooks | ||
| android | ||
| bin | ||
| build-support | ||
| docs | ||
| include | ||
| licenses | ||
| src | ||
| subprojects | ||
| .clang-format | ||
| .clang-format-ignore | ||
| .clang-format-include | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .graphqlrc.yml | ||
| .mailmap | ||
| .mr-label-maker.yml | ||
| .shellcheckrc | ||
| CODEOWNERS | ||
| meson.build | ||
| meson.options | ||
| README.rst | ||
| rustfmt.toml | ||
| VERSION | ||
`Mesa <https://mesa3d.org>`_ - The 3D Graphics Library ====================================================== Source ------ This repository lives at https://gitlab.freedesktop.org/mesa/mesa. Other repositories are likely forks, and code found there is not supported. Build & install --------------- You can find more information in our documentation (`docs/install.rst <https://docs.mesa3d.org/install.html>`_), but the recommended way is to use Meson (`docs/meson.rst <https://docs.mesa3d.org/meson.html>`_): .. code-block:: sh $ meson setup build $ ninja -C build/ $ sudo ninja -C build/ install Support ------- Many Mesa devs hang on IRC; if you're not sure which channel is appropriate, you should ask your question on `OFTC's #dri-devel <irc://irc.oftc.net/dri-devel>`_, someone will redirect you if necessary. Remember that not everyone is in the same timezone as you, so it might take a while before someone qualified sees your question. To figure out who you're talking to, or which nick to ping for your question, check out `Who's Who on IRC <https://dri.freedesktop.org/wiki/WhosWho/>`_. The next best option is to ask your question in an email to the mailing lists: `mesa-dev\@lists.freedesktop.org <https://lists.freedesktop.org/mailman/listinfo/mesa-dev>`_ Bug reports ----------- If you think something isn't working properly, please file a bug report (`docs/bugs.rst <https://docs.mesa3d.org/bugs.html>`_). Contributing ------------ Contributions are welcome, and step-by-step instructions can be found in our documentation (`docs/submittingpatches.rst <https://docs.mesa3d.org/submittingpatches.html>`_). Note that Mesa uses gitlab for patches submission, review and discussions.