Jesse Natalie
56589cb02c
Normally, we insert barriers automatically based on bind points. If a resource is bound as both a shader image/SSBO (UAV) and other read-only bind points, we'll choose the UAV state. This behavior is modified by the memory barrier API - if the memory barrier indicates that a read is desired, previously, we would've just not put any barriers to UAV states. Now, we just use that state to disambiguate between read states vs write states for a resource that's bound as both. This turns out to be problematic in some circumstances, e.g.: * PBO download, which does a memory barrier afterwards, since it uses shader images to write, and those might be accessed immediately as a texture afterwards. * A user-issued draw that writes to a SSBO. This should indicate in the state tracker that the SSBO is in the UAV state. * Some other op, like a copy, that writes to the SSBO. Before, the "pending memory barrier" state would cause the user draw to not be put in the UAV state, which means that the copy wouldn't issue a barrier *out* of the UAV state, resulting in the copy being unsynchronized. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26104>
`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.