Re: [Mesa-dev] [ANNOUNCE] Mesa 20.0 branchpoint planned for 2020/01/29, Milestone opened

2020-01-29 Thread Pierre Moreau
On 2020-01-30 — 07:23, Dieter Nützel wrote: > Ugh, LLVM git now at 11.0...missed that. > SPIRV-LLVM-Translator choke with 11.0 git (I think it was the same with 10.0 > git), here. (See below.) > So I can't compile Mesa git (20.0) with '-Dopencl-spirv=true' since November > (15.11.2019). The

Re: [Mesa-dev] [ANNOUNCE] Mesa 20.0 branchpoint planned for 2020/01/29, Milestone opened

2020-01-29 Thread Dieter Nützel
Am 30.01.2020 02:59, schrieb Karol Herbst: On Thu, Jan 30, 2020 at 2:37 AM Dieter Nützel wrote: Maybe compilation with '-Dopencl-spirv=true', again. It is broken, now. Even LLVM 10.0 won't compile for me with SPIRV-LLVM-Translator, currently. do you have any more details on that? It could

[Mesa-dev] [PATCH] vulkan: Add VK_GOOGLE_display_timing extension (x11+display, anv+radv) [v8]

2020-01-29 Thread Keith Packard
This adds support for the VK_GOOGLE_display timing extension, which provides two things: 1) Detailed information about when frames are displayed, including slack time between GPU execution and display frame. 2) Absolute time control over swapchain queue processing. This allows the

Re: [Mesa-dev] [ANNOUNCE] Mesa 20.0 branchpoint planned for 2020/01/29, Milestone opened

2020-01-29 Thread Marek Olšák
Feel free to make the branchpoint now. We don't really need to wait for anybody. Drivers that need fixing can have their fixes backported later. The longer we wait, the greater the chance that somebody will introduce new regressions in master. Marek On Wed, Jan 29, 2020 at 11:02 PM Jason

Re: [Mesa-dev] [ANNOUNCE] Mesa 20.0 branchpoint planned for 2020/01/29, Milestone opened

2020-01-29 Thread Jason Ekstrand
On Wed, Jan 29, 2020 at 4:46 AM Bas Nieuwenhuizen wrote: > On Tue, Jan 28, 2020 at 8:46 PM Dylan Baker wrote: > > > > Quoting Dylan Baker (2020-01-22 10:27:05) > > > Hi list, due to some last minute changes in plan I'll be managing the > 20.0 > > > release. The release calendar has been

Re: [Mesa-dev] [ANNOUNCE] Mesa 20.0 branchpoint planned for 2020/01/29, Milestone opened

2020-01-29 Thread Karol Herbst
On Thu, Jan 30, 2020 at 2:37 AM Dieter Nützel wrote: > > Maybe compilation with '-Dopencl-spirv=true', again. > > It is broken, now. > Even LLVM 10.0 won't compile for me with SPIRV-LLVM-Translator, > currently. > do you have any more details on that? It could be that the spirv-llvm-translator

Re: [Mesa-dev] [ANNOUNCE] Mesa 20.0 branchpoint planned for 2020/01/29, Milestone opened

2020-01-29 Thread Dieter Nützel
Maybe compilation with '-Dopencl-spirv=true', again. It is broken, now. Even LLVM 10.0 won't compile for me with SPIRV-LLVM-Translator, currently. Greetings, Dieter Am 22.01.2020 19:27, schrieb Dylan Baker: Hi list, due to some last minute changes in plan I'll be managing the 20.0 release.

[Mesa-dev] [Review Request (master branch)] svga: Use pipe_shader_state_from_tgsi to set shader state

2020-01-29 Thread Neha Bhende
Use pipe_shader_state_from_tgsi() to set shader state for transformed shader so that we get all correct data for respective shader state. This fixes several regressed glretrace, piglit crashes found during merging upsteam mesa Fixes: bf12bc2dd7a2 (draw: add nir info gathering and building

[Mesa-dev] [Review Request (master branch) 2/2] svga: fix size of format_conversion_table[]

2020-01-29 Thread Neha Bhende
Since we are now using sparse matrix for format_conversion_table, we have to make sure we have last entry in table which gives the sense of required size of format_conversion_table Fixes: 84db6ba7 ("svga: Drop unsupported formats from the format table") Reviewed-by: Charmaine Lee ---

[Mesa-dev] [Review Request (master branch) 1/2] svga: Ensure copy_region_fallback can be used for resource copy

2020-01-29 Thread Neha Bhende
Verify preconditions for copy_region_fallback() before using it, else try cpu_blit if it fails to meet preconditions Fixes crash with viewperf after merged-master-2019-12-10 Fixes: b30589cbd3dd ("mesa/st: Reuse st_choose_matching_format from st_choose_format()") Reviewed-by: Charmaine Lee

[Mesa-dev] [Review Request (master branch)] compiler: change datatype of 'spacing' in shader_info with uint_8

2020-01-29 Thread Neha Bhende
With msvc compiler, enum is signed int. It caused failures with piglit test and glretrace gl4_arb_tessellation_shader_v1 Fixes 84a1a2578dab ('compiler: pack shader_info from 160 bytes to 96 bytes') Fixes vmware bug 2480550 Reviewed-by: Brian Paul Reviewed-by: Charmaine Lee ---

Re: [Mesa-dev] -fno-common build failures (default from upcoming gcc release 10)

2020-01-29 Thread Stefan Dirsch
On Tue, Jan 28, 2020 at 11:45:39AM -0800, Dylan Baker wrote: > Quoting Ian Romanick (2020-01-21 09:50:47) > > On 1/20/20 6:41 AM, Stefan Dirsch wrote: > > > Hi > > > > > > Starting from the upcoming GCC release 10, the default of -fcommon option > > > will > > > change to -fno-common. Due to

Re: [Mesa-dev] [ANNOUNCE] Mesa 20.0 branchpoint planned for 2020/01/29, Milestone opened

2020-01-29 Thread Bas Nieuwenhuizen
On Tue, Jan 28, 2020 at 8:46 PM Dylan Baker wrote: > > Quoting Dylan Baker (2020-01-22 10:27:05) > > Hi list, due to some last minute changes in plan I'll be managing the 20.0 > > release. The release calendar has been updated, but the gitlab milestone > > wasn't > > opened. That has been

Re: [Mesa-dev] [ANNOUNCE] Mesa 20.0 branchpoint planned for 2020/01/29, Milestone opened

2020-01-29 Thread Samuel Pitoiset
On 1/28/20 8:46 PM, Dylan Baker wrote: Quoting Dylan Baker (2020-01-22 10:27:05) Hi list, due to some last minute changes in plan I'll be managing the 20.0 release. The release calendar has been updated, but the gitlab milestone wasn't opened. That has been corrected, and is here

[Mesa-dev] swrast driver dll

2020-01-29 Thread bigfarmer
Hi I'm trying to build swrast driver with MinGW. It seems like the build system creates swrast_dri.so instead of .dll format. I want to call *__driDriverGetExtensions_swrast* function directly from my program. 1. how can I configure the build in order to get swrast_dri.dll ? or 2. Does