Alejandro Piñeiro
f76dad8f89
So far, we were doing the compilation to qpu when the pipeline was created (as part of vkCreateGraphicsPipeline). But this would not be correct when some specific descriptors are involved, like textures. For that case some nir lowerings depend on the texture format, and that info is not available until the specific descriptors are bound to the command buffer. In the same way, the same command buffer with a given pipeline could get their descriptor bound again. So it would be needed to support compilation variants of the same shader. So finally, the v3d_key would work as keys, as the variants would be tracked with a hash table. This commit introduces the new structures for that. What we were building as the final qpu shader would become the initial default variant for the pipeline. We are also saving the keys used at that point, to avoid needing to fully regenerate them when a new variant is created. Not just for performance, but also to avoid needing to track the graphics pipeline create info structure. The code to handle updating the current variant would be done on following commits. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6766>
`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 `Freenode's #dri-devel <irc://chat.freenode.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.