Alyssa Rosenzweig
cc04a65828
libwrap.dylib is helpful to trace control streams on macOS. When it was originally implemented, we.. * supported macOS in our OpenGL driver and needed to actually exercise these interfaces * didn't have Linux support or hypervisor support or anything so needed the traces to be utterly thorough * only had a single macOS version to worry about The landscape today is very different * no macOS support in our driver stack * we can trace registers via the hypervisor - libwrap.dylib is no longer "correctness" bearing, it's just a convenience tool * what counts is the hardware side - tracing all the macOS software structs is not actually useful, the hypervisor is the right place to grab control regs * piles of macOS versions, this code only ever worked properly on 11.x and 12.x, but with m4 r/e coming up soon we need a lot more versions working. So... we keep around libwrap.dylib, but slim it down to only decode the bare minimum of macOS versioned structures, just enough to grab the control stream pointer and dump that. This is a loss of functionality around CRs (but we have the hypervisor as a much better way to grab CRs). In exchange it makes the code much more manageable and less likely to break every 6 months. So in exchange for all this deletion we also get things working again, this time on 13.x. But porting back to 12.x or 11.x would be a very small diffstat given the reduced focus of the new code. Signed-off-by: Alyssa Rosenzweig <alyssa@rosenzweig.io> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/33682>
`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://docs.mesa3d.org/install.html>`_), but the recommended way is to use Meson (`docs/meson.rst <https://docs.mesa3d.org/meson.html>`_): .. code-block:: sh $ meson setup build $ ninja -C build/ $ sudo ninja -C build/ 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://docs.mesa3d.org/bugs.html>`_). Contributing ------------ Contributions are welcome, and step-by-step instructions can be found in our documentation (`docs/submittingpatches.rst <https://docs.mesa3d.org/submittingpatches.html>`_). Note that Mesa uses gitlab for patches submission, review and discussions.