Ian Romanick writes:
> On 12/23/2013 04:08 PM, Eric Anholt wrote:
>> Noticed by tex3d-maxsize on my next commit to check that our addresses
>> don't overflow.
>
> Should this also go to stable branches?
I'm a little wary of picking this back because of some cases where we
assert that a blit will
On Mit, 2014-01-08 at 18:23 +0100, Marek Olšák wrote:
>
> diff --git a/src/gallium/drivers/radeonsi/si_state.c
> b/src/gallium/drivers/radeonsi/si_state.c
> index 3666a11..ba73401 100644
> --- a/src/gallium/drivers/radeonsi/si_state.c
> +++ b/src/gallium/drivers/radeonsi/si_state.c
[...]
> @@ -21
https://bugs.freedesktop.org/show_bug.cgi?id=70410
Krzysztof A. Sobiecki changed:
What|Removed |Added
CC||sob...@gmail.com
--
You are rec
On Wed, Jan 8, 2014 at 4:37 PM, Brian Paul wrote:
> If a channel has zero bits it's not signed.
>
> v2: also check for luminance and intensity format bits. Bruce
> Merry's proposed piglit test hits the luminance case.
>
> Bugzilla: http://bugs.freedesktop.org/show_bug.cgi?id=73096
> Cc: 10.0
> -
Reviewed-by: Matt Turner
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
https://bugs.freedesktop.org/show_bug.cgi?id=70410
--- Comment #13 from Krzysztof A. Sobiecki ---
Created attachment 91725
--> https://bugs.freedesktop.org/attachment.cgi?id=91725&action=edit
Another patch, with newline hack
llvm-config --ldflags:
-L/usr/lib/llvm-3.5/lib
Needed libraries are
I doubt the swrast-based drivers will ever support GS.
Signed-off-by: Brian Paul
---
src/mesa/main/extensions.c |4
1 file changed, 4 deletions(-)
diff --git a/src/mesa/main/extensions.c b/src/mesa/main/extensions.c
index efda548..89d4793 100644
--- a/src/mesa/main/extensions.c
+++ b/s
We weren't handling the LUMINANCE_SNORM, LUMINANCE_ALPHA_SNORM and
INTENSITY_SNORM cases. Note that adding these cases here does not
require a driver to support rendering to these surface types. If
the driver can't do it we'll report an incomplete framebuffer.
NVIDIA doesn't support GL_EXT_textu
If a channel has zero bits it's not signed.
v2: also check for luminance and intensity format bits. Bruce
Merry's proposed piglit test hits the luminance case.
Bugzilla: http://bugs.freedesktop.org/show_bug.cgi?id=73096
Cc: 10.0
---
src/mesa/main/get.c | 37 ++
> + OUT_BATCH(0);
> + ADVANCE_BATCH();
> + } else {
> + BEGIN_BATCH(4);
> + OUT_BATCH(_3DSTATE_PIPE_CONTROL | flags | (4 - 2));
If the PRM is to believed, then ILK has two of its flag bits in dw1
[Stall at scoreboard, and the nonfunctional depth cache flush
inhibit]; it looks
https://bugs.freedesktop.org/show_bug.cgi?id=70410
--- Comment #12 from Armin K ---
Oh, I'm sorry for multiple posts. Seems that I've downgraded to llvm-3.4 but I
was using 3.5 snapshot and that's why --ldflags works for me as it is - there's
no --system-libs option. You could easily fill a bug f
https://bugs.freedesktop.org/show_bug.cgi?id=70410
--- Comment #11 from Armin K ---
llvm-config --ldflags
-L/usr/lib -lz -lpthread -lffi -lcurses -ldl -lm
There's also this command which doesn't add new line, at least not here.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=70410
--- Comment #10 from Armin K ---
Same here, but I use llvm-3.4 release. You could easily strip the new line
using sed or whatever.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=70410
--- Comment #9 from Krzysztof A. Sobiecki ---
(In reply to comment #8)
> llvm-config now has this parameter:
>
> --system-libs System Libraries needed to link against LLVM components.
>
> And on my system it outputs:
>
> -lz -lpthread
On 01/08/2014 01:43 PM, Matt Turner wrote:
This flag was really just a proxy for determining whether the backend
was vector (AOS) or scalar (SOA). It will be used to apply a future
optimization only for vector backends.
---
src/glsl/glsl_parser_extras.cpp | 2 +-
src/mesa/drivers/
Series Reviewed-by: Jordan Justen
On Wed, Jan 8, 2014 at 1:11 PM, Chris Forbes wrote:
> This is not observed to actually fix anything, but the PRM says this
> field must be zero for other surface types.
>
> Signed-off-by: Chris Forbes
> ---
> src/mesa/drivers/dri/i965/gen7_wm_surface_state.c |
We have this "edge rule" state for points. It has 4 bits called Left,
Right, Top, Bottom. 1 means "in", 0 means "out". It probably
determines what happens if a primitive edge intersects a pixel or
something like that. We set Left=0, Right=1, Top=0, Bottom=1.
We also have this state:
ROUND_MODE
C
On Wed, Jan 8, 2014 at 1:00 PM, Kenneth Graunke wrote:
> On 01/08/2014 12:43 PM, Matt Turner wrote:
>> total instructions in shared programs: 1500212 -> 1500153 (-0.00%)
>> instructions in affected programs: 1 -> 17718 (-0.33%)
>> ---
>> src/mesa/drivers/dri/i965/brw_dead_control_flow.cpp
On 01/08/2014 11:20 AM, Paul Berry wrote:
> These are replaced with
> ctx->Const.Program[MESA_SHADER_{VERTEX,FRAGMENT,GEOMETRY}]. In
> patches to follow, this will allow us to replace a lot of ad-hoc logic
> with a variable index into the array.
>
> With the exception of the changes to mtypes.h,
This is not observed to actually fix anything, but the PRM says this
field must be zero for other surface types.
Signed-off-by: Chris Forbes
---
src/mesa/drivers/dri/i965/gen7_wm_surface_state.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/
Previously this was missing many interesting fields. Having them decoded
makes debugging views much easier.
Signed-off-by: Chris Forbes
---
src/mesa/drivers/dri/i965/brw_state_dump.c | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/src/mesa/drivers/dri/i965
Signed-off-by: Chris Forbes
---
src/mesa/drivers/dri/i965/brw_defines.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/mesa/drivers/dri/i965/brw_defines.h
b/src/mesa/drivers/dri/i965/brw_defines.h
index 0fc24a7..358a404 100644
--- a/src/mesa/drivers/dri/i965/brw_defines.h
+++ b/src/me
On 01/08/2014 12:43 PM, Matt Turner wrote:
> total instructions in shared programs: 1500212 -> 1500153 (-0.00%)
> instructions in affected programs: 1 -> 17718 (-0.33%)
> ---
> src/mesa/drivers/dri/i965/brw_dead_control_flow.cpp | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
https://bugs.freedesktop.org/show_bug.cgi?id=70410
--- Comment #8 from Armin K ---
llvm-config now has this parameter:
--system-libs System Libraries needed to link against LLVM components.
And on my system it outputs:
-lz -lpthread -lffi -lcurses -ldl -lm
This should be added to LDFL
https://bugs.freedesktop.org/show_bug.cgi?id=70410
Alexander Tsoy changed:
What|Removed |Added
CC||alexan...@tsoy.me
--
You are receiving
total instructions in shared programs: 1500212 -> 1500153 (-0.00%)
instructions in affected programs: 1 -> 17718 (-0.33%)
---
src/mesa/drivers/dri/i965/brw_dead_control_flow.cpp | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_dead_con
Reduces vertex shader instruction counts in DOTA2 by 6.42%, L4D2 by
4.61%, and CS:GO by 5.71%.
total instructions in shared programs: 1500153 -> 1498191 (-0.13%)
instructions in affected programs: 59919 -> 57957 (-3.27%)
---
src/glsl/Makefile.sources | 1 +
src/glsl/glsl_parser_extras
This flag was really just a proxy for determining whether the backend
was vector (AOS) or scalar (SOA). It will be used to apply a future
optimization only for vector backends.
---
src/glsl/glsl_parser_extras.cpp | 2 +-
src/mesa/drivers/dri/i965/brw_context.c | 2 +-
src/mesa/dr
---
src/mesa/drivers/dri/i965/brw_context.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/mesa/drivers/dri/i965/brw_context.c
b/src/mesa/drivers/dri/i965/brw_context.c
index da34e3d..3da328a 100644
--- a/src/mesa/drivers/dri/i965/brw_context.c
+++ b/src/mesa/drivers/dri/i965/brw_context
Only implemented for ir_swizzles currently, but perhaps will be useful
for other IR types in the future.
---
src/glsl/ir.h | 14 +--
src/glsl/ir_equals.cpp | 63 +++---
2 files changed, 41 insertions(+), 36 deletions(-)
diff --git a/src
On 08/01/14 19:20, Paul Berry wrote:
> Suggested-by: Brian Paul
> ---
> src/mesa/program/ir_to_mesa.cpp| 17 +
> src/mesa/program/program.h | 18 ++
> src/mesa/state_tracker/st_glsl_to_tgsi.cpp | 40
> +++---
> 3 files c
On 01/08/2014 12:51 PM, Marek Olšák wrote:
On Wed, Jan 8, 2014 at 8:21 PM, Brian Paul wrote:
On 01/08/2014 10:23 AM, Marek Olšák wrote:
From: Marek Olšák
An example why it is required:
Let's say there's a fragment shader writing to gl_FragData[0..1].
The user calls: glDrawBuffe
Am 08.01.2014 19:48, schrieb Marek Olšák:
> On Wed, Jan 8, 2014 at 7:31 PM, Roland Scheidegger wrote:
>> Am 08.01.2014 19:12, schrieb Jose Fonseca:
>>>
>>>
>>> - Original Message -
Am 08.01.2014 18:27, schrieb jfons...@vmware.com:
> From: José Fonseca
>
> Commit eda21d2a3
On Wed, Jan 8, 2014 at 8:21 PM, Brian Paul wrote:
> On 01/08/2014 10:23 AM, Marek Olšák wrote:
>>
>> From: Marek Olšák
>>
>> An example why it is required:
>>
>> Let's say there's a fragment shader writing to gl_FragData[0..1].
>> The user calls: glDrawBuffers(2, {GL_NONE, GL_COLOR_ATTA
On 01/08/2014 12:20 PM, Paul Berry wrote:
These are replaced with
ctx->Const.Program[MESA_SHADER_{VERTEX,FRAGMENT,GEOMETRY}]. In
patches to follow, this will allow us to replace a lot of ad-hoc logic
with a variable index into the array.
With the exception of the changes to mtypes.h, this patch
On Wed, Jan 8, 2014 at 7:54 PM, Lauri Kasanen wrote:
> On Wed, 8 Jan 2014 19:03:53 +0100
> Marek Olšák wrote:
>
>> On Wed, Jan 8, 2014 at 6:21 PM, Lauri Kasanen wrote:
>> > On Wed, 8 Jan 2014 15:54:04 +0100
>> > Marek Olšák wrote:
>> >> It's not accurate at all, it's actually pretty random. The
On 01/08/2014 10:23 AM, Marek Olšák wrote:
From: Marek Olšák
---
src/gallium/auxiliary/util/u_clear.h | 4
src/gallium/auxiliary/util/u_framebuffer.c | 3 +++
2 files changed, 7 insertions(+)
diff --git a/src/gallium/auxiliary/util/u_clear.h
b/src/gallium/auxiliary/util/u_clear
On 01/08/2014 10:23 AM, Marek Olšák wrote:
From: Marek Olšák
An example why it is required:
Let's say there's a fragment shader writing to gl_FragData[0..1].
The user calls: glDrawBuffers(2, {GL_NONE, GL_COLOR_ATTACHMENT0});
That means gl_FragData[0] is unused and gl_FragData[1
Suggested-by: Brian Paul
---
src/mesa/program/ir_to_mesa.cpp| 17 +
src/mesa/program/program.h | 18 ++
src/mesa/state_tracker/st_glsl_to_tgsi.cpp | 40 +++---
3 files changed, 39 insertions(+), 36 deletions(-)
diff --gi
---
src/glsl/ast_to_hir.cpp| 13 +
src/glsl/link_atomics.cpp | 16 ++--
src/glsl/link_varyings.cpp | 32 ++--
src/glsl/linker.cpp| 43 ---
4 files changed, 17 insertions(+), 87 deletions(-)
di
This allows the caller to execute it in a loop rather than
hand-rolling a separate call for each stage.
---
src/mesa/main/context.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/src/mesa/main/context.c b/src/mesa/main/context.c
index cfebbd2..0b8fb94 100644
---
src/mesa/program/program.c | 17 ++---
1 file changed, 2 insertions(+), 15 deletions(-)
diff --git a/src/mesa/program/program.c b/src/mesa/program/program.c
index df4d75f..3c19e8c 100644
--- a/src/mesa/program/program.c
+++ b/src/mesa/program/program.c
@@ -896,21 +896,8 @@ _mesa_v
On 01/08/2014 10:23 AM, Marek Olšák wrote:
From: Marek Olšák
---
src/mesa/main/clear.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/src/mesa/main/clear.c b/src/mesa/main/clear.c
index f0b525f..fd5bb35 100644
--- a/src/mesa/main/clear.c
+++ b/src/mesa/main/clear.c
On 01/08/2014 10:30 AM, jfons...@vmware.com wrote:
From: José Fonseca
This example is very useful to understand the rasterization of lines.
And with this change, points too.
Adding a key / command-line option to switch modes is left for a future
opportunity though.
For both:
Reviewed-by: Bri
On Wed, 8 Jan 2014 19:03:53 +0100
Marek Olšák wrote:
> On Wed, Jan 8, 2014 at 6:21 PM, Lauri Kasanen wrote:
> > On Wed, 8 Jan 2014 15:54:04 +0100
> > Marek Olšák wrote:
> >> It's not accurate at all, it's actually pretty random. The stats
> >> should not be called "num_reads" and "num_writes",
On Wed, Jan 8, 2014 at 7:31 PM, Roland Scheidegger wrote:
> Am 08.01.2014 19:12, schrieb Jose Fonseca:
>>
>>
>> - Original Message -
>>> Am 08.01.2014 18:27, schrieb jfons...@vmware.com:
From: José Fonseca
Commit eda21d2a3010d9fc5a68b55a843c5e44b2abf8dd fixed the rasterizat
Am 08.01.2014 19:12, schrieb Jose Fonseca:
>
>
> - Original Message -
>> Am 08.01.2014 18:27, schrieb jfons...@vmware.com:
>>> From: José Fonseca
>>>
>>> Commit eda21d2a3010d9fc5a68b55a843c5e44b2abf8dd fixed the rasterization
>>> of points for Direct3D but ended up breaking the rasteriza
- Original Message -
> Am 08.01.2014 18:27, schrieb jfons...@vmware.com:
> > From: José Fonseca
> >
> > Commit eda21d2a3010d9fc5a68b55a843c5e44b2abf8dd fixed the rasterization
> > of points for Direct3D but ended up breaking the rasterization of OpenGL
> > non-sprite points, in particul
On Wed, Jan 8, 2014 at 6:38 PM, Lauri Kasanen wrote:
> On Wed, 8 Jan 2014 15:56:33 +0200
> Lauri Kasanen wrote:
>
>> On Wed, 8 Jan 2014 12:03:12 +0100
>> Marek Olšák wrote:
>> > Also, last_cpu_time will be wrong anyway, because the driver may call
>> > the buffer_map function only once per buffe
- Original Message -
> On Wed, Jan 8, 2014 at 6:27 PM, wrote:
> > }
> > -
> > +
> > + if (0) {
> > + debug_printf(" bbox: (%i, %i) - (%i, %i)\n",
> > + bbox.x0, bbox.y0,
> > + bbox.x1, bbox.y1);
> > + }
> > +
> > if (!u_rect_test_inter
Am 08.01.2014 18:27, schrieb jfons...@vmware.com:
> From: José Fonseca
>
> Commit eda21d2a3010d9fc5a68b55a843c5e44b2abf8dd fixed the rasterization
> of points for Direct3D but ended up breaking the rasterization of OpenGL
> non-sprite points, in particular conform's pntrast.c test.
>
> The only
- Original Message -
> On Wed, Jan 8, 2014 at 6:30 PM, wrote:
> > From: José Fonseca
> >
> > This example is very useful to understand the rasterization of lines.
> > And with this change, points too.
> >
> > Adding a key / command-line option to switch modes is left for a future
> > o
On Wed, Jan 8, 2014 at 6:30 PM, wrote:
> From: José Fonseca
>
> This example is very useful to understand the rasterization of lines.
> And with this change, points too.
>
> Adding a key / command-line option to switch modes is left for a future
> opportunity though.
> ---
> src/demos/pixeltest
On Wed, Jan 8, 2014 at 6:21 PM, Lauri Kasanen wrote:
> On Wed, 8 Jan 2014 15:54:04 +0100
> Marek Olšák wrote:
>
>> > On Wed, 8 Jan 2014 12:03:12 +0100
>> > Marek Olšák wrote:
>> >> Why don't you just set the statistics once per CS in
>> >> radeon_drm_cs_flush? I don't see a value in doing it in
On Wed, Jan 8, 2014 at 6:27 PM, wrote:
> }
> -
> +
> + if (0) {
> + debug_printf(" bbox: (%i, %i) - (%i, %i)\n",
> + bbox.x0, bbox.y0,
> + bbox.x1, bbox.y1);
> + }
> +
> if (!u_rect_test_intersection(&setup->draw_regions[viewport_index],
> &b
On Wed, 8 Jan 2014 15:56:33 +0200
Lauri Kasanen wrote:
> On Wed, 8 Jan 2014 12:03:12 +0100
> Marek Olšák wrote:
> > Also, last_cpu_time will be wrong anyway, because the driver may call
> > the buffer_map function only once per buffer, e.g. at buffer creation.
> > It's not a rule, but it happens
From: José Fonseca
Commit eda21d2a3010d9fc5a68b55a843c5e44b2abf8dd fixed the rasterization
of points for Direct3D but ended up breaking the rasterization of OpenGL
non-sprite points, in particular conform's pntrast.c test.
The only way to get both working is to properly honour
pipe_rasterizer::p
From: José Fonseca
This example is very useful to understand the rasterization of lines.
And with this change, points too.
Adding a key / command-line option to switch modes is left for a future
opportunity though.
---
src/demos/pixeltest.c | 109
From: José Fonseca
Not really used/necessary.
---
src/demos/pixeltest.c | 113 +++---
1 file changed, 52 insertions(+), 61 deletions(-)
diff --git a/src/demos/pixeltest.c b/src/demos/pixeltest.c
index e9b95b8..0898290 100644
--- a/src/demos/pixeltest.
From: Marek Olšák
---
src/gallium/drivers/r600/evergreen_state.c | 59 ++
src/gallium/drivers/r600/r600_blit.c | 23 ++--
2 files changed, 54 insertions(+), 28 deletions(-)
diff --git a/src/gallium/drivers/r600/evergreen_state.c
b/src/gallium/drivers/r
From: Marek Olšák
---
src/gallium/drivers/r600/r600_state.c | 120 --
1 file changed, 55 insertions(+), 65 deletions(-)
diff --git a/src/gallium/drivers/r600/r600_state.c
b/src/gallium/drivers/r600/r600_state.c
index f4ceb4a..a0d527b 100644
--- a/src/gallium/dri
From: Marek Olšák
---
src/gallium/auxiliary/util/u_clear.h | 4
src/gallium/auxiliary/util/u_framebuffer.c | 3 +++
2 files changed, 7 insertions(+)
diff --git a/src/gallium/auxiliary/util/u_clear.h
b/src/gallium/auxiliary/util/u_clear.h
index 75047c1..db0b9b3 100644
--- a/src/galli
From: Marek Olšák
also restructure the code
---
src/gallium/drivers/r600/r600_blit.c | 69
1 file changed, 31 insertions(+), 38 deletions(-)
diff --git a/src/gallium/drivers/r600/r600_blit.c
b/src/gallium/drivers/r600/r600_blit.c
index 2b86138..de8ff4f 1006
From: Marek Olšák
---
src/gallium/drivers/radeonsi/si_state.c | 20 +++-
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/src/gallium/drivers/radeonsi/si_state.c
b/src/gallium/drivers/radeonsi/si_state.c
index 3666a11..ba73401 100644
--- a/src/gallium/drivers/radeo
From: Marek Olšák
An example why it is required:
Let's say there's a fragment shader writing to gl_FragData[0..1].
The user calls: glDrawBuffers(2, {GL_NONE, GL_COLOR_ATTACHMENT0});
That means gl_FragData[0] is unused and gl_FragData[1] is written
to GL_COLOR_ATTACHMENT0.
st/me
From: Marek Olšák
---
src/mesa/main/clear.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/src/mesa/main/clear.c b/src/mesa/main/clear.c
index f0b525f..fd5bb35 100644
--- a/src/mesa/main/clear.c
+++ b/src/mesa/main/clear.c
@@ -179,7 +179,11 @@ _mesa_Clear( GLbitfield ma
On Wed, 8 Jan 2014 15:54:04 +0100
Marek Olšák wrote:
> > On Wed, 8 Jan 2014 12:03:12 +0100
> > Marek Olšák wrote:
> >> Why don't you just set the statistics once per CS in
> >> radeon_drm_cs_flush? I don't see a value in doing it in every function
> >> that sets the resources.
> >
> > It's the o
On Wed, Jan 8, 2014 at 8:23 PM, Steven Newbury wrote:
> On Fri, 2014-01-03 at 13:14 +0800, Chia-I Wu wrote:
>> On Thu, Jan 2, 2014 at 10:39 PM, Steven Newbury
>> wrote:
>> > Forgot to add signed-off-by...
>> >
>> > In trying to get gallium-nine working with the ilo Gallium driver I
>> > noticed
On 7 January 2014 16:58, Chad Versace wrote:
> Unconditionally set brw->need_workaround_flush at the top of gen6 blorp
> state emission.
>
> The art of emitting workaround flushes on Sandybridge is mysterious and
> not fully understood. Ken and I believe that
> intel_emit_post_sync_nonzero_flush(
On 7 January 2014 15:06, Brian Paul wrote:
> On 01/07/2014 03:13 PM, Paul Berry wrote:
>
>> diff --git a/src/glsl/glsl_parser_extras.h b/src/glsl/glsl_parser_extras.h
>> index 0e281ae..ecf832f 100644
>> --- a/src/glsl/glsl_parser_extras.h
>> +++ b/src/glsl/glsl_parser_extras.h
>> @@ -165,7 +165,7
On 7 January 2014 15:25, Kenneth Graunke wrote:
> On 01/07/2014 02:13 PM, Paul Berry wrote:
> > This reduces confusion since gl_shader::Type is sometimes
> > GL_SHADER_PROGRAM_MESA but is more frequently
> > GL_SHADER_{VERTEX,GEOMETRY,FRAGMENT}. It also has the advantage that
> > when switching
On 01/08/2014 01:16 AM, Thomas Sondergaard wrote:
On 08-01-2014 00:11, Brian Paul wrote:
On 01/07/2014 03:30 PM, Ian Romanick wrote:
On 01/07/2014 02:22 PM, Thomas Sondergaard wrote:
On 2014-01-07 23:05, Ian Romanick wrote:
On 01/07/2014 12:31 PM, Thomas Sondergaard wrote:
This small rearran
On Wed, Jan 8, 2014 at 2:56 PM, Lauri Kasanen wrote:
> On Wed, 8 Jan 2014 12:03:12 +0100
> Marek Olšák wrote:
>
>> On Tue, Jan 7, 2014 at 7:14 PM, Lauri Kasanen wrote:
>> > These will be used later on for optimizing the VRAM placement.
>> >
>> > No measurable overhead (glxgears, torcs).
>> >
>>
On 08-01-2014 00:11, Brian Paul wrote:
On 01/07/2014 03:30 PM, Ian Romanick wrote:
On 01/07/2014 02:22 PM, Thomas Sondergaard wrote:
On 2014-01-07 23:05, Ian Romanick wrote:
On 01/07/2014 12:31 PM, Thomas Sondergaard wrote:
This small rearrangement avoids MSVC 2013 ICE. Also, this should be a
On Wed, 8 Jan 2014 12:03:12 +0100
Marek Olšák wrote:
> On Tue, Jan 7, 2014 at 7:14 PM, Lauri Kasanen wrote:
> > These will be used later on for optimizing the VRAM placement.
> >
> > No measurable overhead (glxgears, torcs).
> >
> > v2: Get accurate stats by taking dirty_masks into account
>
>
dri2_add_config makes decisions based on NOK_texture_from_pixmap so
it needs to be enabled before calling dri2_add_configs_for_visuals.
Signed-off-by: Tapani Pälli
---
src/egl/drivers/dri2/platform_x11.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/src/egl/driv
yInverted is used by EGL_NOK_texture_from_pixmap to indicate that
window system rendering is y-inverted compared to OpenGL texture
representation. This extension is only known to be used with X11
window system where sane default is GL_TRUE.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=73
https://bugs.freedesktop.org/show_bug.cgi?id=73371
Tapani Pälli changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|mesa-dev@list
On Fri, 2014-01-03 at 13:14 +0800, Chia-I Wu wrote:
> On Thu, Jan 2, 2014 at 10:39 PM, Steven Newbury wrote:
> > Forgot to add signed-off-by...
> >
> > In trying to get gallium-nine working with the ilo Gallium driver I
> > noticed there's no ilo pipe-loader driver being built.
> >
> > This patch
https://bugs.freedesktop.org/show_bug.cgi?id=73371
--- Comment #6 from Carsten Haitzler ---
indeed. and thus why we noticed... as we had it right without the extension
assuming the default of inversion... :) once we actually ASKED for it... it
told us the wrong thing. fyi we already handled inver
https://bugs.freedesktop.org/show_bug.cgi?id=73371
--- Comment #5 from Tapani Pälli ---
(In reply to comment #4)
> but it is wrong - it IS inverted. without the extension at all the default
> assumption is to assume inversion. it all worked fine until we added support
> for this extension and the
https://bugs.freedesktop.org/show_bug.cgi?id=73371
--- Comment #4 from Carsten Haitzler ---
but it is wrong - it IS inverted. without the extension at all the default
assumption is to assume inversion. it all worked fine until we added support
for this extension and then everything flipped on mes
https://bugs.freedesktop.org/show_bug.cgi?id=73392
Priority: medium
Bug ID: 73392
Assignee: mesa-dev@lists.freedesktop.org
Summary: GLX context memory leak if context was bound to
drawable on thread exit
Severity: normal
On Tue, Jan 7, 2014 at 7:14 PM, Lauri Kasanen wrote:
> These will be used later on for optimizing the VRAM placement.
>
> No measurable overhead (glxgears, torcs).
>
> v2: Get accurate stats by taking dirty_masks into account
Why don't you just set the statistics once per CS in
radeon_drm_cs_flus
84 matches
Mail list logo
