Timo Aaltonen pushed to branch upstream-experimental at X Strike Force / lib / mesa
Commits: 30645ecb by Eric Engestrom at 2024-08-14T11:01:39+02:00 .pick_status.json: Update to c90e2bccf756004e48f9e7e71e555db0d03c1b98 - - - - - f55d119d by Eric Engestrom at 2024-08-14T11:14:57+02:00 ci: pass MESA_SPIRV_LOG_LEVEL from job to the test Fixes: 4b8735cd4e2fd5fca820 ("ci: raise the log level threshold of spirv logs") Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30546> (cherry picked from commit b6d8459e3a0b630b5f4365a2df0974381ada82cc) - - - - - 19e29aca by Karol Herbst at 2024-08-14T11:50:06+02:00 rusticl/memory: Fix memory unmaps after rework An application could map and unmap a host ptr allocation multiple times, but because how the refcounting works, we might never ended up syncing the written data to the mapped region. This moves the refcounting out of the event processing. Fixes: 7b22bc617bf ("rusticl/memory: complete rework on how mapping is implemented") Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30528> (cherry picked from commit 1fa288b224efe6a41d056dc08b3cb783e4f8f841) - - - - - 34ad0f8b by Karol Herbst at 2024-08-14T11:50:06+02:00 rusticl/image: take pitches into account when allocating memory for maps This is more correct than the previous code and the CL CTS relies on edge case behavior here, e.g. for 1Dbuffer images. I think part of that is not actually required by the spec, but whatever. Fixes: 7b22bc617bf ("rusticl/memory: complete rework on how mapping is implemented") Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30528> (cherry picked from commit 2484331e8282146a89f371a69b3f91f81cb882ed) - - - - - 7880933b by Karol Herbst at 2024-08-14T11:50:06+02:00 rusticl/image: properly sync mappings content for 1Dbuffer images This fixes clFillImage 1Dbuffer use_pitches CL CTS tests. Fixes: 7b22bc617bf ("rusticl/memory: complete rework on how mapping is implemented") Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30528> (cherry picked from commit 012323a1d196b89cdc289270a16b3f3d0df49379) - - - - - 54386fe9 by Sil Vilerino at 2024-08-14T11:50:40+02:00 Revert "d3d12: Video Encode - Remove PIPE_VIDEO_PROFILE_MPEG4_AVC_BASELINE as not supported" This reverts commit d6bb4ddc638f3ee37fbbe066c631dad80aaeb2d3. Fixes: d6bb4ddc638 ("d3d12: Video Encode - Remove PIPE_VIDEO_PROFILE_MPEG4_AVC_BASELINE as not supported") PIPE_VIDEO_PROFILE_MPEG4_AVC_BASELINE is necessary for some scenarios like the example below described in https://github.com/microsoft/WSL/issues/11838 gst-launch-1.0 -v videotestsrc num-buffers=250 ! video/x-raw,width=1920,height=1200 ! vaapipostproc ! vaapih264enc ! filesink location=~/wsl_test.h264 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30548> (cherry picked from commit a0f1a708c4f3abb055734d35fb3b35b3db15210b) - - - - - c7dfe51e by Paulo Zanoni at 2024-08-14T11:51:03+02:00 intel: fix compute SLM sizes on Xe2 and newer Before the patch, intel_device_info_get_max_preferred_slm_size() returns values in kilobytes, but then intel_device_info_get_max_slm_size() is multiplying it by 1024. As a result, LNL is reporting maxComputeSharedMemorySize to be 134217728, which is 128mb. Fix this by making intel_device_info_get_max_slm_size() not multiply it by 1024. This should fix at least the following dEQP tests: dEQP-VK.compute.pipeline.zero_initialize_workgroup_memory.max_workgroup_memory.1 dEQP-VK.compute.pipeline.zero_initialize_workgroup_memory.max_workgroup_memory.128 dEQP-VK.compute.pipeline.zero_initialize_workgroup_memory.max_workgroup_memory.16 dEQP-VK.compute.pipeline.zero_initialize_workgroup_memory.max_workgroup_memory.2 dEQP-VK.compute.pipeline.zero_initialize_workgroup_memory.max_workgroup_memory.4 dEQP-VK.compute.pipeline.zero_initialize_workgroup_memory.max_workgroup_memory.64 Some tests were failing with: deqp-vk: ../../src/intel/common/intel_compute_slm.c:24: slm_encode_lookup: Assertion `kbytes <= table[table_len - 1].size_in_kb' failed. while other tests were triggering the OOM. v2: - Make everybody return sizes in bytes (José). v3: - Rename variable to bytes (José, Jordan). Fixes: fd368f552112 ("anv: Set maxComputeSharedMemorySize value for Xe2 platforms") Reviewed-by: Jordan Justen <jordan.l.jus...@intel.com> Reviewed-by: José Roberto de Souza <jose.so...@intel.com> Signed-off-by: Paulo Zanoni <paulo.r.zan...@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30541> (cherry picked from commit 0e38b794e29482c55e74d7c1a6558c3a850b0f4e) - - - - - 4194c3b9 by Eric Engestrom at 2024-08-14T11:51:05+02:00 android: fix build in multiple ways Includes the libgallium versioning, the megadriver hardlink -> symlink change, and some fixes for things like abusing ls output. backport-to: 24.2 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30470> (cherry picked from commit 9568976c52a4b9fb4af659d127bfc6f9d9e7970d) - - - - - 5c6f0280 by Marek Olšák at 2024-08-14T11:51:11+02:00 ac/surface/gfx12: turn off HiZ for pre-production samples Fixes: f703dfd1bb8 - radeonsi: add gfx12 Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-pra...@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30525> (cherry picked from commit 97d664b22f09fe68df3613a2b86c1b0a8dda9cc8) - - - - - 3610b26a by Eric R. Smith at 2024-08-14T11:51:12+02:00 panfrost: fix texture.border_clamp regression for valhall We have to swizzle the border color in order to offset the automatic swizzling introduced to compensate for limited component order support in AFBC/AFRC. However, the border color format is only available if the `TEXTURE_BORDER_COLOR_QUIRK` is enabled, so set that for v10 (it was already set for v7). While testing, we uncovered another issue: valhall introduces a swizzle for depth+stencil formats that isn't present for bifrost, and also isn't needed (or wanted) for the border color. So ignore the border color swizzle for depth+stencil on valhall (on bifrost the swizzle is a no-op anyway). Fixes: 87aad0a5e4f ("panfrost: encode component order as an inverted swizzle (v10)") Reviewed-by: Louis-Francis Ratté-Boulianne <l...@collabora.com> Reviewed-by: Mary Guillemard <mary.guillem...@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30542> (cherry picked from commit 3135f76331aee4f7bad50a7e1236f81e149cc746) - - - - - 3f8d9068 by Eric R. Smith at 2024-08-14T11:51:13+02:00 panfrost: use RGB1 component ordering for R5G6B5 pixel formats For some purposes (e.g. advanced blending) we need a non-zero alpha value returned from reads. This is only guaranteed on Bifrost if we explicitly request RGB1 component ordering. The default is to use RGBA component ordering, which for R5G6B5 causes 0 to be read for alpha. A complication is that the Mali fixed function hardware requires four components (which implies RGBA rather than RGB1). If fixed function blending is in use, we modify the pixel format back to RGBA when building the blend descriptor. Cc: mesa-stable Reviewed-by: Boris Brezillon <boris.brezil...@collabora.com> Reviewed-by: Mary Guillemard <mary.guillem...@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29606> (cherry picked from commit 004e0eb3ab854957bdb798142678765360b7104b) - - - - - 6e51ea00 by Lionel Landwerlin at 2024-08-14T11:51:14+02:00 anv/blorp: force CC_VIEWPORT reallocation when programming 3DSTATE_VIEWPORT_STATE_POINTERS_CC Signed-off-by: Lionel Landwerlin <lionel.g.landwer...@intel.com> Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11647 Fixes: fe1baa6481 ("anv: reduce blorp dynamic state emissions") Reviewed-by: Tapani Pälli <tapani.pa...@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30532> (cherry picked from commit 10533e7b4cbbaca7c01a7e9a59ff4c20173710f6) - - - - - 3fcb2db3 by Karol Herbst at 2024-08-14T11:51:17+02:00 rusticl/queue: add clSetCommandQueueProperty The CL CTS started to call this API, luckily we don't have to actually implement it, because we don't intent to support CL 1.0 only devices in the first place (probably). Cc: mesa-stable Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30575> (cherry picked from commit cd2dc4f70c35b6981789b02c32a9f1d71562638c) - - - - - 0a8b665c by Tapani Pälli at 2024-08-14T11:51:18+02:00 anv: fix a cmd_buffer reference in simple shader In utrace timestamp copy case cmd_buffer is NULL. Fixes: dbbcd5c32c ("anv: factor out generation kernel dispatch into helper") Signed-off-by: Tapani Pälli <tapani.pa...@intel.com> Reviewed-by: Lionel Landwerlin <lionel.g.landwer...@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30475> (cherry picked from commit ff8953f66621329d8c2eaaf4cfa5e51d7f8dcd80) - - - - - ec87b9cb by Mike Blumenkrantz at 2024-08-14T11:51:28+02:00 egl: fix zink init * close(fd) requires also resetting the fd=-1 or else boom * checking just driver_name is broken because loader_get_driver_for_fd() uses MESA_LOADER_DRIVER_OVERRIDE, so there's no way to differentiate an inferred load Fixes: b907eb47504 ("egl: don't bind zink under dri2/3") Acked-by: Dave Airlie <airl...@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30556> (cherry picked from commit 1a579552afb86a56e0923cd739e2fcdb063039aa) - - - - - 8fd12baa by Mike Blumenkrantz at 2024-08-14T11:51:29+02:00 dri: fix kms_swrast screen fail this should match all the other screen init functions cc: mesa-stable Reviewed-by: Marek Olšák <marek.ol...@amd.com> Reviewed-by: Adam Jackson <a...@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30524> (cherry picked from commit d6ac254c0152cbb760ee87e8243c78f87503f805) - - - - - 2ff3011b by Georg Lehmann at 2024-08-14T11:51:29+02:00 nir/lower_int64: replace uadd_sat with ior for find_lsb64 and ufind_msb64 Using ior here is equivalent to using uadd_sat, but works for every driver and shouldn't hurt anywhere. I forgot to fix this up when fixing up some vvl errors with zink. Fixes crashes with the integer_ctz CL CTS tests in zink. Fixes: 39ec184db6e ("zink: lower 64 bit find_lsb, ufind_msb and bit_count") Reviewed-by: Karol Herbst <kher...@redhat.com> Reviewed-by: Alyssa Rosenzweig <aly...@rosenzweig.io> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30535> (cherry picked from commit 48acf9d3583cf5fc1c4036a14e21e27df2f8bb86) - - - - - c9f1f288 by Jesse Natalie at 2024-08-14T11:51:43+02:00 meson: Add an error message for llvmpipe without llvm draw support Fixes: 010b2f9497a ("gallium/meson: Deconflate swrast/softpipe/llvmpipe") Reviewed-by: Eric Engestrom <e...@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30577> (cherry picked from commit 169f8ec2270b54af75a2c7688dcbb461afbb0375) - - - - - 6f625b1b by Ian Romanick at 2024-08-14T11:52:15+02:00 intel/brw: Don't propagate saturate to an instruction that writes flags There are two problems. 1. This is not NaN safe. 'add.le.sat dst F, Inf F, -Inf F' has a different result than 'add dst F, Inf F, -Inf F; cmp.le null, dst F, 0F'. 2. Ignoring the first problem, this only produces the desired flags for LE and G. All other cases can produce the wrong result. For example, batman_arkham_city_goty.foz 6a63c4caacaa0dae has the following code: mad.ge.f0.0(8) g51<1>F g50<8,8,1>F g46<8,8,1>F g11<1,1,1>F mov.sat(8) g52<1>F g51<1,1,0>F ... (+f0.0) sel(8) g54<1>UD g53<8,8,1>UD 0x3f000000UD Without this commit, the saturate is incorrectly propagated to the MAD. A similar case exists in witcher_3_dxvk_g2.foz 5b03243be667a275. There are even worse cases like total_war_warhammer3.dx12vk-g6.foz 78328466761ef7ab and ee920491573860fc. The former has the following code (and the latter has very similar code): mad.l.f0.0(16) g95<1>F g93<8,8,1>F g62<8,8,1>F g68<1,1,1>F ... mov.sat(16) g109<1>F -g95<1,1,0>F ... (+f0.0) sel(16) g68<1>UD g111<1,1,0>UD g54<1,1,0>UD (+f0.0) sel(16) g70<1>UD g113<1,1,0>UD g56<1,1,0>UD (+f0.0) sel(16) g72<1>UD g115<1,1,0>UD g58<1,1,0>UD Saturate propagation makes a hash of this code: mad.sat.l.f0.0(16) g106<1>F -g93<8,8,1>F -g62<8,8,1>F g68<1,1,1>F ... (+f0.0) sel(16) g70<1>UD g110<1,1,0>UD g56<1,1,0>UD (+f0.0) sel(16) g72<1>UD g112<1,1,0>UD g58<1,1,0>UD (+f0.0) sel(16) g68<1>UD g108<1,1,0>UD g54<1,1,0>UD Not only is the saturate incorrectly applied to the MAD, but the MAD result is negated without changing the conditional modifier to G! NOTE: Backports of this commit to stable branches may need to be more like the following commit to elk. shader-db: All Intel platforms had similar results. (Meteor Lake shown) total instructions in shared programs: 19729375 -> 19729377 (<.01%) instructions in affected programs: 112 -> 114 (1.79%) helped: 0 HURT: 2 total cycles in shared programs: 916234266 -> 916234288 (<.01%) cycles in affected programs: 636 -> 658 (3.46%) helped: 0 HURT: 2 fossil-db: All Intel platforms had similar results. (Meteor Lake shown) Totals: Instrs: 151531594 -> 151531601 (+0.00%) Cycle count: 17209107419 -> 17209107474 (+0.00%); split: -0.00%, +0.00% Totals from 6 (0.00% of 630198) affected shaders: Instrs: 4550 -> 4557 (+0.15%) Cycle count: 194629 -> 194684 (+0.03%); split: -0.00%, +0.03% Fixes: 947c828d5cb ("i965/fs: Add a saturation propagation optimization pass.") Reviewed-by: Kenneth Graunke <kenn...@whitecape.org> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29774> (cherry picked from commit 3d8fea0e092e66abcac466ea630e7dcf42c76db8) - - - - - fef088fd by Ian Romanick at 2024-08-14T11:52:16+02:00 intel/elk: Don't propagate saturate to an instruction that writes flags There are two problems. 1. This is not NaN safe. 'add.le.sat dst F, Inf F, -Inf F' has a different result than 'add dst F, Inf F, -Inf F; cmp.le null, dst F, 0F'. 2. Ignoring the first problem, this only produces the desired flags for LE and G. All other cases can produce the wrong result. shader-db: All Intel platforms had similar results. (Broadwell shown) total instructions in shared programs: 18282314 -> 18282316 (<.01%) instructions in affected programs: 78 -> 80 (2.56%) helped: 0 HURT: 2 total cycles in shared programs: 952924234 -> 952924252 (<.01%) cycles in affected programs: 584 -> 602 (3.08%) helped: 0 HURT: 2 Fixes: e6022281f27 ("intel/elk: Rename files to use elk prefix") Reviewed-by: Kenneth Graunke <kenn...@whitecape.org> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29774> (cherry picked from commit 9125b7c1b41c75a4f39ce2949f74530ae7f1fde0) - - - - - 7ce99a3f by Faith Ekstrand at 2024-08-14T11:52:16+02:00 nvk: Require color or depth/stencil attachment support for input attachments Fixes: 20d8d1e239be ("nvk: Add a more competent GetPhysicalDeviceImageFormatProperties") Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30580> (cherry picked from commit 08f6066e87a461444f347bef56e5e56225e5c2c3) - - - - - cd2ea3a4 by Faith Ekstrand at 2024-08-14T11:52:17+02:00 nvk: Support STORAGE_READ_WITHOUT_FORMAT on buffers Fixes: fc191730145e ("nvk: Rework format features queries") Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30580> (cherry picked from commit 8244b87822e7f9b744eee9ff77078cb77c1ab6cc) - - - - - 239fb0bd by Faith Ekstrand at 2024-08-14T11:52:19+02:00 zink: Align descriptor buffers to descriptorBufferOffsetAlignment Instead of aligning offsets, we just align the size every time we query it. This simplifies our offset and size calculations later since we can always just add up descriptor buffer sizes and know that we'll be okay. Acked-by: Mike Blumenkrantz <michael.blumenkra...@gmail.com> Fixes: 7ab5c5d36d2b ("zink: use EXT_descriptor_buffer with ZINK_DESCRIPTORS=db") Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30580> (cherry picked from commit 0f8f407e572734462fb2d2ea17296b747f67446c) - - - - - 3cf68b12 by David Heidelberg at 2024-08-14T11:52:19+02:00 llvmpipe: Silence "possibly uninitialized value" warning for ssbo_limit (cont) Fixes: ce611935df5e ("llvmpipe: Silence "possibly uninitialized value" warning for ssbo_limit.") Signed-off-by: David Heidelberg <da...@ixit.cz> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30482> (cherry picked from commit 9c8e75e2564fd29e351d973d517c0d3a93998dcc) - - - - - 88b8d722 by David Heidelberg at 2024-08-14T11:52:24+02:00 ci/alpine: use llvm variables Fixes: da391650f534 ("ci: build a host version of mesa for cross builds") Reviewed-by: Eric Engestrom <e...@igalia.com> Signed-off-by: David Heidelberg <da...@ixit.cz> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30482> (cherry picked from commit 34753cefd828f5db8e9e14cee9c4e45cee5baaaa) - - - - - 75a13131 by Timothy Arceri at 2024-08-14T11:52:39+02:00 glsl: always copy bindless sampler packing constructors to a temp Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11648 Fixes: 3cdcc5f02f39 ("glsl: implement ARB_bindless_texture conversions") Reviewed-by: Marek Olšák <marek.ol...@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30586> (cherry picked from commit 3da4b5eaa51ea74a4e3e1309a75308a9586189a6) - - - - - 6d680b5d by Georg Lehmann at 2024-08-14T11:52:40+02:00 aco/gfx10+: set lateKill for sgprs used by wave64 VALU writing a mask RDNA2 ISA doc, 6.2.4. Wave64 Destination Restrictions: The first pass of a wave64 VALU instruction may not overwrite a scalar value used by the second half. Foz-DB Navi31: Totals from 5221 (6.58% of 79395) affected shaders: Instrs: 9751484 -> 9752179 (+0.01%); split: -0.01%, +0.01% CodeSize: 50624072 -> 50626088 (+0.00%); split: -0.00%, +0.01% Latency: 85646450 -> 85647419 (+0.00%); split: -0.00%, +0.00% InvThroughput: 15039160 -> 15039277 (+0.00%); split: -0.00%, +0.00% VClause: 200275 -> 200204 (-0.04%) SClause: 248645 -> 248607 (-0.02%); split: -0.03%, +0.01% Copies: 640802 -> 641413 (+0.10%); split: -0.01%, +0.11% PreSGPRs: 236297 -> 236735 (+0.19%) VALU: 5666449 -> 5666440 (-0.00%) SALU: 967482 -> 968111 (+0.07%); split: -0.01%, +0.07% Cc: mesa-stable Reviewed-by: Rhys Perry <pendingchao...@gmail.com> Reviewed-by: Daniel Schürmann <dan...@schuermann.dev> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30368> (cherry picked from commit 510f5e55be05e8d6061cda2f53d16abc6a35be55) - - - - - cf393b40 by Mike Blumenkrantz at 2024-08-14T11:52:44+02:00 egl/wayland: bail on zink init in non-sw mode if extension check fails cc: mesa-stable Acked-by: Daniel Stone <dani...@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30479> (cherry picked from commit d120992e1a16e046ee189691f721e636c35c783b) - - - - - 3dc242cb by Valentine Burley at 2024-08-14T11:52:45+02:00 vulkan/wsi: Refactor can_present_on_device Make wsi_device_matches_drm_fd() a default helper that PCI based GPUs plug in to wsi_dev->can_present_on_device. This is needed for devices without libdrm, where wsi_device_matches_drm_fd was still being called causing an "undefined reference" build error. Suggested-by: Rob Clark <robdcl...@chromium.org> Fixes: baa38c144f6 ("vulkan/wsi: Use VK_EXT_pci_bus_info for DRM fd matching") Reviewed-by: Mark Collins <m...@igalia.com> Reviewed-by: Faith Ekstrand <faith.ekstr...@collabora.com> Signed-off-by: Valentine Burley <valentine.bur...@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29627> (cherry picked from commit 47289ebc8d815bac2cf0cbb1515972c94d3cee2b) - - - - - 0ffd6a87 by Valentine Burley at 2024-08-14T11:52:46+02:00 tu: Always report that we can present on kgsl Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/8637 Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/9240 Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/9365 Fixes: 3e7f6c9aebf ("tu: implement wsi hook to decide if we can present directly on device") Signed-off-by: Valentine Burley <valentine.bur...@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29627> (cherry picked from commit 367191ff632e00b1822c53ecead8c48e18b73535) - - - - - fef78c34 by Karol Herbst at 2024-08-14T11:52:47+02:00 util/u_printf: do not double print format string with unused arugments the CL CTS added a new test being printf("\n", "foo"), but we ended up printing the new line twice. If we can't find a specifier anymore, ignore the argument as after the loop processing all arguments we'll print the remaining format string anyway. Cc: mesa-stable Reviewed-by: Jesse Natalie <jenat...@microsoft.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30574> (cherry picked from commit 408026984551665562ce95260b92fd7db7f49c71) - - - - - fbba6b7b by Pavel Ondračka at 2024-08-14T11:52:47+02:00 r300: bias presubtract fix We need to double check that the source is indeed constant before looking at the constant type. Signed-off-by: Pavel Ondračka <pavel.ondra...@gmail.com> Fixes: 0508db91556242c57029ad538613c2b1ee1969ef Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29893> (cherry picked from commit 1cad339409d437ba1170725f7575b016c7c896e7) - - - - - 46ad101f by Karol Herbst at 2024-08-14T11:52:48+02:00 rusticl/memory: fix sampler argument size check Not entirely sure why this hasn't caused any problems... Cc: mesa-stable Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30602> (cherry picked from commit 0cfcd2ff83acb8733f3fb0da56b5764fc268feec) - - - - - db297c65 by Lionel Landwerlin at 2024-08-14T11:52:49+02:00 brw/rt: fix ray_object_(direction|origin) for closest-hit shaders When closest hit shader is called, the BVH object level brw_nir_rt_load_mem_ray origin/direction is 0. What we should be using is the ray origin/direction and apply the transform of the current instance. Signed-off-by: Lionel Landwerlin <lionel.g.landwer...@intel.com> Fixes: 9ba7d459a3 ("intel/rt: Implement the new ray-tracing system values") Reviewed-by: Sagar Ghuge <sagar.gh...@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30578> (cherry picked from commit aaff19135644049cde3bd3ddd649b48f96111fa4) - - - - - f6b2fe84 by Mike Blumenkrantz at 2024-08-14T11:52:50+02:00 zink: fix partial update handling * the damage region was not being used correctly (this is a normal rect) * use_damage was never unset at frame boundary * original renderArea was never re-set Fixes: 3d38c9597ff ("zink: hook up KHR_partial_update") Acked-by: Daniel Stone <dani...@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30625> (cherry picked from commit a7f64c62037eb33e97e0d4a0f9a27345baa8bcc3) - - - - - 7335dbb8 by Matt Turner at 2024-08-14T11:53:31+02:00 util: Add ATTRIBUTE_OPTIMIZE(flags) Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30622> (cherry picked from commit b3430a7bb8b49cb5a4e0cdb1e690f53025d80069) - - - - - 56bef9de by Matt Turner at 2024-08-14T11:53:31+02:00 util: Force emission of stack frame in stack unit test The `capture_not_overwritten` unit test captures and compares two backtraces -- one from inside a call to `func_c` and one outside -- and confirms that they are not identical. That is, that `func_c` is in the backtrace. On 32-bit x86, without `-fno-omit-frame-pointer`, the function will not emit a stack frame. As a result, the unit test fails. The fix is to compile `func_c` with the flag `-fno-omit-frame-pointer` to prevent the compiler from optimizing out the stack frame which is otherwise unneeded. Bug: https://bugs.gentoo.org/823774 Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/4091 Fixes: d0d14f3f648 ("util: Add unit test for stack backtrace caputure") Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30622> (cherry picked from commit 05dc4eb536d0b527c4d0e6dcea177ff318974cae) - - - - - a8ea86d2 by Icenowy Zheng at 2024-08-14T16:06:05+02:00 util: detect LoongArch architecture Only 64-bit is considered now because 32-bit LoongArch Linux support doesn't exist in upstream yet. Signed-off-by: Icenowy Zheng <u...@icenowy.me> Reviewed-by: Dave Airlie <airl...@redhat.com> (cherry picked from commit 08425d9aaff8440eec3a93246b0f3ad7f6fbecab) Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30645> - - - - - 89dbb1ca by Icenowy Zheng at 2024-08-14T16:06:23+02:00 gallivm: add LoongArch support to the mattrs setting code Currently the mattrs is set according to the softdev convention, with LSX explicitly disabled because it's troublesome at least on LLVM 17. Signed-off-by: Icenowy Zheng <u...@icenowy.me> Reviewed-by: Dave Airlie <airl...@redhat.com> (cherry picked from commit 979c36401880132f7c8ca1f70a5fb9e8430b62f8) Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30645> - - - - - df083003 by Icenowy Zheng at 2024-08-14T16:06:29+02:00 llvmpipe: add LoongArch support in ORCJIT LoongArch is an architecture too new to have MCJIT support. Add its support to ORCJIT code. Signed-off-by: Icenowy Zheng <u...@icenowy.me> Reviewed-by: Dave Airlie <airl...@redhat.com> (cherry picked from commit e16a74c0237d2e75bb8ed9c10536c290fe7eb312) Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30645> - - - - - 27b64843 by Icenowy Zheng at 2024-08-14T16:06:34+02:00 gallivm: orcjit: keep the ownership of tm for LPJit The ownership of the TargetMachine object is released when LPJit singleton is constructed, leads to a slight memory loss detectable. Keep the ownership by saving the unique pointer as another class member named tm_unique. Signed-off-by: Icenowy Zheng <u...@icenowy.me> Reviewed-by: Dave Airlie <airl...@redhat.com> (cherry picked from commit 3423e73cece2657e4e0008a60f2f9d0ade618fbe) Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30645> - - - - - b01adb21 by Icenowy Zheng at 2024-08-14T16:06:41+02:00 gallivm: orcjit: use atexit to release LPJit singleton at exit Valgrind will report some memory possibly lost because of this singleton (it's dynamically allocated when it is first accessed). Use atexit() to register a handler that releases this singleton. Signed-off-by: Icenowy Zheng <u...@icenowy.me> Reviewed-by: Dave Airlie <airl...@redhat.com> (cherry picked from commit 5f22e152ade956fdce1b0cba8097d76aac085c92) Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30645> - - - - - 10dfd5d1 by Eric Engestrom at 2024-08-14T16:07:01+02:00 .pick_status.json: Update to 214b6c30406f844560bdf35a54ff8a51ee248709 - - - - - 9f8856c5 by Rob Clark at 2024-08-14T16:07:01+02:00 gallium: Add option to not add version to libgallium filename This is unneeded in some environments, like ChromeOS and Android. And for CrOS it specifically causes problems with the gpu sandbox rules.. we don't want to have to update the sandbox rules for each new mesa version. Signed-off-by: Rob Clark <robdcl...@chromium.org> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30579> (cherry picked from commit 19ff16387a0c844552f4956dfbce176fd62c1cc8) - - - - - 5854ff2d by Antonio Ospite at 2024-08-14T16:07:01+02:00 android: simplify building libgallium_dri on Android The versioned libgallium library can be confusing on Android, and it is probably not even needed there, so simplify the build on Android by always build the unversioned `libgallium_dri.so` overriding the `-Dunversion-libgallium=true` option added in https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30579 Remove also all the bits that deal with the versioned library which are not needed anymore. Fixes: 9568976c52a ("android: fix build in multiple ways") Acked-by: Rob Clark <robdcl...@gmail.com> Reviewed-by: Mauro Rossi <issor.or...@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30641> (cherry picked from commit 2d2bc5b307f9099c79618ea0bae37e31d7bfbcc2) - - - - - a4b0f0f7 by Eric Engestrom at 2024-08-14T17:45:37+02:00 .pick_status.json: Update to cc2dbb8ea5329b509d79eedb6c0cbb9a1903b5ad - - - - - f11e04e3 by Hans-Kristian Arntzen at 2024-08-14T17:45:41+02:00 wsi/x11: Bump maximum number of outstanding COMPLETE events. Fixes a "regression" where comically large FPS tests regressed. Signed-off-by: Hans-Kristian Arntzen <p...@arntzen-software.no> Fixes: 19dba854 ("wsi/x11: Rewrite implementation to always use threads.") Reviewed-By: Mike Blumenkrantz <michael.blumenkra...@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30638> (cherry picked from commit 5a97916fdce788ac707df94d6b3b145a377482ac) - - - - - 14f6b726 by WANG Xuerui at 2024-08-14T17:45:45+02:00 meson: Force use of LLVM ORCJIT for hosts without MCJIT support Although the ORCJIT codepath is fresh and relatively less tested, this is still better than no llvmpipe at all for those newer architectures that will not gain MCJIT support, such as LoongArch or RISC-V. Fixes: 6f02ec5ed18 ("llvmpipe: add an implementation with llvm orcjit") Reviewed-by: Icenowy Zheng <u...@icenowy.me> Reviewed-by: Yukari Chiba <i...@0x7f.cc> Reviewed-by: David Heidelberg <da...@ixit.cz> Signed-off-by: WANG Xuerui <g...@xen0n.name> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30599> (cherry picked from commit 56f38672a28b91f4be8cf2bb89a47df75a67a663) - - - - - a2d4bd10 by WANG Xuerui at 2024-08-14T17:45:45+02:00 meson: Additionally probe -mtls-dialect=desc for TLSDESC support Previously only `-mtls-dialect=gnu2` was probed, which was appropriate for arm, x86 and x86_64, but not for newer architectures such as aarch64, loongarch64 and riscv64 which all use `-mtls-dialect=desc` instead. Because the driver option is not consistent across architectures (and probably will not), try both variants and choose the first one working. While at it, rename "gnu2_*" variables to "tlsdesc_*" respectively, for clarity. Cc: mesa-stable Reviewed-by: Icenowy Zheng <u...@icenowy.me> Reviewed-by: Yukari Chiba <i...@0x7f.cc> Reviewed-by: David Heidelberg <da...@ixit.cz> Signed-off-by: WANG Xuerui <g...@xen0n.name> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30599> (cherry picked from commit cc2dbb8ea5329b509d79eedb6c0cbb9a1903b5ad) - - - - - 22fafc98 by Eric Engestrom at 2024-08-14T18:37:13+02:00 VERSION: bump for 24.2.0 - - - - - 30 changed files: - .gitlab-ci/common/generate-env.sh - .gitlab-ci/container/alpine/x86_64_build.sh - .pick_status.json - VERSION - android/Android.mk - android/mesa3d_cross.mk - meson.build - meson_options.txt - src/amd/common/ac_surface.c - src/amd/compiler/aco_live_var_analysis.cpp - src/compiler/glsl/ast_function.cpp - src/compiler/nir/nir_lower_int64.c - src/egl/drivers/dri2/platform_wayland.c - src/egl/drivers/dri2/platform_x11.c - src/egl/drivers/dri2/platform_x11_dri3.c - src/egl/drivers/dri2/platform_x11_dri3.h - src/freedreno/vulkan/tu_wsi.cc - src/gallium/auxiliary/gallivm/lp_bld_init_orc.cpp - src/gallium/auxiliary/gallivm/lp_bld_misc.cpp - src/gallium/auxiliary/gallivm/lp_bld_tgsi_soa.c - src/gallium/drivers/d3d12/d3d12_video_enc_h264.cpp - src/gallium/drivers/d3d12/d3d12_video_screen.cpp - src/gallium/drivers/panfrost/pan_cmdstream.c - src/gallium/drivers/panfrost/pan_screen.c - src/gallium/drivers/r300/compiler/radeon_optimize.c - src/gallium/drivers/zink/zink_context.c - src/gallium/drivers/zink/zink_descriptors.c - src/gallium/drivers/zink/zink_kopper.c - src/gallium/drivers/zink/zink_screen.c - src/gallium/frontends/dri/dri2.c The diff was not included because it is too large. View it on GitLab: https://salsa.debian.org/xorg-team/lib/mesa/-/compare/f9d8468d29764ce735ffcc70de2005ed7aa8927d...22fafc9824f9afe594e5e3c3d488ef7f47a70a10 -- View it on GitLab: https://salsa.debian.org/xorg-team/lib/mesa/-/compare/f9d8468d29764ce735ffcc70de2005ed7aa8927d...22fafc9824f9afe594e5e3c3d488ef7f47a70a10 You're receiving this email because of your account on salsa.debian.org.
