mirror of https://gitlab.freedesktop.org/mesa/mesa
Is a phi source is an undef, there's no point in copying it or really caring about it at all. We would just end up inserting a mov from an undef to a register. Instead, treat phi sources which point to an undef as if the phi source doesn't exist. This also prevents them from being included in phi webs which should reduce the overall interference seen in the shader. Currently, if two phis share an undef, their phi webs are consdiered to interfere. By ignoring undefs we can get rid of this false interference and reduce the size of phi webs. Reducing the number of things being copied by the parallel copy instructions should also free up the paralle copy algorithm and reduce the over-all churn of movs. Shader-db results on Haswell: total instructions in shared programs: 8156608 -> 8155406 (-0.01%) instructions in affected programs: 164838 -> 163636 (-0.73%) Shader-db results on Skylake: total instructions in shared programs: 18227370 -> 18227359 (<.01%) instructions in affected programs: 519 -> 508 (-2.12%) helped: 6 HURT: 0 Shader-db results on Tigerlake: total instructions in shared programs: 21167987 -> 21168025 (<.01%) instructions in affected programs: 23701 -> 23739 (0.16%) helped: 21 HURT: 27 Reviewed-by: Daniel Schürmann <daniel@schuermann.dev> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16817> |
||
---|---|---|
.github/workflows | ||
.gitlab/issue_templates | ||
.gitlab-ci | ||
android | ||
bin | ||
build-support | ||
docs | ||
include | ||
src | ||
subprojects | ||
.dir-locals.el | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.gitlab-ci.yml | ||
.mailmap | ||
CODEOWNERS | ||
README.rst | ||
VERSION | ||
meson.build | ||
meson_options.txt |
README.rst
`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.