mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-03-06 14:20:39 +01:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
ce13aa4ee7
The last 3 instructions can't use specific registers so flag all the nodes for temps used in the last program instructions and try to avoid assigning any of these. This may help us avoid injecting nops for the last thread switch instruction. Because regisster allocation needs to happen before QPU scheduling and instruction merging we can't tell exactly what the last 3 instructions will be, so we do this for a few more instructions than just 3. We only do this for fragment shaders because other shader stages always end with VPM store instructions that take an small immediate and therefore will never allow us to merge the final thread switch earlier, so limiting allocation for these shaders will never improve anything and might instead be detrimental. total instructions in shared programs: 11471389 -> 11464335 (-0.06%) instructions in affected programs: 582908 -> 575854 (-1.21%) helped: 4669 HURT: 578 Instructions are helped. total max-temps in shared programs: 2230497 -> 2230150 (-0.02%) max-temps in affected programs: 5662 -> 5315 (-6.13%) helped: 344 HURT: 44 Max-temps are helped. total sfu-stalls in shared programs: 18068 -> 18077 (0.05%) sfu-stalls in affected programs: 264 -> 273 (3.41%) helped: 37 HURT: 48 Inconclusive result (value mean confidence interval includes 0). total inst-and-stalls in shared programs: 11489457 -> 11482412 (-0.06%) inst-and-stalls in affected programs: 585180 -> 578135 (-1.20%) helped: 4659 HURT: 588 Inst-and-stalls are helped. total nops in shared programs: 301738 -> 298140 (-1.19%) nops in affected programs: 14680 -> 11082 (-24.51%) helped: 3252 HURT: 108 Nops are helped. Reviewed-by: Alejandro Piñeiro <apinheiro@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450> |
||
|---|---|---|
| .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.