764760314d
Currently lima uses generic TXP lowering that results in downgrading coords precision to FP16 since we have to do some calculations with coords instead of loading them directly from varying. Mali4x0 has native TXP support, however coords and projector have to come from a single source. Add NIR lowering pass that combines coords and projector into a single backend-specific source and use it instead of generic lowering. Unfortunately this change regresses one test, but it also fails in blob and disassembly is now identical. shader-db diff: total instructions in shared programs: 15623 -> 15603 (-0.13%) instructions in affected programs: 877 -> 857 (-2.28%) helped: 7 HURT: 0 helped stats (abs) min: 2 max: 8 x̄: 2.86 x̃: 2 helped stats (rel) min: 0.87% max: 10.53% x̄: 4.93% x̃: 1.85% 95% mean confidence interval for instructions value: -4.95 -0.76 95% mean confidence interval for instructions %-change: -9.31% -0.55% Instructions are helped. total loops in shared programs: 3 -> 3 (0.00%) loops in affected programs: 0 -> 0 helped: 0 HURT: 0 total spills in shared programs: 136 -> 137 (0.74%) spills in affected programs: 0 -> 1 helped: 0 HURT: 1 total fills in shared programs: 598 -> 602 (0.67%) fills in affected programs: 0 -> 4 helped: 0 HURT: 1 Tested-by: Denis Pauk <pauk.denis@gmail.com> Reviewed-by: Andreas Baierl <ichgeh@imkreisrum.de> Signed-off-by: Vasily Khoruzhick <anarsoul@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13111> |
||
---|---|---|
.gitlab/issue_templates | ||
.gitlab-ci | ||
android | ||
bin | ||
build-support | ||
docs | ||
include | ||
src | ||
subprojects | ||
.dir-locals.el | ||
.editorconfig | ||
.gitignore | ||
.gitlab-ci.yml | ||
.mailmap | ||
.travis.yml | ||
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.