9d75795087ce1233e92df2582846ec6f6116d423
Move most of the DB_SHADER_CONTROL fields from the pipeline to the pixel shader for preparation for shader objects. Also, the GFX11 export conflict bug workaround doesn't need to be enabled for non-1x sample counts or if blending is not enabled, so make the application of DB_SHADER_CONTROL consider the current sample count and blending state even if they're dynamic. Having access to the exact sample count in DB_SHADER_CONTROL setup is also necessary for good performance in SampleInterlock execution modes of fragment shader interlock, for configuration of POPS_OVERLAP_NUM_SAMPLES (GFX9-10.3) or OVERRIDE_INTRINSIC_RATE (GFX11), as PixelInterlock is massively slower with multisampling due to overlap between adjacent polygons sharing covered pixels among the common edge. The name of the dynamic state controlling DB_SHADER_CONTROL is now unambiguous - previously line rasterization mode had effect on attachment feedback loop state emission. Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Signed-off-by: Vitaliy Triang3l Kuzmin <triang3l@yandex.ru> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/23474>
`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://mesa3d.org/install.html>`_), but the recommended way is to use Meson (`docs/meson.rst <https://mesa3d.org/meson.html>`_): .. code-block:: sh $ mkdir build $ cd build $ meson .. $ sudo ninja 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://mesa3d.org/bugs.html>`_). Contributing ------------ Contributions are welcome, and step-by-step instructions can be found in our documentation (`docs/submittingpatches.rst <https://mesa3d.org/submittingpatches.html>`_). Note that Mesa uses gitlab for patches submission, review and discussions.
Description
Languages
C
75.5%
C++
17.2%
Python
2.7%
Rust
1.8%
Assembly
1.5%
Other
1%