mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-06-13 13:48:20 +02:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
1ce2d57a31
Previously we had special ops doing data model breaking things on GPRs. But there's no real reason for that, we can calculate lane IDs as UGPR vectors within the Jay data model just fine. Adjust jay_ir/jay_validate to define packed 16-bit UGPR vectors, giving them the natural semantics, then use that to calculate lane IDs, peeling back all the hacks we added along the way. This also unfortunately pessimizes inverse_ballot() but only in a corner case that could be revisited later. Stats are net positive. In addition to the code clean up, this has 3 other benefits: * Now that we can rematerialize the lane ID code anywhere we want, we could theoretically reduce register pressure in some scenarios. Stats show this doesn't help in the current implementation, though. * Now that we can calculate lane IDs in control flow, the issues with divergent function calls all go away. (Well, the lane ID issue. There are other issues.) * Now that we use UGPRs for this, we don't need a stride=16 GRF in shaders that don't actually use 16-bit math, meaning less shuffling from bad partitions. That's reflected in the positive stats here. SIMD16: Totals from 1643 (62.07% of 2647) affected shaders: Instrs: 2227750 -> 2221032 (-0.30%); split: -0.44%, +0.14% CodeSize: 33138416 -> 33034224 (-0.31%); split: -0.52%, +0.20% SIMD32: Totals from 1643 (62.07% of 2647) affected shaders: Instrs: 2864583 -> 2806217 (-2.04%); split: -2.22%, +0.19% CodeSize: 43088064 -> 42171504 (-2.13%); split: -2.29%, +0.17% Signed-off-by: Alyssa Rosenzweig <alyssa.rosenzweig@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/41872> |
||
|---|---|---|
| .ci-farms | ||
| .ci-farms-disabled | ||
| .github/workflows | ||
| .gitlab | ||
| .gitlab-ci | ||
| .marge/hooks | ||
| android | ||
| bin | ||
| build-support | ||
| docs | ||
| include | ||
| licenses | ||
| 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 | ||
| .mr-label-maker.yml | ||
| .shellcheckrc | ||
| clippy.toml | ||
| CODEOWNERS | ||
| meson.build | ||
| meson.options | ||
| README.rst | ||
| rustfmt.toml | ||
| 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://docs.mesa3d.org/install.html>`_), but the recommended way is to use Meson (`docs/meson.rst <https://docs.mesa3d.org/meson.html>`_): .. code-block:: sh $ meson setup build $ ninja -C build/ $ sudo ninja -C build/ 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://docs.mesa3d.org/bugs.html>`_). Contributing ------------ Contributions are welcome, and step-by-step instructions can be found in our documentation (`docs/submittingpatches.rst <https://docs.mesa3d.org/submittingpatches.html>`_). Note that Mesa uses gitlab for patches submission, review and discussions.