Re: [Mesa-dev] Chromium - Application-level nouveau blacklist

On 1/6/19 9:37 AM, Jason Ekstrand wrote: On Sat, Jan 5, 2019 at 2:40 PM Ilia Mirkin > wrote: It looks like as of Chromium 71, nouveau is completely blacklisted. That's rather unfortunate. :-(  The intel mesa drivers were also blacklisted for quite some time

Re: [Mesa-dev] [RFC 0/6] Enable fp16 visuals and fbconfigs

Hi; On 1/4/19 11:56 PM, Kevin Strasser wrote: This series enables fp16 fbconfigs and visuals by leveraging existing off-screen rendering support. These formats can be used in conjunction with EXT_surface_SMPTE2086_metadata (not yet implemented by any drivers) to support EXT_gl_colorspace_scrgb

[Mesa-dev] [Bug 109159] [KBL-G][vulkan] dEQP-VK.api.version_check.entry_points test failed.

https://bugs.freedesktop.org/show_bug.cgi?id=109159 --- Comment #2 from dong xinyu --- Created attachment 142990 --> https://bugs.freedesktop.org/attachment.cgi?id=142990&action=edit TestResults.qpa update the attachment -- You are receiving this mail because: You are the assignee for the bu

Re: [Mesa-dev] [PATCH v2 51/53] intel/compiler: support half-float in the combine constants pass

On Thu, Jan 03, 2019 at 08:49:48AM +0100, Iago Toral wrote: > On Wed, 2019-01-02 at 13:02 +0200, Pohjolainen, Topi wrote: > > On Wed, Dec 19, 2018 at 12:51:19PM +0100, Iago Toral Quiroga wrote: > > > --- > > > .../compiler/brw_fs_combine_constants.cpp | 60 > > > +++ > > > 1 fi

[Mesa-dev] [Bug 109151] [KBL-G][vulkan] dEQP-VK.texture.explicit_lod.2d.sizes.31x55_nearest_linear_mipmap_nearest_repeat failed verification.

https://bugs.freedesktop.org/show_bug.cgi?id=109151 --- Comment #9 from Hai --- Verified with this patch. This test case can pass with this patch, thanks. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.___

[Mesa-dev] [Bug 109231] [nir] src/compiler/nir/nir_loop_analyze.c uninitialized variable

https://bugs.freedesktop.org/show_bug.cgi?id=109231 Timothy Arceri changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

Re: [Mesa-dev] [PATCH] nir: avoid uninitialized variable warning

Reviewed-by: Bas Nieuwenhuizen On Mon, Jan 7, 2019 at 12:35 AM Timothy Arceri wrote: > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109231 > --- > src/compiler/nir/nir_loop_analyze.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/src/compiler/nir/nir_loop_a

[Mesa-dev] [Bug 109231] [nir] src/compiler/nir/nir_loop_analyze.c uninitialized variable

https://bugs.freedesktop.org/show_bug.cgi?id=109231 --- Comment #3 from Timothy Arceri --- I've sent a patch to avoid the warning: https://patchwork.freedesktop.org/patch/275164/ -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.__

[Mesa-dev] [PATCH] nir: avoid uninitialized variable warning

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109231 --- src/compiler/nir/nir_loop_analyze.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/compiler/nir/nir_loop_analyze.c b/src/compiler/nir/nir_loop_analyze.c index 259f02a854..6deb6cb962 100644 --- a/src/compile

[Mesa-dev] [Bug 109231] [nir] src/compiler/nir/nir_loop_analyze.c uninitialized variable

https://bugs.freedesktop.org/show_bug.cgi?id=109231 --- Comment #2 from osch...@web.de --- Ok, that makes sense, thanks. Would it be a good idea to zero-initialize the variable anyways, just to silence the warning? Anyways, feel free to close this. -- You are receiving this mail because: You are

[Mesa-dev] [Bug 109231] [nir] src/compiler/nir/nir_loop_analyze.c uninitialized variable

https://bugs.freedesktop.org/show_bug.cgi?id=109231 --- Comment #1 from Timothy Arceri --- The first two conditions of the if can never be true on the first iteration of the loop so we will never actually do a comparison with an uninitialized variable. Unfortunately the compiler can't know that.

Re: [Mesa-dev] Chromium - Application-level nouveau blacklist

On Sat, Jan 5, 2019 at 3:40 PM Ilia Mirkin wrote: > > It looks like as of Chromium 71, nouveau is completely blacklisted. > > I don't really see a way back from this, since they don't cite any > easily reproducible issues, except that some people had some issues > with indeterminate hardware and i

[Mesa-dev] [Bug 109231] [nir] src/compiler/nir/nir_loop_analyze.c uninitialized variable

https://bugs.freedesktop.org/show_bug.cgi?id=109231 osch...@web.de changed: What|Removed |Added CC||t_arc...@yahoo.com.au -- You are recei

[Mesa-dev] [Bug 109231] [nir] src/compiler/nir/nir_loop_analyze.c uninitialized variable

https://bugs.freedesktop.org/show_bug.cgi?id=109231 Bug ID: 109231 Summary: [nir] src/compiler/nir/nir_loop_analyze.c uninitialized variable Product: Mesa Version: git Hardware: Other OS: All Sta

[Mesa-dev] [Bug 109204] [regression, bisected] retroarch's crt-royale shader crash radv

https://bugs.freedesktop.org/show_bug.cgi?id=109204 --- Comment #13 from osch...@web.de --- (In reply to Bas Nieuwenhuizen from comment #12) > https://gitlab.freedesktop.org/mesa/mesa/merge_requests/67 > > fixes the crash parsing the fragment shader for me. With this patch applied it works corre

[Mesa-dev] [RFC] clover/meson: Ignore 'svn' suffix when computing CLANG_RESOURCE_DIR

The version exported by LLVM in its CMake configuration files can include the “svn” suffix when building a development version (for example “8.0.0svn”). However the exported clang headers are still found under “lib/clang/8.0.0/”, without the “svn” suffix. This processing is already performed in “co

[Mesa-dev] [Bug 109204] [regression, bisected] retroarch's crt-royale shader crash radv

https://bugs.freedesktop.org/show_bug.cgi?id=109204 --- Comment #12 from Bas Nieuwenhuizen --- https://gitlab.freedesktop.org/mesa/mesa/merge_requests/67 fixes the crash parsing the fragment shader for me. -- You are receiving this mail because: You are the QA Contact for the bug. You are the