On 02/04/16 01:52, John Sheu wrote:
> This removes a hack introduced in 1999 in the first version of
> fakeglx.c, with the comment:
>
> /* XXX revisit this after 3.0 is finished. */
>
> Mesa 4.0 was released in 2001. It is now 2016, and Mesa 11.0 was
> released last year.
Probably it would be g
Assuming that the comments on the previous patch would be updated:
Reviewed-by: Alejandro Piñeiro
On 02/04/16 01:52, John Sheu wrote:
> The vishandle member of XMesaVisualInfo is used to support the
> comparison of XVisualInfo instances by pointer value, in
> find_glx_visual(). The comparison h
Reviewed-by: Alejandro Piñeiro
On 02/04/16 01:52, John Sheu wrote:
> ---
> src/mesa/drivers/x11/fakeglx.c | 29 +
> 1 file changed, 21 insertions(+), 8 deletions(-)
>
> diff --git a/src/mesa/drivers/x11/fakeglx.c b/src/mesa/drivers/x11/fakeglx.c
> index 208fc5bb..508d
On 04/04/16 08:11, Alejandro Piñeiro wrote:
> On 02/04/16 01:52, John Sheu wrote:
>> XMesaVisual.vishandle is being unconditionally overwritten every time
>> glXChooseVisual/glXGetVisualFromFBConfig returns a new XVisualInfo
>> instance, causing a memory leak.
>> ---
>> src/mesa/drivers/x11/fakegl
On Sunday, April 3, 2016 9:16:29 PM PDT Timothy Arceri wrote:
> ---
> src/compiler/glsl/linker.cpp | 70
> 1 file changed, 70 deletions(-)
Hrm?
glsl: remove unused buffer block splitting function
But it /is/ used...you just delete the use here.
On Sunday, April 3, 2016 9:16:28 PM PDT Timothy Arceri wrote:
[snip]
> @@ -3295,8 +3296,8 @@ should_add_buffer_variable(struct gl_shader_program
*shProg,
> if (type != GL_BUFFER_VARIABLE)
>return true;
>
> - for (unsigned i = 0; i < shProg->NumBufferInterfaceBlocks; i++) {
> -
https://bugs.freedesktop.org/show_bug.cgi?id=94805
Kenneth Graunke changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On 02/04/16 01:52, John Sheu wrote:
> XMesaVisual.vishandle is being unconditionally overwritten every time
> glXChooseVisual/glXGetVisualFromFBConfig returns a new XVisualInfo
> instance, causing a memory leak.
> ---
> src/mesa/drivers/x11/fakeglx.c | 26 --
> 1 file chang
The bblock_t::prev/prev_const/next/next_const API returns bblock_t
pointers, rather than exec_nodes. So it's a bit surprising.
Signed-off-by: Kenneth Graunke
---
src/mesa/drivers/dri/i965/brw_cfg.h | 12
src/mesa/drivers/dri/i965/brw_shader.cpp | 2 +-
2 files changed, 13 ins
There may not be a previous block. In this case, there's no real work
to do, so just continue on to the next one.
v2: Update for bblock->prev() API change.
Signed-off-by: Kenneth Graunke
---
src/mesa/drivers/dri/i965/brw_dead_control_flow.cpp | 4
1 file changed, 4 insertions(+)
diff --g
On Apr 3, 2016 7:51 PM, "Kenneth Graunke" wrote:
>
> %ld and %lu aren't the right format specifiers for int64_t and uint64_t
> on 32-bit (x86) systems. They're %zu on Linux and %Iu on Windows.
>
> Use the standard C99 macros in hopes that they work everywhere.
>
> Signed-off-by: Kenneth Graunke
Patches 1-5, 8 & 10 are,
Reviewed-by: Edward O'Callaghan
On 2016-04-04 12:15, Dave Airlie wrote:
Okay I've taken Tobias' last work in progress, cleaned it up a bit,
move the rename out into a separate patch, reordered things slightly.
I've dropped the separate passes, I think nearly all hw op
On Sunday, April 3, 2016 9:34:05 PM PDT Timothy Arceri wrote:
> On Sun, 2016-04-03 at 01:37 -0700, Kenneth Graunke wrote:
> > Consider the case of linking a program with both a vertex and
> > fragment
> > shader. The VS may compute output varyings that are intended for
> > transform feedback, and
%ld and %lu aren't the right format specifiers for int64_t and uint64_t
on 32-bit (x86) systems. They're %zu on Linux and %Iu on Windows.
Use the standard C99 macros in hopes that they work everywhere.
Signed-off-by: Kenneth Graunke
---
src/compiler/nir/nir_search.c | 5 +++--
1 file changed,
On Mon, 2016-04-04 at 12:15 +1000, Dave Airlie wrote:
> From: Tobias Klausmann
>
> Signed-off-by: Tobias Klausmann >
> ---
> src/compiler/glsl/ast_to_hir.cpp | 14 +++
> src/compiler/glsl/builtin_variables.cpp | 11 ++-
> src/compiler/glsl/glcpp/glcpp-parse.y| 3 +
>
On Sun, Apr 3, 2016 at 10:15 PM, Dave Airlie wrote:
> From: Tobias Klausmann
>
> This enables ARB_cull_distance.
This isn't enough - something needs to lower the CULLDIST into
CLIPDIST (or some combined thing). Ideally they'd both just come in as
CLIPDIST and the property would let us know where
From: Tobias Klausmann
Signed-off-by: Tobias Klausmann
---
src/mesa/state_tracker/st_extensions.c | 1 +
src/mesa/state_tracker/st_program.c| 40 ++
2 files changed, 41 insertions(+)
diff --git a/src/mesa/state_tracker/st_extensions.c
b/src/mesa/state_trac
From: Tobias Klausmann
This will come in handy when we want to lower gl_CullDistance into
gl_CullDistanceMESA.
[airlied: drop separate APIs for clip/cull - just use single API
to call both passes.]
Signed-off-by: Tobias Klausmann
---
src/compiler/glsl/ir_optimization.h | 3 +-
src/compiler
From: Tobias Klausmann
Signed-off-by: Tobias Klausmann
---
src/compiler/glsl/linker.cpp | 2 +-
src/compiler/glsl_types.cpp | 8
src/compiler/glsl_types.h| 10 --
3 files changed, 13 insertions(+), 7 deletions(-)
diff --git a/src/compiler/glsl/linker.cpp b/src/compiler/
From: Tobias Klausmann
Signed-off-by: Tobias Klausmann
---
src/mapi/glapi/gen/gl_API.xml | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/src/mapi/glapi/gen/gl_API.xml b/src/mapi/glapi/gen/gl_API.xml
index 8b49f91..024acfd 100644
--- a/src/mapi/glapi/gen/gl_API.xml
+++
From: Tobias Klausmann
Signed-off-by: Tobias Klausmann
---
src/gallium/drivers/nouveau/codegen/nv50_ir_from_tgsi.cpp | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/gallium/drivers/nouveau/codegen/nv50_ir_from_tgsi.cpp
b/src/gallium/drivers/nouveau/codegen/nv50_ir_from_tgsi.cpp
inde
From: Tobias Klausmann
Signed-off-by: Tobias Klausmann
---
src/gallium/drivers/llvmpipe/lp_screen.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gallium/drivers/llvmpipe/lp_screen.c
b/src/gallium/drivers/llvmpipe/lp_screen.c
index 4665487..eb00e7c 100644
--- a/src/ga
From: Tobias Klausmann
This lets us safely enable or disable the extension as needed
Signed-off-by: Tobias Klausmann
---
src/gallium/docs/source/screen.rst | 2 ++
src/gallium/drivers/freedreno/freedreno_screen.c | 1 +
src/gallium/drivers/i915/i915_screen.c | 1 +
src/
From: Dave Airlie
This just renames the file in anticipation of adding cull lowering.
Signed-off-by: Dave Airlie
---
src/compiler/Makefile.sources | 2 +-
src/compiler/glsl/Makefile.sources| 2 +-
src/compiler/glsl/lower_clip_distance.cpp | 574 -
From: Tobias Klausmann
Signed-off-by: Tobias Klausmann
---
src/compiler/glsl/ast_to_hir.cpp | 14 +++
src/compiler/glsl/builtin_variables.cpp | 11 ++-
src/compiler/glsl/glcpp/glcpp-parse.y| 3 +
src/compiler/glsl/glsl_parser_extras.cpp | 1 +
src/compiler/gls
From: Tobias Klausmann
Signed-off-by: Tobias Klausmann
---
src/mesa/program/prog_print.c | 4
1 file changed, 4 insertions(+)
diff --git a/src/mesa/program/prog_print.c b/src/mesa/program/prog_print.c
index 08381b4..755d644 100644
--- a/src/mesa/program/prog_print.c
+++ b/src/mesa/program
From: Tobias Klausmann
airlied:
v2: rename LowerClipDistance to LowerCombinedClipCullDistnace.
I don't think we want any other behaviour with any current hw.
Signed-off-by: Tobias Klausmann
---
src/compiler/glsl/link_varyings.cpp | 2 +-
src/compiler/glsl/linker.cpp | 2 +-
From: Tobias Klausmann
This enables ARB_cull_distance.
Signed-off-by: Tobias Klausmann
---
docs/GL3.txt| 2 +-
src/gallium/drivers/nouveau/nvc0/nvc0_program.c | 2 ++
src/gallium/drivers/nouveau/nvc0/nvc0_program.h | 1 +
src/gallium/drivers/nouveau/nvc0/nvc
Okay I've taken Tobias' last work in progress, cleaned it up a bit,
move the rename out into a separate patch, reordered things slightly.
I've dropped the separate passes, I think nearly all hw operates the
same, I do wonder why we even have this as an option, since at least
965/gallium always req
Signed-off-by: Ilia Mirkin
---
src/mesa/main/bufferobj.c | 3 ++-
src/mesa/vbo/vbo_exec_array.c | 8
2 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/src/mesa/main/bufferobj.c b/src/mesa/main/bufferobj.c
index 731b62e..9a59043 100644
--- a/src/mesa/main/bufferobj.c
+++
On Sun, Apr 3, 2016 at 5:36 PM, Kenneth Graunke
wrote:
> This is kind of a hack. We currently track precise/invariant
> requirements by decorating ir_variables. Propagating or grafting
> the RHS of an assignment to a precise/invariant value into some
> other expression tree can lose those decor
---
src/mesa/drivers/x11/fakeglx.c | 29 +
1 file changed, 21 insertions(+), 8 deletions(-)
diff --git a/src/mesa/drivers/x11/fakeglx.c b/src/mesa/drivers/x11/fakeglx.c
index 208fc5bb..508dc65e 100644
--- a/src/mesa/drivers/x11/fakeglx.c
+++ b/src/mesa/drivers/x11/fake
XMesaVisual.vishandle is being unconditionally overwritten every time
glXChooseVisual/glXGetVisualFromFBConfig returns a new XVisualInfo
instance, causing a memory leak.
---
src/mesa/drivers/x11/fakeglx.c | 26 --
1 file changed, 8 insertions(+), 18 deletions(-)
diff --git
This removes a hack introduced in 1999 in the first version of
fakeglx.c, with the comment:
/* XXX revisit this after 3.0 is finished. */
Mesa 4.0 was released in 2001. It is now 2016, and Mesa 11.0 was
released last year.
---
src/mesa/drivers/x11/fakeglx.c | 42 +++---
The vishandle member of XMesaVisualInfo is used to support the
comparison of XVisualInfo instances by pointer value, in
find_glx_visual(). The comparison however will always be false, as in
every case the comparison is made, the VisualInfo instance being
compared to is a new allocation passed in t
This is kind of a hack. We currently track precise/invariant
requirements by decorating ir_variables. Propagating or grafting
the RHS of an assignment to a precise/invariant value into some
other expression tree can lose those decorations.
In the long run, it might be better to replace these ir_
The SIN and COS instructions on Intel hardware can produce values
slightly outside of the [-1.0, 1.0] range for a small set of values.
Obviously, this can break everyone's expectations about trig functions.
According to an internal presentation, the COS instruction can produce
a value up to 1.
Am 03.04.2016 um 17:05 schrieb Rob Clark:
> On Sat, Apr 2, 2016 at 8:31 PM, Rob Clark wrote:
>> On Sat, Apr 2, 2016 at 7:55 PM, Roland Scheidegger
>> wrote:
>>> I don't really have anything against the new interface (though don't
>>> really feel qualified for a proper review), but it is indeed t
Am 03.04.2016 um 02:31 schrieb Rob Clark:
> On Sat, Apr 2, 2016 at 7:55 PM, Roland Scheidegger wrote:
>> I don't really have anything against the new interface (though don't
>> really feel qualified for a proper review), but it is indeed the
>> existence of the two interfaces living in parallel se
Am 04.04.2016 um 00:25 schrieb Jose Fonseca:
> For adding .v4f32 like suffixes to intrinsics, taking special care for
> scalar case, which was being often neglected.
>
> This fixes invalid IR when doing mipmap filtering on SSE2 (the only
> case where we'd use intrinsics with scalars.)
> ---
> src
On Sun, Apr 3, 2016 at 12:29 PM, Chih-Wei Huang wrote:
> 2016-04-04 0:53 GMT+08:00 Chih-Wei Huang :
>> 2016-04-02 4:42 GMT+08:00 Rob Herring :
>>>
>>> Here's an initial gralloc implementation based on my GBM map/unmap support:
>>>
>>> https://github.com/robherring/gbm_gralloc
>>>
>>> It's based on
For adding .v4f32 like suffixes to intrinsics, taking special care for
scalar case, which was being often neglected.
This fixes invalid IR when doing mipmap filtering on SSE2 (the only
case where we'd use intrinsics with scalars.)
---
src/gallium/auxiliary/gallivm/lp_bld_arit.c | 19 -
The functionality should be accessible today with KHR_debug (and
ARB_something, also in GL 4.3). I believe glretrace uses it, and
there's also an option to expose GREMEDY_string_marker. (If you do
ST_DEBUG=gremedy iirc.)
On Sun, Apr 3, 2016 at 5:53 PM, Samuel Pitoiset
wrote:
> I guess it's needed
I guess it's needed to override the gl version to use this feature as
4.3 is not yet supported?
Anyway, this might be useful if apps use glDebugMessageInsert().
Reviewed-by: Samuel Pitoiset
On 04/03/2016 10:04 PM, Ilia Mirkin wrote:
This should hopefully make it a little easier to debug with
On 03/04/16 16:20, Roland Scheidegger wrote:
Am 03.04.2016 um 12:24 schrieb Jose Fonseca:
We could unconditionally use these instrinsics, but performance with SSE2
would suck, as LLVM falls back to calling libm.
Would that really work now? Last time I checked, calls out to libm from
the jitted
This sets the AA location to the d3d11
spec.
EG/NI 8X MSAA is left as is. Not sure
why it was set different to Cayman, so
let it as is.
Signed-off-by: Axel Davy
---
src/gallium/drivers/radeon/cayman_msaa.c | 68
1 file changed, 34 insertions(+), 34 deletions(-)
This should hopefully make it a little easier to debug with GL
applications like glretrace and looking at command streams.
Signed-off-by: Ilia Mirkin
---
src/gallium/drivers/nouveau/nv50/nv50_context.c | 25 +
src/gallium/drivers/nouveau/nv50/nv50_screen.c | 2 +-
src/g
d3d 9 needs COLOR0 to be 1.0 on all channels when
undefined. 0.0 for the others is fine.
GL behaviour is undefined.
Signed-off-by: Axel Davy
---
src/gallium/drivers/r600/evergreen_state.c | 4
1 file changed, 4 insertions(+)
diff --git a/src/gallium/drivers/r600/evergreen_state.c
b/src/ga
Provide a callback to reallocate the underlying storage of a resource so
that it is not bound to any existing fences.
Signed-off-by: Ilia Mirkin
---
src/gallium/drivers/nouveau/nouveau_buffer.c | 33
src/gallium/drivers/nouveau/nouveau_buffer.h | 4 +++
src/gall
On Sun, Apr 3, 2016 at 12:53 PM, Chih-Wei Huang wrote:
> 2016-04-02 4:42 GMT+08:00 Rob Herring :
>>
>> Here's an initial gralloc implementation based on my GBM map/unmap support:
>>
>> https://github.com/robherring/gbm_gralloc
>>
>> It's based on drm_gralloc, but heavily re-written to collapse som
Am 03.04.2016 um 10:11 schrieb Axel Davy:
> d3d 9 needs COLOR0 to be 1.0 on all channels when
> undefined. 0.0 for the others is fine.
> GL behaviour is undefined.
>
> Signed-off-by: Axel Davy
> ---
> src/gallium/drivers/r600/r600_state.c | 4
> 1 file changed, 4 insertions(+)
>
> diff --g
On 03/04/2016 19:37, Marek Olšák wrote:
r600_state.c only applies to r600-r700. evergreen_state.c is for EG
and NI. Did you want to update that as well?
Marek
Thanks for pointing that out, I'll write a patch for EG and NI as well.
Axem
___
mesa-dev
For the series:
Reviewed-by: Marek Olšák
Marek
On Sun, Apr 3, 2016 at 10:11 AM, Axel Davy wrote:
> Besides depth/stencil, the hardware doesn't support
> mixed formats.
>
> The GL state tracker doesn't make use of them.
>
> Signed-off-by: Axel Davy
> ---
> src/gallium/drivers/radeonsi/si_stat
r600_state.c only applies to r600-r700. evergreen_state.c is for EG
and NI. Did you want to update that as well?
Marek
On Sun, Apr 3, 2016 at 10:11 AM, Axel Davy wrote:
> d3d 9 needs COLOR0 to be 1.0 on all channels when
> undefined. 0.0 for the others is fine.
> GL behaviour is undefined.
>
> S
Reviewed-by: Eduardo Lima Mitev
On 04/03/2016 10:34 AM, Kenneth Graunke wrote:
Signed-off-by: Kenneth Graunke
---
src/compiler/glsl/ir_print_visitor.cpp | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/src/compiler/glsl/ir_print_visitor.cpp
b/src/compiler/glsl/ir_pr
2016-04-04 0:53 GMT+08:00 Chih-Wei Huang :
> 2016-04-02 4:42 GMT+08:00 Rob Herring :
>>
>> Here's an initial gralloc implementation based on my GBM map/unmap support:
>>
>> https://github.com/robherring/gbm_gralloc
>>
>> It's based on drm_gralloc, but heavily re-written to collapse some
>> unnecess
2016-04-02 4:42 GMT+08:00 Rob Herring :
>
> Here's an initial gralloc implementation based on my GBM map/unmap support:
>
> https://github.com/robherring/gbm_gralloc
>
> It's based on drm_gralloc, but heavily re-written to collapse some
> unnecessary layers.
Thank you for it.
What GPU have you te
On Sun, Apr 3, 2016 at 4:37 AM, Kenneth Graunke wrote:
> Ilia Mirkin did all the hard work here. We can just enable it.
In fairness, the *hard* work was done by the people who added texture
and image buffers support to mesa. Anyways, mind also updating GL3.txt
and perhaps relnotes? This was the
Am 03.04.2016 um 12:24 schrieb Jose Fonseca:
> We could unconditionally use these instrinsics, but performance with SSE2
> would suck, as LLVM falls back to calling libm.
Would that really work now? Last time I checked, calls out to libm from
the jitted code weren't just slow, they simply crashed.
Am 03.04.2016 um 12:24 schrieb Jose Fonseca:
> Exactly the same code.
> ---
> src/gallium/auxiliary/gallivm/lp_bld_arit.c | 11 +++
> 1 file changed, 3 insertions(+), 8 deletions(-)
>
> diff --git a/src/gallium/auxiliary/gallivm/lp_bld_arit.c
> b/src/gallium/auxiliary/gallivm/lp_bld_arit
On Sat, Apr 2, 2016 at 8:31 PM, Rob Clark wrote:
> On Sat, Apr 2, 2016 at 7:55 PM, Roland Scheidegger wrote:
>> I don't really have anything against the new interface (though don't
>> really feel qualified for a proper review), but it is indeed the
>> existence of the two interfaces living in par
Ping? (~4 months later). Ilia? :)
On 11/23/2015 09:36 PM, Samuel Pitoiset wrote:
Fixes the following piglit tests:
- gl-1.0-edgeflag
- gl-1.0-edgeflag-quads
- gl-2.0-edgeflag
- gl-2.0-edgeflag-immediate
- point-vertex-id divisor
- point-vertex-id gl_InstanceID
- point-vertex-id gl_
This series is,
Tested-By: Edward O'Callaghan
I didn`t pick up anything major wrong with it, but with others
minor suggestions this series is also,
Reviewed-By: Edward O'Callaghan
Kind Regards,
On 2016-04-03 00:10, Bas Nieuwenhuizen wrote:
This series implements OpenGL compute shader for r
This series is,
Acked-by: Edward O'Callaghan
On 2016-04-03 21:16, Timothy Arceri wrote:
This is the final clean-up of the buffer block structures. With this
series we just create two arrays to begin with and drop the combined
array.
Note to avoid code churn and regressions I intend to squash
On 2016-04-03 14:55, Ilia Mirkin wrote:
On Sat, Apr 2, 2016 at 10:54 PM, Edward O'Callaghan
wrote:
This series implements ARB_framebuffer_no_attachments for radeonsi &
r600g. It is a rebase of the last previous patch series with the
respective Rb's added.
I have given back my R9 hw today and s
On Sun, 2016-04-03 at 01:37 -0700, Kenneth Graunke wrote:
> Consider the case of linking a program with both a vertex and
> fragment
> shader. The VS may compute output varyings that are intended for
> transform feedback, and not read by the fragment shader.
>
> In this case, var->data.is_unmatch
This is the final clean-up of the buffer block structures. With this
series we just create two arrays to begin with and drop the combined
array.
Note to avoid code churn and regressions I intend to squash patches
1-4 before pushing I've just sent them split up to make reviewing
easier.
__
---
src/compiler/glsl/linker.cpp | 70
1 file changed, 70 deletions(-)
diff --git a/src/compiler/glsl/linker.cpp b/src/compiler/glsl/linker.cpp
index 75a2afa..2f152d6 100644
--- a/src/compiler/glsl/linker.cpp
+++ b/src/compiler/glsl/linker.cpp
@@ -4122
---
src/compiler/glsl/link_uniform_initializers.cpp | 17 +++---
src/compiler/glsl/link_uniforms.cpp | 22 +++--
src/compiler/glsl/linker.cpp| 42 ++---
3 files changed, 48 insertions(+), 33 deletions(-)
diff --git a/src/compiler/gls
With this chage we create the UBO and SSBO arrays separately from the
beginning rather than putting them into a combined array and splitting
it apart later.
---
src/compiler/glsl/link_uniform_blocks.cpp | 204 +---
src/compiler/glsl/link_uniform_initializers.cpp | 4 +-
---
src/compiler/glsl/link_uniform_blocks.cpp | 1 -
src/mesa/main/mtypes.h| 5 -
2 files changed, 6 deletions(-)
diff --git a/src/compiler/glsl/link_uniform_blocks.cpp
b/src/compiler/glsl/link_uniform_blocks.cpp
index 3ef1633..2efb4e3 100644
--- a/src/compiler/glsl/link_
---
src/compiler/glsl/link_uniform_blocks.cpp | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/src/compiler/glsl/link_uniform_blocks.cpp
b/src/compiler/glsl/link_uniform_blocks.cpp
index 2efb4e3..25a30e3 100644
--- a/src/compiler/glsl/link_uniform_blocks.cpp
+++ b/sr
Index is the block index so we need to lookup the reference in the
separate arrays not the combined buffer block array.
---
src/mesa/main/shader_query.cpp | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/src/mesa/main/shader_query.cpp b/src/mesa/main/shader_query.cpp
inde
For simulating less capable machines.
---
src/gallium/auxiliary/gallivm/lp_bld_init.c | 25 ++---
1 file changed, 14 insertions(+), 11 deletions(-)
diff --git a/src/gallium/auxiliary/gallivm/lp_bld_init.c
b/src/gallium/auxiliary/gallivm/lp_bld_init.c
index ab55be4..6e08ac4 10
Exactly the same code.
---
src/gallium/auxiliary/gallivm/lp_bld_arit.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/src/gallium/auxiliary/gallivm/lp_bld_arit.c
b/src/gallium/auxiliary/gallivm/lp_bld_arit.c
index 1277743..587c83a 100644
--- a/src/gallium/auxiliar
We could unconditionally use these instrinsics, but performance with SSE2
would suck, as LLVM falls back to calling libm.
lp_test_arit.
---
src/gallium/auxiliary/gallivm/lp_bld_arit.c | 46 -
1 file changed, 39 insertions(+), 7 deletions(-)
diff --git a/src/gallium/au
https://bugs.freedesktop.org/show_bug.cgi?id=94805
Bug ID: 94805
Summary: Compile Mesa , specific compilation , error: LLVM is
required to build Gallium
Product: Mesa
Version: 11.1
Hardware: Other
OS: All
Ilia Mirkin did all the hard work here. We can just enable it.
Signed-off-by: Kenneth Graunke
---
src/mesa/drivers/dri/i965/intel_extensions.c | 1 +
1 file changed, 1 insertion(+)
ES31-CTS.texture_buffer.texture_buffer_texture_buffer_range failed
when I originally enabled this extension, but
Consider the case of linking a program with both a vertex and fragment
shader. The VS may compute output varyings that are intended for
transform feedback, and not read by the fragment shader.
In this case, var->data.is_unmatched_generic_inout will be true,
but we still cannot eliminate the varyi
Signed-off-by: Kenneth Graunke
---
src/compiler/glsl/ir_print_visitor.cpp | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/src/compiler/glsl/ir_print_visitor.cpp
b/src/compiler/glsl/ir_print_visitor.cpp
index 960b23f..e06acce 100644
--- a/src/compiler/glsl/ir_print_visito
d3d 9 needs COLOR0 to be 1.0 on all channels when
undefined. 0.0 for the others is fine.
GL behaviour is undefined.
Signed-off-by: Axel Davy
---
src/gallium/drivers/radeonsi/si_state_shaders.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/gallium/drivers/radeonsi/si_state_shaders.c
Besides depth/stencil, the hardware doesn't support
mixed formats.
The GL state tracker doesn't make use of them.
Signed-off-by: Axel Davy
---
src/gallium/drivers/radeonsi/si_state.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/src/gallium/drivers/radeonsi/si_state.c
b/src/g
d3d 9 needs COLOR0 to be 1.0 on all channels when
undefined. 0.0 for the others is fine.
GL behaviour is undefined.
Signed-off-by: Axel Davy
---
src/gallium/drivers/r600/r600_state.c | 4
1 file changed, 4 insertions(+)
diff --git a/src/gallium/drivers/r600/r600_state.c
b/src/gallium/driv
83 matches
Mail list logo
