mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-05-07 07:08:04 +02:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
cc7ce6c01f
This is safe to do in all circumstances due to the age of the hardware. (we don't have UBOs, just constant registers with automatic OOB checks) R500 hardware doesn't have standard adress register in fragment shaders and while we have the loop register which we in theory can use for indirect access, this is currently not possible to wire through NIR. So anytime there is an indirect uniform array access in a loop, we end with a if ladder with size depending on the size of the uniform array. The two worst behaving apps here are glamor and some GTK shaders, both of which are sometimes ending over the 512 instructions limit. Flattening the if ladders helps a LOT, so we can get into the instruction limit in most cases (all glamor shaders are OK now). So just enable the flattening by setting all load_ubo_vec4 with ACCESS_CAN_SPECULATE. Shader-db RV530: total instructions in shared programs: 128762 -> 128440 (-0.25%) instructions in affected programs: 540 -> 218 (-59.63%) helped: 3 HURT: 0 total temps in shared programs: 17543 -> 17550 (0.04%) temps in affected programs: 11 -> 18 (63.64%) helped: 0 HURT: 3 total cycles in shared programs: 196984 -> 196657 (-0.17%) cycles in affected programs: 592 -> 265 (-55.24%) helped: 3 HURT: 0 LOST: 0 GAINED: 7 No changes for R300/R400 because there we don't have control flow anyway. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/6366 Reviewed-by: Alyssa Rosenzweig <alyssa@rosenzweig.io> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26877> |
||
|---|---|---|
| .ci-farms | ||
| .ci-farms-disabled | ||
| .github/workflows | ||
| .gitlab | ||
| .gitlab-ci | ||
| android | ||
| bin | ||
| build-support | ||
| docs | ||
| include | ||
| 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 | ||
| CODEOWNERS | ||
| meson.build | ||
| meson_options.txt | ||
| README.rst | ||
| 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://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.