OpenSWR added to mesa. http://openswr.org/ Citation from the site below: > How to build Mesa with OpenSWR: > On Linux, OpenSWR is built using the standard autoconf package as described here, with the addition of "swr" to the list of gallium drivers. > Example: > ./configure --disable-dri --disable-egl --enable-xlib-glx --with-gallium-drivers=swrast,swr VIDEO_CARD="swr" option should be added to use this .
Created attachment 555094 [details, diff] proposed patch over mesa-18.3.0_rc2.ebuild (at least for 18.2.4 too) - proposed ebuild patch, adding CPU_FLAGS_X86: avx avx2 avx512bw avx512er avx512f. Testing over current CFLAGS to current common feature levels (-march=*, -mavx*) and build all swr modules from CFLAGS to useflags. This feature levels are runtime selected and may be used all for bindist (or upgrades).
Created attachment 555096 [details, diff] (fixed) proposed patch over mesa-18.3.0_rc2.ebuild sorry, my usual last seconds bug... cleaned/fixed
To be honest I'm really unexcited about adding OpenSWR support because of all the additional complications it will brings. Can we simply enable all SWR backends and be done with it? I don't see much reason to offer all the configurability if they're all run-time selected.
Or, to make dafault all ON but still reasonable optimized - prefix "+" to all cpu_flags_x86_* in IUSE in my patch...
fyi: https://bugs.freedesktop.org/show_bug.cgi?id=109023 - meson-specific bug to build "future" features
Created attachment 563288 [details, diff] mesa-18.3.2-swr2.patch Simple build only one actual (autodetected by CXXFLAGS) swr arch without additional USE (on amd64+gallium+llvm).
Created attachment 563290 [details, diff] fixed - mesa-18.3.2-swr3.patch fixed
Created attachment 563294 [details, diff] fixed2 mesa-18.3.2-swr3.patch fixed again. sorry, last minute converting from working external script...
Created attachment 563296 [details, diff] fixed2 mesa-18.3.2-swr4.patch fixed again. sorry, last minute converting from working external script...
(In reply to Matt Turner from comment #3) > To be honest I'm really unexcited about adding OpenSWR support because of > all the additional complications it will brings. ... especially since it seems to be almost entirely unmaintained now.
