[Mesa-dev] [PATCH] docs/envvars: Document radv env variables

Signed-off-by: Edward O'Callaghan --- docs/envvars.html | 13 + 1 file changed, 13 insertions(+) diff --git a/docs/envvars.html b/docs/envvars.html index 5dd7bab..f5593b2 100644 --- a/docs/envvars.html +++ b/docs/envvars.html @@ -197,6 +197,19 @@ See the

Re: [Mesa-dev] Leaked hardware event if kernel launch fails?

Hello Francisco! Thank you for your quick reply! On 02:33 pm - Dec 25 2016, Francisco Jerez wrote: > Pierre Moreau writes: > > > Hello, > > > Hi Pierre! > > > I noticed that, if trying to enqueue a kernel which had no > > `module::section::text_executable` attached to

Re: [Mesa-dev] Leaked hardware event if kernel launch fails?

Pierre Moreau writes: > Hello, > Hi Pierre! > I noticed that, if trying to enqueue a kernel which had no > `module::section::text_executable` attached to its clover module, I would get > a > `std::out_of_range` exception, instead of the expected >

[Mesa-dev] Leaked hardware event if kernel launch fails?

Hello, I noticed that, if trying to enqueue a kernel which had no `module::section::text_executable` attached to its clover module, I would get a `std::out_of_range` exception, instead of the expected CL_INVALID_PROGRAM_EXECUTABLE (see [0]; I tried enqueueing using `clEnqueueNDRangeKernel). I

Re: [Mesa-dev] [PATCH 5/6] nir: Add a pass for moving SPIR-V continue blocks to the ends of loops

On Dec 25, 2016 2:15 PM, "Mark Janes" wrote: Jason Ekstrand writes: > When shaders come in from SPIR-V, we handle continue blocks by placing > the contents of the continue inside of a "if (!first_iteration)". We do > this so that we can properly

Re: [Mesa-dev] [PATCH 5/6] nir: Add a pass for moving SPIR-V continue blocks to the ends of loops

Jason Ekstrand writes: > When shaders come in from SPIR-V, we handle continue blocks by placing > the contents of the continue inside of a "if (!first_iteration)". We do > this so that we can properly handle the fact that continues in SPIR-V > jump to the continue block at

[Mesa-dev] [Bug 99125] Log to a file all GALLIUM_HUD infos

https://bugs.freedesktop.org/show_bug.cgi?id=99125 --- Comment #1 from Edmondo Tommasina --- If you want to play a bit with, I've posted some RFC patches to write hud values into logfiles: https://patchwork.freedesktop.org/series/17109/

Re: [Mesa-dev] [PATCH] intel/blorp_blit: Fix max blit size for gen6

On 2016-12-24 19:07:44, Jason Ekstrand wrote: > Guys... Stop reviewing patches on Christmas Eve... Jesus is the reason for the patches! Merry Sunday! ;) > On Dec 24, 2016 7:34 PM, "Kenneth Graunke" wrote: > > > On Saturday, December 24, 2016 9:49:14 AM PST Jordan Justen