mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-04-18 23:20:36 +02:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
5716700bbf
We have much better regalloc in the backend, and additionally having a close to ssa form means some optimizations can be more effective. RV370: total instructions in shared programs: 82500 -> 81645 (-1.04%) instructions in affected programs: 32147 -> 31292 (-2.66%) helped: 396 HURT: 1 total temps in shared programs: 12355 -> 12465 (0.89%) temps in affected programs: 368 -> 478 (29.89%) helped: 5 HURT: 96 GAINED: shaders/trine/vp-237.shader_test VS GAINED: shaders/trine/vp-79.shader_test VS RV530: total instructions in shared programs: 130706 -> 129684 (-0.78%) instructions in affected programs: 40902 -> 39880 (-2.50%) helped: 428 HURT: 1 total temps in shared programs: 16811 -> 16920 (0.65%) temps in affected programs: 421 -> 530 (25.89%) helped: 7 HURT: 89 The instruction decrease is from the channel merging pass which can be much more agressive when we have ssa-like form. The temp regressions are cases where we merge something like 3: MAD output[1].xy, const[8].xy__, input[1].ww__, temp[0].xy__; .... 12: MOV output[1].zw, none.__00; We always merge the first instruction into the second one, which means the liverange for temp[0] will be unnecessarily extended here. This can be fixed with the following draft MR https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19790 however if we ever get a VS pair scheduling support this will be solved as well as a consequence, so let it be for now. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7693 Reviewed-by: Filip Gawin <filip.gawin@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/23927> |
||
|---|---|---|
| .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 | ||
| .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.