I think it would be better to add a new TGSI file for shared variables.
Marek
On Sun, Jan 24, 2016 at 10:09 PM, Samuel Pitoiset
wrote:
> This adds a new SHARED attribute to TGSI_FILE_BUFFER. Only
> one shared buffer can be declared and its size is defined by
>
On Mon, Jan 25, 2016 at 4:02 PM, Ilia Mirkin wrote:
> How about
>
> st/mesa: add compute program dispatch callbacks
>
> or something along those lines. I don't think "state tracker" is the
> right term to use.
With that done:
Reviewed-by: Marek Olšák
On Sun, Jan 24, 2016 at 10:18 PM, Samuel Pitoiset
wrote:
> Signed-off-by: Samuel Pitoiset
> ---
>
> I have forgot this one...
>
> src/gallium/drivers/trace/tr_context.c| 80
> +++
>
Reviewed-by: Marek Olšák
Marek
On Sun, Jan 24, 2016 at 10:09 PM, Samuel Pitoiset
wrote:
> This will allow to query the underlying drivers for the maximum
> total storage size of all variables declared as with
> PIPE_COMPUTE_CAP_MAX_LOCAL_SIZE.
>
For the series:
Reviewed-by: Marek Olšák
Marek
On Tue, Jan 26, 2016 at 8:40 AM, Michel Dänzer wrote:
> From: Michel Dänzer
>
> Failing to do this was resulting in the kernel driver unnecessarily
> leaving open the possibility
Reviewed-by: Marek Olšák
Marek
On Sun, Jan 24, 2016 at 10:09 PM, Samuel Pitoiset
wrote:
> From: Ilia Mirkin
>
> Looks like the various max's were never plumbed through.
>
> Signed-off-by: Ilia Mirkin
Functions cso_save_compute_shader & cso_restore_compute_shader, and
the compute_shader_saved variable can be removed. There is no use for
them as far as I can see.
Marek
On Sun, Jan 24, 2016 at 10:09 PM, Samuel Pitoiset
wrote:
> Signed-off-by: Samuel Pitoiset
I don't understand this. Can you explain it?
AFAIK, shared variables don't need a backing buffer.
Thanks,
Marek
On Sun, Jan 24, 2016 at 10:09 PM, Samuel Pitoiset
wrote:
> At least, one shader buffer must be available for compute shaders.
>
> Signed-off-by: Samuel
With Ilia's suggestion applied:
Reviewed-by: Marek Olšák
Marek
On Mon, Jan 25, 2016 at 3:28 PM, Ilia Mirkin wrote:
> On Sun, Jan 24, 2016 at 4:09 PM, Samuel Pitoiset
> wrote:
>> Like indirect draw, we need to store a
Reviewed-by: Marek Olšák
Marek
On Sun, Jan 24, 2016 at 10:09 PM, Samuel Pitoiset
wrote:
> This binds atomics, constants, samplers, ssbos, textures and ubos.
>
> Signed-off-by: Samuel Pitoiset
> ---
>
On Mon, Jan 25, 2016 at 10:49 PM, Nicolai Hähnle wrote:
> From: Nicolai Hähnle
>
> The new name for the intrinsic was introduced in LLVM r258558.
> ---
> src/gallium/drivers/radeonsi/si_shader.c | 7 ++-
> 1 file changed, 6 insertions(+), 1
On Tue, Jan 26, 2016 at 6:17 AM, Alex Deucher wrote:
> On Mon, Jan 25, 2016 at 6:35 PM, Nicolai Hähnle wrote:
>> On 24.01.2016 16:09, Samuel Pitoiset wrote:
>>>
>>> Loosely based on tessellation shaders.
>>
>>
>> Do we actually need this? The graphics
Reviewed-by: Marek Olšák
Marek
On Sun, Jan 24, 2016 at 10:09 PM, Samuel Pitoiset
wrote:
> Signed-off-by: Samuel Pitoiset
> ---
> src/mesa/state_tracker/st_atom.c| 2 +-
> src/mesa/state_tracker/st_atom.h
For the series:
Reviewed-by: Marek Olšák
Marek
On Mon, Jan 25, 2016 at 6:00 PM, Nicolai Hähnle wrote:
> From: Nicolai Hähnle
>
> This currently just writes out the name of dump files, which can be useful
> to easily correlate
https://bugs.freedesktop.org/show_bug.cgi?id=54600
Timothy Arceri changed:
What|Removed |Added
Status|NEW |RESOLVED
On 25.01.2016 10:56, Herminio Hernandez, Jr. wrote:
> So I believe I have all the debugging symbols installed. From what I
> am seeing in gdb and valgrind I am still thinking the issue is in the
> glx branch. For gdb I ran it twice and stopped it during it attempt
> to load the r300 driver and in
Would the same thing apply swrast driver? I see glxgears trying to fall back to
it and relieving the same error.
Sent from my iPhone
> On Jan 26, 2016, at 3:31 AM, Michel Dänzer wrote:
>
>> On 25.01.2016 10:56, Herminio Hernandez, Jr. wrote:
>> So I believe I have all the
On Sun, Jan 24, 2016 at 10:09 PM, Samuel Pitoiset
wrote:
> Compute needs a new and different validation path.
>
> Signed-off-by: Samuel Pitoiset
> ---
> src/gallium/include/state_tracker/st_api.h | 8 +
>
Reviewed-by: Marta Lofstedt
> -Original Message-
> From: Ilia Mirkin [mailto:ibmir...@gmail.com] On Behalf Of Ilia Mirkin
> Sent: Friday, January 22, 2016 9:24 PM
> To: mesa-dev@lists.freedesktop.org
> Cc: Lofstedt, Marta; Ilia Mirkin
> Subject: [PATCH v2]
Reviewed-by: Marek Olšák
Marek
On Sun, Jan 24, 2016 at 10:09 PM, Samuel Pitoiset
wrote:
> This introduces pipe_grid_info which contains all information to
> describe a launch_grid call. This will be used to implement indirect
> compute in the
Reviewed-by: Marek Olšák
Marek
On Sun, Jan 24, 2016 at 10:09 PM, Samuel Pitoiset
wrote:
> According to the spec, this also increases the following minimum values:
> - MAX_COMBINED_TEXTURE_IMAGE_UNITS 96 (6*16), was 80
> -
https://bugs.freedesktop.org/show_bug.cgi?id=62046
Timothy Arceri changed:
What|Removed |Added
Summary|Power Point Viewer crashed |[nouveau] Power
> -Original Message-
> From: mesa-dev [mailto:mesa-dev-boun...@lists.freedesktop.org] On
> Behalf Of Ilia Mirkin
> Sent: Tuesday, January 26, 2016 6:01 PM
> To: Marta Lofstedt
> Cc: mesa-dev@lists.freedesktop.org; Marek Olšák
> Subject: Re: [Mesa-dev] [PATCH v5] mesa: enable enums for
>
Reviewed-by: Jordan Justen
On 2016-01-26 15:44:01, Ben Widawsky wrote:
> Cc: Jordan Justen
> Signed-off-by: Ben Widawsky
> ---
> src/mesa/drivers/dri/i965/brw_fs_visitor.cpp | 4 +++-
> 1 file changed, 3
On Tue, 2016-01-26 at 13:33 +1100, Timothy Arceri wrote:
> On Mon, 2016-01-25 at 16:58 -0800, Ian Romanick wrote:
> > On 01/25/2016 04:46 PM, Timothy Arceri wrote:
> > > Previously an empty program would go through the entire
> > > link_shaders() function and we would have to be careful
> > > not
On 01/26/2016 05:59 AM, Timothy Arceri wrote:
On Tue, 2016-01-19 at 07:20 +0100, Samuel Iglesias Gonsálvez wrote:
Commit 781d278 did not restrict consumer_stage only to separate
shader
objects, which is when we don't know if the consumer stage would be a
fragment shader added later. In normal
I am sorry for this.
I am sending up a v5 where I have accounted for that check_extra doesn't
evaluate lazily
FYI I believe that the the EXTRA_EXT_*_TESS tokens may need to be looked over,
since they are bound to cause similar trouble when we enable
oes_tesselation_shader for GLES 3.1.
I
From: Marta Lofstedt
Enable GL_OES_geometry_shader enums for OpenGL ES 3.1.
V4: EXTRA tokens updated according to comments from Ilia Mirkin.
V5: Account for check_extra does not evaluate "or" lazy. Fix issues
with EXTRA_EXT_FB_NO_ATTACH_CS.
Signed-off-by: Marta
Am 26.01.2016 um 08:40 schrieb Michel Dänzer:
From: Michel Dänzer
Failing to do this was resulting in the kernel driver unnecessarily
leaving open the possibility of CPU access to tiled BOs.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93862
(This change
On Tue, Jan 26, 2016 at 5:28 AM, Marek Olšák wrote:
> On Tue, Jan 26, 2016 at 6:17 AM, Alex Deucher wrote:
>> On Mon, Jan 25, 2016 at 6:35 PM, Nicolai Hähnle wrote:
>>> On 24.01.2016 16:09, Samuel Pitoiset wrote:
Loosely
I'd be fine with a new TGSI_FILE_MEMORY which provided options for
shared, global, and local(/private?) memory. I believe the old
TGSI_FILE_RESOURCE had support for these in a hacky way, this would be
the clean way of doing it.
On Tue, Jan 26, 2016 at 5:52 AM, Marek Olšák
From: Karol Herbst
sometimes an application might crash with a message like this:
ERROR: no viable spill candidates left
this is due to a memory corruption wich only manifest when there is another RA
round
this fixes this
Signed-off-by: Karol Herbst
On Tue, Jan 26, 2016 at 2:40 AM, Michel Dänzer wrote:
> From: Michel Dänzer
>
> In particular, AMDGPU_GEM_CREATE_CPU_GTT_USWC can affect even BOs created
> in VRAM if they get evicted to GTT. In general there's no need to
> restrict any of the flags to
On Tue, Jan 26, 2016 at 8:57 AM, Marek Olšák wrote:
> On Tue, Jan 26, 2016 at 2:25 PM, Ilia Mirkin wrote:
>> I'd be fine with a new TGSI_FILE_MEMORY which provided options for
>> shared, global, and local(/private?) memory. I believe the old
>>
On 20/01/16 19:48, Rob Clark wrote:
On Wed, Jan 20, 2016 at 2:44 PM, Ilia Mirkin wrote:
On Wed, Jan 20, 2016 at 2:32 PM, Rob Clark wrote:
From: Rob Clark
Signed-off-by: Rob Clark
---
On 01/25/2016 08:07 PM, Marek Olšák wrote:
On Sun, Jan 24, 2016 at 4:47 PM, Samuel Pitoiset
wrote:
Like other resources, the indirect draw buffer must be unwrapped.
Signed-off-by: Samuel Pitoiset
---
On 01/26/2016 11:30 AM, Marek Olšák wrote:
Functions cso_save_compute_shader & cso_restore_compute_shader, and
the compute_shader_saved variable can be removed. There is no use for
them as far as I can see.
Yeah, because the next patch ("gallium: disable compute shaders for meta
ops") is
On 26.01.2016 06:55, Marek Olšák wrote:
On Mon, Jan 25, 2016 at 10:49 PM, Nicolai Hähnle wrote:
From: Nicolai Hähnle
The new name for the intrinsic was introduced in LLVM r258558.
---
src/gallium/drivers/radeonsi/si_shader.c | 7 ++-
1 file
On 01/25/2016 03:28 PM, Ilia Mirkin wrote:
On Sun, Jan 24, 2016 at 4:09 PM, Samuel Pitoiset
wrote:
Like indirect draw, we need to store a resource and an offset that
needs to be 4 byte aligned. When indirect is used, the size of the
grid (in blocks) is stored with
On 01/26/2016 12:47 PM, Marek Olšák wrote:
On Sun, Jan 24, 2016 at 10:18 PM, Samuel Pitoiset
wrote:
Signed-off-by: Samuel Pitoiset
---
I have forgot this one...
src/gallium/drivers/trace/tr_context.c| 80
On 01/26/2016 02:22 PM, Ilia Mirkin wrote:
On Tue, Jan 26, 2016 at 5:28 AM, Marek Olšák wrote:
On Tue, Jan 26, 2016 at 6:17 AM, Alex Deucher wrote:
On Mon, Jan 25, 2016 at 6:35 PM, Nicolai Hähnle wrote:
On 24.01.2016 16:09,
On 01/25/2016 04:02 PM, Ilia Mirkin wrote:
How about
st/mesa: add compute program dispatch callbacks
or something along those lines. I don't think "state tracker" is the
right term to use.
Fine by me, thanks for the suggestion.
On Sun, Jan 24, 2016 at 4:09 PM, Samuel Pitoiset
On 01/26/2016 02:57 PM, Marek Olšák wrote:
On Tue, Jan 26, 2016 at 2:25 PM, Ilia Mirkin wrote:
I'd be fine with a new TGSI_FILE_MEMORY which provided options for
shared, global, and local(/private?) memory. I believe the old
TGSI_FILE_RESOURCE had support for these in a
On 01/26/2016 05:45 AM, Ilia Mirkin wrote:
On Mon, Jan 25, 2016 at 11:00 PM, Michel Dänzer wrote:
On 26.01.2016 01:17, Nicolai Hähnle wrote:
On 25.01.2016 10:04, Ilia Mirkin wrote:
Yeah so this isn't going to fly. r600/radeonsi both expose
PIPE_CAP_COMPUTE, for clover,
On 25.01.2016 23:45, Ilia Mirkin wrote:
On Mon, Jan 25, 2016 at 11:00 PM, Michel Dänzer wrote:
On 26.01.2016 01:17, Nicolai Hähnle wrote:
On 25.01.2016 10:04, Ilia Mirkin wrote:
Yeah so this isn't going to fly. r600/radeonsi both expose
PIPE_CAP_COMPUTE, for clover, but
On 01/26/2016 11:36 AM, Marek Olšák wrote:
I don't understand this. Can you explain it?
This shader buffer for shared storage is actually a fake buffer. Only
one shared "fake" buffer can be used and it will contain all shared
variables which are defined in the compute shaders. Its size is
Patches 1 to 4 are,
Reviewed-by: Iago Toral Quiroga
I intend to review the remaining patches tomorrow as well if nobody else
beats me to it.
Iago
On Mon, 2016-01-25 at 15:18 -0800, Matt Turner wrote:
> This series adds NIR support for lowering pack/unpack opcodes and
>
From: Nicolai Hähnle
This parameter is equivalent to the corresponding OpenGL implementation
limit which is in texels, not bytes.
---
Based on a discussion in IRC; I plan to push it with the rest of the
series on PBO uploads.
src/gallium/docs/source/screen.rst | 2 +-
Reviewed-by: Ilia Mirkin
On Tue, Jan 26, 2016 at 11:06 AM, Nicolai Hähnle wrote:
> From: Nicolai Hähnle
>
> This parameter is equivalent to the corresponding OpenGL implementation
> limit which is in texels, not bytes.
> ---
>
On Tue, Jan 26, 2016 at 3:48 AM, Marta Lofstedt
wrote:
> From: Marta Lofstedt
>
> Enable GL_OES_geometry_shader enums for OpenGL ES 3.1.
>
> V4: EXTRA tokens updated according to comments from Ilia Mirkin.
>
> V5: Account for check_extra
On Tue, Jan 26, 2016 at 1:47 AM, Tom Stellard wrote:
> On Fri, Jan 22, 2016 at 03:18:12PM +0100, Marek Olšák wrote:
>> From: Marek Olšák
>>
>> v2: account for LDS usage in PS
>> the limit is per SIMD, not per CU
>> ---
>>
On Mon, Jan 11, 2016 at 1:31 AM, Steinar H. Gunderson
wrote:
> On Wed, Dec 09, 2015 at 11:42:59AM +0100, Steinar H. Gunderson wrote:
>>> Might be worth keeping _mesa_ref_sync_object(), even if it's an inline
>>> wrapper around the above. As things get a bit confusing -
Matt Turner writes:
> This series adds NIR support for lowering pack/unpack opcodes and
> switches i965 over to using that. The only place we still use the
> GLSL IR lower_packing_builtins.cpp is for the half-precision functions
> on Sandybridge.
>
> As a result, I get to
I've pushed this series. Thanks.
Marek
On Thu, Jan 21, 2016 at 5:17 PM, Jan Vesely wrote:
> v2: drop inline keyword
> drop radeon_llvm_dispose_kernel_module wrapper
>
> v3: move definitions to .c file
> use in radeonsi
>
> Signed-off-by: Jan Vesely
https://bugs.freedesktop.org/show_bug.cgi?id=89599
--- Comment #9 from Vinson Lee ---
(In reply to Matt Turner from comment #6)
> What do I have to do to reproduce this? Mesa builds with clang (3.7.0)
> fine for me. I've built with clang occasionally for a few years and
>
On Tue, Jan 26, 2016 at 10:05 AM, Eric Anholt wrote:
> Matt Turner writes:
>
>> This series adds NIR support for lowering pack/unpack opcodes and
>> switches i965 over to using that. The only place we still use the
>> GLSL IR lower_packing_builtins.cpp is for
On Tue, Jan 26, 2016 at 3:53 PM, Samuel Pitoiset
wrote:
>
>
> On 01/25/2016 08:07 PM, Marek Olšák wrote:
>>
>> On Sun, Jan 24, 2016 at 4:47 PM, Samuel Pitoiset
>> wrote:
>>>
>>> Like other resources, the indirect draw buffer must be
On Tue, Jan 26, 2016 at 4:21 PM, Samuel Pitoiset
wrote:
>
>
> On 01/26/2016 11:36 AM, Marek Olšák wrote:
>>
>> I don't understand this. Can you explain it?
>
>
> This shader buffer for shared storage is actually a fake buffer. Only one
> shared "fake" buffer can be used
On Tue, Jan 26, 2016 at 3:12 PM, Ilia Mirkin wrote:
> On Tue, Jan 26, 2016 at 8:57 AM, Marek Olšák wrote:
>> On Tue, Jan 26, 2016 at 2:25 PM, Ilia Mirkin wrote:
>>> I'd be fine with a new TGSI_FILE_MEMORY which provided options for
Reviewed-by: Marek Olšák
Marek
On Tue, Jan 26, 2016 at 5:06 PM, Nicolai Hähnle wrote:
> From: Nicolai Hähnle
>
> This parameter is equivalent to the corresponding OpenGL implementation
> limit which is in texels, not bytes.
>
From: Marek Olšák
---
src/gallium/auxiliary/tgsi/tgsi_scan.c | 2 ++
src/gallium/auxiliary/tgsi/tgsi_scan.h | 1 +
2 files changed, 3 insertions(+)
diff --git a/src/gallium/auxiliary/tgsi/tgsi_scan.c
b/src/gallium/auxiliary/tgsi/tgsi_scan.c
index 7a02e27..687fb54 100644
On Tue, Jan 26, 2016 at 3:23 PM, Marek Olšák wrote:
> On Tue, Jan 26, 2016 at 3:12 PM, Ilia Mirkin wrote:
>> On Tue, Jan 26, 2016 at 8:57 AM, Marek Olšák wrote:
>>> On Tue, Jan 26, 2016 at 2:25 PM, Ilia Mirkin
On Wednesday 20 January 2016, Fredrik Höglund wrote:
> On Tuesday 19 January 2016, Nicolai Hähnle wrote:
> > On 19.01.2016 10:45, Fredrik Höglund wrote:
> > > On Tuesday 19 January 2016, Nicolai Hähnle wrote:
> > >>
> > >> On 18.01.2016 18:50, Ilia Mirkin wrote:
> > >>> On Mon, Jan 18, 2016 at
https://bugs.freedesktop.org/show_bug.cgi?id=93878
Bug ID: 93878
Summary: [llvmpipe][softpipe] piglit
arb_gpu_shader_fp64-double-gettransformfeedbackvarying
regression
Product: Mesa
Version: git
From: Timothy Arceri
The last time this was bumped we settled on 4.2.0 because OpenBSD
wasn't willing to ship anything greater than 4.2.1 (as that was the
last GPLv2 licensed version) however they now ship 4.9.3.
As far as I can tell the oldest distro still using a
From: Timothy Arceri
---
src/util/macros.h | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/src/util/macros.h b/src/util/macros.h
index 0c8958f..55d5424 100644
--- a/src/util/macros.h
+++ b/src/util/macros.h
@@ -160,9 +160,7 @@ do {
On Tue, Jan 26, 2016 at 2:04 PM, Timothy Arceri
wrote:
> The last time this was bumped we settled on 4.2.0 because OpenBSD
> wasn't willing to ship anything greater than 4.2.1 (as that was the
> last GPLv2 licensed version) however they now ship 4.9.3.
I suspect
On Tue, Jan 26, 2016 at 07:00:20PM +0100, Marek Olšák wrote:
Might be worth keeping _mesa_ref_sync_object(), even if it's an inline
wrapper around the above. As things get a bit confusing - foo_get vs
foo_unref.
>>> What about _mesa_get_and_ref_sync()?
> Sounds good to me.
Attached
> Ilia Mirkin hat am 26. Januar 2016 um 04:53
> geschrieben:
>
> On Mon, Jan 25, 2016 at 9:57 AM, Karol Herbst wrote:
> > From: Karol Herbst
> >
> > helps some shaders in multiple games
> >
> > total instructions in shared
On Tue, 2016-01-26 at 14:24 -0800, Matt Turner wrote:
> On Tue, Jan 26, 2016 at 2:04 PM, Timothy Arceri
> wrote:
> > The last time this was bumped we settled on 4.2.0 because OpenBSD
> > wasn't willing to ship anything greater than 4.2.1 (as that was the
> > last
Cc: Jordan Justen
Signed-off-by: Ben Widawsky
---
src/mesa/drivers/dri/i965/brw_fs_visitor.cpp | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/src/mesa/drivers/dri/i965/brw_fs_visitor.cpp
On 27 January 2016 at 08:04, Timothy Arceri
wrote:
> From: Timothy Arceri
>
> The last time this was bumped we settled on 4.2.0 because OpenBSD
> wasn't willing to ship anything greater than 4.2.1 (as that was the
> last GPLv2 licensed
Might be a good idea to update the comment above the second hunk. It's very
precise about which bits, and so now wrong.
- Chris
On Wed, Jan 27, 2016 at 12:44 PM, Ben Widawsky
wrote:
> Cc: Jordan Justen
> Signed-off-by: Ben Widawsky
On Tue, Jan 26, 2016 at 9:48 PM, Ilia Mirkin wrote:
> On Tue, Jan 26, 2016 at 3:23 PM, Marek Olšák wrote:
>> On Tue, Jan 26, 2016 at 3:12 PM, Ilia Mirkin wrote:
>>> On Tue, Jan 26, 2016 at 8:57 AM, Marek Olšák
On Tue, Jan 26, 2016 at 7:05 PM, Marek Olšák wrote:
> On Tue, Jan 26, 2016 at 9:48 PM, Ilia Mirkin wrote:
>> On Tue, Jan 26, 2016 at 3:23 PM, Marek Olšák wrote:
>>> On Tue, Jan 26, 2016 at 3:12 PM, Ilia Mirkin
On Tue, Jan 26, 2016 at 3:44 PM, Ben Widawsky
wrote:
> Cc: Jordan Justen
> Signed-off-by: Ben Widawsky
> ---
> src/mesa/drivers/dri/i965/brw_fs_visitor.cpp | 4 +++-
> 1 file changed, 3 insertions(+), 1
On Tue, Jan 26, 2016 at 02:24:34PM -0800, Matt Turner wrote:
> On Tue, Jan 26, 2016 at 2:04 PM, Timothy Arceri
> wrote:
> > The last time this was bumped we settled on 4.2.0 because OpenBSD
> > wasn't willing to ship anything greater than 4.2.1 (as that was the
> >
On Wed, 2016-01-27 at 11:35 +1100, Jonathan Gray wrote:
> On Tue, Jan 26, 2016 at 02:24:34PM -0800, Matt Turner wrote:
> > On Tue, Jan 26, 2016 at 2:04 PM, Timothy Arceri
> > wrote:
> > > The last time this was bumped we settled on 4.2.0 because OpenBSD
> > > wasn't
On Tue, Jan 26, 2016 at 7:35 PM, Jonathan Gray wrote:
> I would be interested to hear specifics as to what post gcc 4.2.1
> extensions/changes people are interested in using.
Lack of C++11 has been a bit of an annoyance in nouveau - I've been
using tr1 versions of things, but
On Tue, Jan 26, 2016 at 07:51:06PM -0500, Ilia Mirkin wrote:
> On Tue, Jan 26, 2016 at 7:35 PM, Jonathan Gray wrote:
> > I would be interested to hear specifics as to what post gcc 4.2.1
> > extensions/changes people are interested in using.
>
> Lack of C++11 has been a bit of an
On 26.01.2016 19:15, Herminio Hernandez Jr. wrote:
> Would the same thing apply swrast driver? I see glxgears trying to
> fall back to it and relieving the same error.
Possibly, though that's a bit weird indeed. Anyway, trace the code
execution (e.g. in gdb) and see.
--
Earthling Michel
https://bugs.freedesktop.org/show_bug.cgi?id=61364
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |FIXED
82 matches
Mail list logo