This means the pass has to walk all the instructions but it was doing that in a bunch of cases anyway when it didn't have a HALT_TARGET. However, removing HALT_TARGET frees up the scheduler a bit because HALT_TARGET is considered a scheduling barrier. The shader-db results are kind-of a wash but we're about to add HALT_TARGET unconditionally so we want to be able to get rid of it. Shader-db results on Ice Lake: total instructions in shared programs: 19935623 -> 19935623 (0.00%) instructions in affected programs: 0 -> 0 helped: 0 HURT: 0 total cycles in shared programs: 976758472 -> 976766135 (<.01%) cycles in affected programs: 11097707 -> 11105370 (0.07%) helped: 1750 HURT: 875 helped stats (abs) min: 1 max: 866 x̄: 26.39 x̃: 4 helped stats (rel) min: <.01% max: 39.24% x̄: 1.25% x̃: 0.46% HURT stats (abs) min: 1 max: 1678 x̄: 61.54 x̃: 10 HURT stats (rel) min: <.01% max: 65.69% x̄: 1.86% x̃: 0.42% 95% mean confidence interval for cycles value: -2.48 8.32 95% mean confidence interval for cycles %-change: -0.40% -0.03% Inconclusive result (value mean confidence interval includes 0). LOST: 62 GAINED: 46 All of the lost/gained programs are SIMD32 fragment shaders. Reviewed-by: Francisco Jerez <currojerez@riseup.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5071> |
||
---|---|---|
.appveyor | ||
.gitlab/issue_templates | ||
.gitlab-ci | ||
bin | ||
build-support | ||
docs | ||
doxygen | ||
include | ||
scons | ||
src | ||
subprojects | ||
.dir-locals.el | ||
.editorconfig | ||
.gitignore | ||
.gitlab-ci.yml | ||
.mailmap | ||
.travis.yml | ||
Android.common.mk | ||
Android.mk | ||
CleanSpec.mk | ||
README.rst | ||
REVIEWERS | ||
SConstruct | ||
VERSION | ||
appveyor.yml | ||
common.py | ||
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 `Freenode's #dri-devel <irc://chat.freenode.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.