Jesse Natalie
f9b0382faf
There's a few changes in here that are very inter-related. First, we stop lowering load_deref on shader_temp to load_ptr_dxil, and just leave it as load_deref. In order for that to work, we need the derefs to be in a shape that's acceptable to DXIL, so the only current producer of shader_temp loads (the CLC frontend) needs to run some lowering passes on them first. The DXIL backend is augmented to just write out deref indices while walking a deref chain, which will get combined in the load op into a GEP instruction. For non-mesh/raytracing shaders, these are required to be single-level scalar arrays, but the complexity here is preparation for when we don't need to do that anymore. Additionally, the const lookups are changed from using a hash table to just putting an index on the variable. All of this together is enough to enable the authored-forever-ago test which uses indirect array access into a const packed struct. The load_ptr_dxil handling didn't deal with packed structs / unaligned accesses, but now that we're in a logical address space with derefs instead of physical, there's no alignment to deal with anymore and the fact that it's packed goes out the window. This removes one custom DXIL intrinsic. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/23173>
`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.