mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-05-14 10:08:05 +02:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
9ef47c8921
Previously, we handled vectors by giving each SSAValue a number of components which we assume matches in all uses. To deal with swizzles and component selection, we had OpVec and OpSplit instructions to convert vectors to/from scalars as-needed. This is fine as an SSA representation but it leads to a lot of redundant values when it comes time for assigning registers. There are strategies for dealing with this such as ensuring that splits always kill the whole vector and then re-combining into a new vector for later uses. It's possible by doing this to ensure that each component only ever exists exactly once at the cost of a LOT of vec/split instructions. Another possible solution is to naievely emit vec/split but teach liveness analysis and RA bout the duplicated values. Instead of RA working on individual SSA values, it can work on equivalence classes of components. This takes a different (and currently novel to Mesa) approach of making each SSAValue a single component but having an SSARef type which can reference up to 4 SSAValues as a vector. Register allocation then works on individual components and only ensures that the components of a vector are contiguous when it's used as a vector. This isn't very different from how it worked before. If anything, it's a bit more straightforward now because the component/vector split uses the same types as the rest of the IR and the SSAComp is gone. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/24998> |
||
|---|---|---|
| .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.