725fc0ec03
RADV currently has two paths for PS epilogs: - the first one is mostly used by GPL to compile fragment shader epilogs as part of the graphics pipeline. It's supposed to be optimal because fragment shader epilogs are compiled in the pipeline and eventually cached. - the second one (the "on-demand" path) is required when some dynamic states are used because otherwise it's just impossible to compile the fragment shader. These epilogs are compiled during cmdbuf recording when all needed info are known, they are also cached in memory. This is the main path for Zink. Having two different paths isn't ideal for maintenance but there is another problem. On RDNA3, alpha to coverage needs to be exported as part of MRTZ when either depth/stencil/samplemask are exported. The problem being that with GPL, the PSO multisample state can be NULL when the frag shader lib is created, which means that we can't know if atc needs to be exported or not, even if it's static. The solution seems to to always use on-demand fragment shader epilogs for GPL on RDNA3. So far, I think that switching to on-demand PS epilogs unconditionally for GPL shouldn't hurt performance and that will simplify a lot of things. Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26398>
`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.