mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-01-09 17:00:13 +01:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
d9449c5201
Right now we always write to a temp and than emit movs to both POS and WPOS. When the result is trivial, like: MOV temp[0], in[0] MOV output[0], temp[0] MOV output[1], temp[0] the dataflow analysis passes can take care of it, this is however one of the last optimizations we need the pass for. Additionally it fails even for some still trivial cases like: MAD temp[2], const[3], temp[0].wwww, temp[1]; MOV output[0], temp[2]; MOV output[2], temp[2]; This patch will just duplicate the output instuction when there is only a single output write. The long-term plan would be to just trust NIR, do as little in the backend as possible and optimize the remaining backend passes to not need any additional cleanups. total instructions in shared programs: 105862 -> 105427 (-0.41%) instructions in affected programs: 20527 -> 20092 (-2.12%) total temps in shared programs: 14029 -> 13991 (-0.27%) temps in affected programs: 152 -> 114 (-25.00%) Signed-off-by: Pavel Ondračka <pavel.ondracka@gmail.com> Reviewed-by: Filip Gawin <filip.gawin@zoho.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15321> |
||
|---|---|---|
| .gitlab/issue_templates | ||
| .gitlab-ci | ||
| android | ||
| bin | ||
| build-support | ||
| docs | ||
| include | ||
| src | ||
| subprojects | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .travis.yml | ||
| 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.