82ee30e558
When the EU validator encountered an error, it would add an annotation to the disassembly. Unfortunately, the code to insert an error assumed that the next instruction would start at (offset + sizeof(brw_inst)), which is not true if the instruction with an error is compacted. This could lead to cascading disassembly errors, where we started trying to decode the next instruction at the wrong offset, and getting lots of scary looking output: ERROR: Register Regioning patterns where [...] (-f0.1.any16h) illegal(*** invalid execution size value 6 ) { align1 $7.src atomic }; (+f0.1.any16h) illegal.sat(*** invalid execution size value 6 ) { align1 $9.src AccWrEnable }; illegal(*** invalid execution size value 6 ) { align1 $11.src }; (+f0.1) illegal.sat(*** invalid execution size value 6 ) { align1 F@2 AccWrEnable }; (+f0.1) illegal.sat(*** invalid execution size value 6 ) { align1 F@2 AccWrEnable }; (+f0.1) illegal.sat(*** invalid execution size value 6 ) { align1 $15.src AccWrEnable }; illegal(*** invalid execution size value 6 ) { align1 $15.src }; (+f0.1) illegal.sat.g.f0.1(*** invalid execution size value 6 ) { align1 $13.src AccWrEnable }; Only the first instruction was actually wrong - the rest are just a result of starting the disassembler at the wrong offset. Trash ensues! To fix this, just pass the instruction size in a few layers so we can record the next offset properly. Cc: mesa-stable Reviewed-by: Francisco Jerez <currojerez@riseup.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17624> |
||
---|---|---|
.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.