mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2025-12-29 05:50:11 +01:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
05f8efbc2c
These end up having a NOP between the ldvary and the next instruction in the sequence (a MOV for flat and an FADD for noperspetive): nop ; nop ; ldvary.r0 nop ; nop fadd rf6, r0, r5 ; nop ; ldvary.r1 nop ; nop fadd rf5, r1, r5 ; nop ; ldvary.r2 nop ; nop fadd rf4, r2, r5 ; nop ; ldvary.r3 To pipeline these, we can reuse the same infrastructure we have in place for smooth varyings but we need to avoid breaking the sequence due to the NOP instruction. We do that by testing if dropping the sequence when we failed to pick up the next instruction also fails to choose an instruction. This is not perfect, because we may be able to choose an instruction outside the sequence such as an ldunif, and use that to break a sequence that we could otherwise continue after scheduling the NOP instruction, but it is still better than nothing. total instructions in shared programs: 13820690 -> 13819774 (<.01%) instructions in affected programs: 64026 -> 63110 (-1.43%) helped: 479 HURT: 62 Instructions are helped. total max-temps in shared programs: 2326435 -> 2326423 (<.01%) max-temps in affected programs: 102 -> 90 (-11.76%) helped: 7 HURT: 0 Max-temps are helped. total sfu-stalls in shared programs: 30683 -> 30710 (0.09%) sfu-stalls in affected programs: 13 -> 40 (207.69%) helped: 2 HURT: 24 Sfu-stalls are HURT. total inst-and-stalls in shared programs: 13851373 -> 13850484 (<.01%) inst-and-stalls in affected programs: 62818 -> 61929 (-1.42%) helped: 466 HURT: 65 Inst-and-stalls are helped. Reviewed-by: Alejandro Piñeiro <apinheiro@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9304> |
||
|---|---|---|
| .appveyor | ||
| .gitlab/issue_templates | ||
| .gitlab-ci | ||
| bin | ||
| build-support | ||
| ci-expects | ||
| docs | ||
| doxygen | ||
| include | ||
| scons | ||
| src | ||
| subprojects | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .travis.yml | ||
| Android.common.mk | ||
| Android.mk | ||
| appveyor.yml | ||
| CleanSpec.mk | ||
| common.py | ||
| meson.build | ||
| meson_options.txt | ||
| README.rst | ||
| REVIEWERS | ||
| SConstruct | ||
| 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 `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.