On 19.05.2014 15:03, Mathias Fröhlich wrote:
>
> I tried to get my local llvm install again to a point where I can see
> backtrace information, but still failed to get valgrind/massif to print
> these nice backtraces. All of the llvm addresses are not resolved so far.
You may want to try some or
https://bugs.freedesktop.org/show_bug.cgi?id=78773
Tapani Pälli changed:
What|Removed |Added
CC||lem...@gmail.com
--- Comment #3 from Tapa
https://bugs.freedesktop.org/show_bug.cgi?id=78773
--- Comment #4 from Tapani Pälli ---
Jan, could you please add full log output from doom3 when you run it.
--
You are receiving this mail because:
You are the assignee for the bug.
___
mesa-dev mailin
I don't have an ILK at hand but the fix should be trivial.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=78872
Cc: "10.2"
Signed-off-by: Topi Pohjolainen
---
src/mesa/drivers/dri/i965/intel_fbo.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/src/mesa/drivers
https://bugs.freedesktop.org/show_bug.cgi?id=7
Priority: medium
Bug ID: 7
Keywords: regression
CC: kenn...@whitecape.org
Assignee: mesa-dev@lists.freedesktop.org
Summary: test_eu_compact.c:54:3: error: implicit declaratio
Hi
> It should be possible to adapt some of the existing float texture tests
> to run on ES mode without too much effort.
Oh dear, the test makes the GL API convert between 16 and 32 bit float formats.
Also it does not appear to test filtering either.
Would it be prudent to make 4 tests: one fo
(forgotten from commit 4b04152d)
Signed-off-by: Tapani Pälli
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=7
---
src/mesa/drivers/dri/i965/test_eu_compact.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/mesa/drivers/dri/i965/test_eu_compact.c
b/src/mesa/dr
On Mon, May 19, 2014 at 10:31:56AM +0300, Tapani P?lli wrote:
> (forgotten from commit 4b04152d)
>
> Signed-off-by: Tapani Pälli
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=7
> ---
> src/mesa/drivers/dri/i965/test_eu_compact.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion
https://bugs.freedesktop.org/show_bug.cgi?id=7
Vinson Lee changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
From: Kevin Rogovin
Define the macro GL_OES_standard_derivatives as 1 if the extension
GL_OES_standard_derivatives is supported.
---
src/glsl/glcpp/glcpp-parse.y | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/glsl/glcpp/glcpp-parse.y b/src/glsl/glcpp/glcpp-parse.y
index 9887583..83f6
https://bugs.freedesktop.org/show_bug.cgi?id=78892
Priority: medium
Bug ID: 78892
Assignee: mesa-dev@lists.freedesktop.org
Summary: configure: error: Could not find clang internal header
stddef.h in /usr/lib64/llvm/clang/3.4 Use
You are complicating it. If we followed the specification to the
letter, the driver would have to advertise OpenGL 1.1 instead of 2.1.
The fact r300 cannot filter floating-point textures is documented by
the vendor and game developers (especially those who targeted D3D9)
knew about it.
For OpenGL
SCons is required for Windows. Add links to flex/bison for Windows.
Reorder items and improve formatting.
---
docs/install.html | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/docs/install.html b/docs/install.html
index 5061ede..f12425f 100644
--- a/docs/ins
https://bugs.freedesktop.org/show_bug.cgi?id=78914
Priority: medium
Bug ID: 78914
Assignee: mesa-dev@lists.freedesktop.org
Summary: Front/Backfaces do not cover the same pixels when
rasterized
Severity: normal
Classificat
Without this, I get linking failures (static linking).
The static linking is sort of required for me, because otherwise Steam and
applications using the Steam runtime regularily fail because my LLVM was
compiled and linked against a newer libgcc_s, libstdc++, etc. and uses
features from those newe
Michel Dänzer schrieb am 19.05.2014 04:12:
> On 18.05.2014 18:37, Kai Wasserbäch wrote:
>>
>> And instead of just not starting, my X starts crashing, whenever
>> libGL fails to load a (32 bit) driver.
>
> FWIW, some potential alternatives for avoiding the X crashes:
>
> With current xserver Git m
Looks good to me.
Jose
- Original Message -
> From: Roland Scheidegger
>
> 2ea923cf571235dfe573c35c3f0d90f632bd86d8 had the side effect of IR counting
> now being done after IR optimization instead of before. Some quick analysis
> shows that there's roughly 1.5 times more IR instruction
Hi,
Firstly, I shall introduce myself (at least more formally than just
sending some patches). My name is Bruno Jiménez, I'm studying
physics at Zaragoza's University (Spain) and I am participating in
this year's Google Summer of Code, where I will try to improve
the compute_memory_pool, solve an
---
src/gallium/drivers/r600/compute_memory_pool.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/gallium/drivers/r600/compute_memory_pool.c
b/src/gallium/drivers/r600/compute_memory_pool.c
index 2f0d4c8..ccbb211 100644
--- a/src/gallium/drivers/r600/compute_memory_po
Explanation of the changes, as requested by Tom Stellard:
Let's take need after is calculated as
item->size_in_dw+2048 - (pool->size_in_dw - allocated)
BEFORE:
If need is positive or 0:
we calculate need += 1024 - (need % 1024), which is like
cealing to the nearest multiple of 1024, f
---
src/gallium/drivers/r600/compute_memory_pool.c | 8
1 file changed, 8 insertions(+)
diff --git a/src/gallium/drivers/r600/compute_memory_pool.c
b/src/gallium/drivers/r600/compute_memory_pool.c
index ccbb211..7143545 100644
--- a/src/gallium/drivers/r600/compute_memory_pool.c
+++ b/s
Now, items whose size is a multiple of 1024 dw won't leave
1024 dw between itself and the following item
The rest of the cases is left as it was
---
src/gallium/drivers/r600/compute_memory_pool.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/src/gallium/drivers/r600
In this case, NULL checks are added to compute_memory_grow_pool,
so it returns -1 when it fails. This makes necesary
to handle such cases in compute_memory_finalize_pending
when it is needed to grow the pool
---
src/gallium/drivers/r600/compute_memory_pool.c | 30 --
src/ga
This fixes an issue when running cl-program-bitcoin-phatk
piglit test where some of the inputs have negative values
---
src/gallium/drivers/r600/evergreen_compute.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gallium/drivers/r600/evergreen_compute.c
b/src/gallium/drive
Removed compute_memory_defrag declaration because it seems
to be unimplemented.
I think that this function would have been the one that solves
the problem with fragmentation that compute_memory_finalize_pending has.
Also removed comments that are already at compute_memory_pool.c
---
src/gallium/
On 04/09/2014 02:56 AM, Tapani Pälli wrote:
> Patch initializes the UniformRemapTable for explicit locations. This
> needs to happen before optimizations to make sure all inactive uniforms
> get their explicit locations correctly.
>
> Signed-off-by: Tapani Pälli
> ---
> src/glsl/linker.cpp | 99
On 04/09/2014 02:56 AM, Tapani Pälli wrote:
> Support inactive uniforms that have explicit location set in
> glUniform* functions.
>
> Signed-off-by: Tapani Pälli
> ---
> src/mesa/main/uniform_query.cpp | 15 +++
> 1 file changed, 15 insertions(+)
>
> diff --git a/src/mesa/main/unif
On 04/09/2014 02:56 AM, Tapani Pälli wrote:
> Patch refactors the existing uniform processing so explicit locations
> are taken in to account during variable processing. These locations
> are temporarily stored in gl_uniform_storage before actual locations
> are set.
>
> The 'remap_location' varia
On 04/09/2014 02:56 AM, Tapani Pälli wrote:
> Patch adds a preprocessor define for the extension and stores explicit
> location data for uniforms during AST->HIR conversion. It also sets
> layout token to be available when having the extension in place.
>
> Signed-off-by: Tapani Pälli
> ---
> sr
Either this patch should:
- Delete the extension enable flag
- Change the table in extensions.c to use dummy_true
or
The next patch needs to not say "all drivers that support GLSL".
I think we should just enable it everywhere.
On 04/09/2014 02:56 AM, Tapani Pälli wrote:
> Signed-off-by: Tapa
Patches 1, 2, and 7 are
Reviewed-by: Ian Romanick
I sent out comments for the rest.
On 04/09/2014 02:56 AM, Tapani Pälli wrote:
> Hi;
>
> Patches implement the extension, no Piglit regressions and all the tests
> for the extension pass. Location initialization and assignment is done
> like Ian
On 04/09/2014 02:56 AM, Tapani Pälli wrote:
> Patch adds new implementation dependent value required by the
> GL_ARB_explicit_uniform_location extension. Default value for user
> assignable locations is calculated as sum of MaxUniformComponents
> for each stage.
>
> Signed-off-by: Tapani Pälli
>
Hi,
When Mesa's GLSL compiler is faced with a code like this:
// vec4 packednormal exists
vec3 normal;
normal.xy = packednormal.wy * 2.0 - 1.0;
normal.z = sqrt(1.0 - dot(normal.xy, normal.xy));
// now do not use the "normal" at all anywhere
Then the dead code elimination pass
On 05/19/2014 06:39 AM, Marek Olšák wrote:
> You are complicating it. If we followed the specification to the
> letter, the driver would have to advertise OpenGL 1.1 instead of 2.1.
>
> The fact r300 cannot filter floating-point textures is documented by
> the vendor and game developers (especiall
Thanks for the quick fix. :) Series is
Reviewed-by: Ian Romanick
On 05/18/2014 11:12 PM, Kenneth Graunke wrote:
> This reverts commit bd44ac8b5ca08016bb064b37edaec95eccfdbcd5.
>
> Fixes:
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=78842
> Bugzilla: https://bugs.freedesktop.org/show
LGTM
Reviewed-by: Ian Romanick
On 05/19/2014 07:17 AM, Brian Paul wrote:
> SCons is required for Windows. Add links to flex/bison for Windows.
> Reorder items and improve formatting.
> ---
> docs/install.html | 15 ---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff
Available from
git://people.freedesktop.org/~mattst88/mesa compaction
Highlights
- Print disassembly after instruction compaction, while still
having control-flow graph information and higher-level IR
annotations.
- Three improvements to instruction compaction increase number
Let's us avoid recompacting the SIMD8 instructions when we compact the
SIMD16 program.
---
src/mesa/drivers/dri/i965/brw_blorp_clear.cpp| 2 +-
src/mesa/drivers/dri/i965/brw_clip.c | 2 +-
src/mesa/drivers/dri/i965/brw_eu.h | 2 +-
src/mesa/drivers/dri/i965/brw_eu_
Similar to Paul's commit e9fa3a944 except brw_fs_generator's debug_flag
is for DEBUG_WM and DEBUG_BLORP.
---
src/mesa/drivers/dri/i965/brw_blorp_blit.cpp| 13 +++--
src/mesa/drivers/dri/i965/brw_blorp_blit_eu.cpp | 17 -
src/mesa/drivers/dri/i965/brw_blorp_blit_eu.h |
The DO instruction doesn't exist on Gen6+. Since before this commit, DO
always ended a basic block, if it also happened to start one (e.g., a
while loop inside an if statement) the block containing only the DO
would actually contain no hardware instructions.
Pre-Gen6's WHILE instructions jumps to
Will be used to print disassembly after jump targets are set and
instructions are compacted, while still retaining higher-level IR
annotations and basic block information.
An array of 'struct annotation' will live along side the generated
assembly. The generators will populate the array with their
Note the weirdness with src1 subregs. The compacted immediate fields are
uncompacted to bits [127:96] and the high five bits of the subreg
mapping maps to bits [100:96].
Number of compacted instructions: 790085 -> 817752 (3.50%)
---
src/mesa/drivers/dri/i965/brw_eu_compact.c | 83
Number of compacted instructions: 827404 -> 833045 (0.68%)
---
src/mesa/drivers/dri/i965/brw_eu_emit.c | 20
1 file changed, 20 insertions(+)
diff --git a/src/mesa/drivers/dri/i965/brw_eu_emit.c
b/src/mesa/drivers/dri/i965/brw_eu_emit.c
index 1810233..ab00d7c 100644
--- a/sr
... to tell us whether it emitted any code. Will be used to determine
whether we need to skip an annotation for it.
---
src/mesa/drivers/dri/i965/brw_fs.h | 4 ++--
src/mesa/drivers/dri/i965/brw_fs_generator.cpp | 5 +++--
src/mesa/drivers/dri/i965/gen8_fs_generator.cpp | 5 +++--
3
That we were comparing its return value with offsets should have been a
clue. :)
Make it take a void *store in preparation for making the function useful
elsewhere.
---
src/mesa/drivers/dri/i965/brw_eu_emit.c | 63 +
1 file changed, 33 insertions(+), 30 deletions(-
The instruction count does not include padding NOPs, but the compaction
stats do.
---
src/mesa/drivers/dri/i965/brw_eu_compact.c | 19 ---
src/mesa/drivers/dri/i965/brw_fs_generator.cpp | 8
src/mesa/drivers/dri/i965/brw_vec4_generator.cpp | 7 +++
3 files ch
Enables the next commits to compact more instructions.
---
src/mesa/drivers/dri/i965/brw_eu_emit.c | 28 ++--
1 file changed, 26 insertions(+), 2 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_eu_emit.c
b/src/mesa/drivers/dri/i965/brw_eu_emit.c
index 38d327a..d8e
Running shader-db without INTEL_DEBUG=annotation reduces the runtime
from ~90 to ~80 seconds on my machine. It also reduces the disk space
consumed by the .out files from 660 MB (676 on disk) to 343 MB (358 on
disk).
---
src/mesa/drivers/dri/i965/brw_fs_generator.cpp| 6 --
src/mesa/driver
---
src/mesa/drivers/dri/i965/brw_fs.h | 4 +-
src/mesa/drivers/dri/i965/brw_fs_generator.cpp | 156 -
2 files changed, 77 insertions(+), 83 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_fs.h
b/src/mesa/drivers/dri/i965/brw_fs.h
index 111e994..d26b
---
src/mesa/drivers/dri/i965/brw_fs_generator.cpp | 4 ++--
src/mesa/drivers/dri/i965/gen8_fs_generator.cpp | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_fs_generator.cpp
b/src/mesa/drivers/dri/i965/brw_fs_generator.cpp
index 872b5a4..914
---
src/mesa/drivers/dri/i965/brw_vec4.h | 4 +-
src/mesa/drivers/dri/i965/brw_vec4_generator.cpp | 109 +--
2 files changed, 66 insertions(+), 47 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_vec4.h
b/src/mesa/drivers/dri/i965/brw_vec4.h
index a86972a
---
src/mesa/drivers/dri/i965/brw_eu_compact.c | 20 +++-
1 file changed, 3 insertions(+), 17 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_eu_compact.c
b/src/mesa/drivers/dri/i965/brw_eu_compact.c
index 40d1fc2..f6f055f 100644
--- a/src/mesa/drivers/dri/i965/brw_eu_com
Also perform arithmetic on char* rather than void* since the latter is a
GNU C extension not available in C++.
---
src/mesa/drivers/dri/i965/brw_eu.h | 12
src/mesa/drivers/dri/i965/brw_eu_emit.c | 11 ---
2 files changed, 12 insertions(+), 11 deletions(-)
diff --git a/s
---
src/mesa/drivers/dri/i965/brw_vec4.h | 3 +-
src/mesa/drivers/dri/i965/gen8_vec4_generator.cpp | 103 +-
2 files changed, 63 insertions(+), 43 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_vec4.h
b/src/mesa/drivers/dri/i965/brw_vec4.h
index 3a1eb1
Number of compacted instructions: 817752 -> 827404 (1.18%)
---
src/mesa/drivers/dri/i965/brw_eu_emit.c | 16
1 file changed, 16 insertions(+)
diff --git a/src/mesa/drivers/dri/i965/brw_eu_emit.c
b/src/mesa/drivers/dri/i965/brw_eu_emit.c
index d8efa01..1810233 100644
--- a/src/me
---
src/mesa/drivers/dri/i965/gen8_fs_generator.cpp | 5 +
src/mesa/drivers/dri/i965/gen8_vec4_generator.cpp | 3 +++
2 files changed, 8 insertions(+)
diff --git a/src/mesa/drivers/dri/i965/gen8_fs_generator.cpp
b/src/mesa/drivers/dri/i965/gen8_fs_generator.cpp
index 0ac00f9..90743ee 10064
---
src/mesa/drivers/dri/i965/brw_fs.h | 3 +-
src/mesa/drivers/dri/i965/gen8_fs_generator.cpp | 138 +++-
2 files changed, 65 insertions(+), 76 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_fs.h
b/src/mesa/drivers/dri/i965/brw_fs.h
index d26b972..139
Small code reduction. Will let us move the program header code into a
common place in generate_assembly().
---
src/mesa/drivers/dri/i965/brw_fs_generator.cpp | 56 ++---
src/mesa/drivers/dri/i965/gen8_fs_generator.cpp | 46 +---
2 files changed, 42 insertions(+
Were used by the blorp unit test programs.
---
src/mesa/drivers/dri/i965/brw_blorp_blit.cpp| 20
src/mesa/drivers/dri/i965/brw_blorp_blit_eu.cpp | 4 ++--
src/mesa/drivers/dri/i965/brw_blorp_blit_eu.h | 2 +-
src/mesa/drivers/dri/i965/brw_fs.h | 5 ++---
---
src/mesa/drivers/dri/i965/brw_fs_generator.cpp| 29 ++-
src/mesa/drivers/dri/i965/brw_vec4_generator.cpp | 17 ++---
src/mesa/drivers/dri/i965/gen8_fs_generator.cpp | 29 ++-
src/mesa/drivers/dri/i965/gen8_vec4_generator.cpp | 17 ++---
https://bugs.freedesktop.org/show_bug.cgi?id=78771
U. Artie Eoff changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Wed, May 14, 2014 at 10:39:05PM -0600, Gary Wong wrote:
> loader_get_pci_id_for_fd() and loader_get_device_name_for_fd() now attempt
> all available strategies to identify the hardware, instead of conditionally
> compiling in a single test. The existing libudev and DRM approaches have
> been re
Looks good.
Reviewed-by: Courtney Goeltzenleuchter
On Mon, May 19, 2014 at 12:12 AM, Kenneth Graunke wrote:
> These aren't necessary - all of the following code is predicated on mask
> being non-zero, so no code will get executed anyway.
>
> Signed-off-by: Kenneth Graunke
> Cc: "10.2"
> ---
Cc:
Signed-off-by: Anuj Phogat
---
src/mesa/drivers/common/meta.c | 97 +++---
1 file changed, 44 insertions(+), 53 deletions(-)
diff --git a/src/mesa/drivers/common/meta.c b/src/mesa/drivers/common/meta.c
index 3ef3f79..87609b4 100644
--- a/src/mesa/drivers/
_mesa_meta_setup_blit_shader() currently generates a fragment shader
which, irrespective of the number of draw buffers, writes the color
to only one output variable. Current shader rely on an undefined
behavior and possibly works by chance.
>From OpenGL 4.0 spec, page 256:
"If a fragment shader
Series is:
Reviewed-by: Chris Forbes
On Mon, May 19, 2014 at 6:12 PM, Kenneth Graunke wrote:
> This is a replacement for bd44ac8b5ca08016bb064b37edaec95eccfdbcd5
> that should actually work.
>
> Fixes Piglit's copyteximage-border on swrast, as well as one of
> es3conform's packed_pixels_pixelst
On Mon, May 19, 2014 at 1:20 PM, Anuj Phogat wrote:
> Cc:
> Signed-off-by: Anuj Phogat
> ---
> src/mesa/drivers/common/meta.c | 97
> +++---
> 1 file changed, 44 insertions(+), 53 deletions(-)
>
> diff --git a/src/mesa/drivers/common/meta.c b/src/mesa/driver
On Mon, May 19, 2014 at 1:20 PM, Anuj Phogat wrote:
> _mesa_meta_setup_blit_shader() currently generates a fragment shader
> which, irrespective of the number of draw buffers, writes the color
> to only one output variable. Current shader rely on an undefined
> behavior and possibly works by chanc
On Tue, May 20, 2014 at 8:20 AM, Anuj Phogat wrote:
> @@ -247,7 +247,8 @@ _mesa_meta_setup_blit_shader(struct gl_context *ctx,
> struct blit_shader *shader = choose_blit_shader(target, table);
> const char *vs_input, *vs_output, *fs_input, *fs_output;
> const char *vs_preprocess = "",
On Mon, May 19, 2014 at 2:45 PM, Matt Turner wrote:
> On Mon, May 19, 2014 at 1:20 PM, Anuj Phogat wrote:
>> _mesa_meta_setup_blit_shader() currently generates a fragment shader
>> which, irrespective of the number of draw buffers, writes the color
>> to only one output variable. Current shader r
On Mon, May 19, 2014 at 3:12 PM, Chris Forbes wrote:
> On Tue, May 20, 2014 at 8:20 AM, Anuj Phogat wrote:
>> @@ -247,7 +247,8 @@ _mesa_meta_setup_blit_shader(struct gl_context *ctx,
>> struct blit_shader *shader = choose_blit_shader(target, table);
>> const char *vs_input, *vs_output, *f
https://bugs.freedesktop.org/show_bug.cgi?id=78914
Roland Scheidegger changed:
What|Removed |Added
Summary|Front/Backfaces do not |[llvmpipe] Front/Backfaces
If you're going to do that, you'd really want to add draw buffer count
to the cache key (and i guess this might be the point where you
convert the blit shader cache to be a hashtable), to avoid recompiling
all the time if the app does two blits with the same target but
different draw buffer counts.
On 18/05/14 12:22, Jonathan Gray wrote:
[snip]
>
> Currently I run my autotools builds like this:
>
> export LDFLAGS=-L/usr/local/lib
> export CPPFLAGS="-I/usr/local/include -I/usr/local/include/libelf"
> export AUTOMAKE_VERSION=1.12
> export AUTOCONF_VERSION=2.69
> export LEX=/usr/local/bin/gfle
On 15/05/14 05:39, Gary Wong wrote:
> loader_get_pci_id_for_fd() and loader_get_device_name_for_fd() now attempt
> all available strategies to identify the hardware, instead of conditionally
> compiling in a single test. The existing libudev and DRM approaches have
> been retained, and another sim
On Mon, May 19, 2014 at 10:56 AM, Aras Pranckevicius wrote:
> Hi,
>
> When Mesa's GLSL compiler is faced with a code like this:
>
> // vec4 packednormal exists
> vec3 normal;
> normal.xy = packednormal.wy * 2.0 - 1.0;
> normal.z = sqrt(1.0 - dot(normal.xy, normal.xy));
> // now
On Mon, May 19, 2014 at 3:52 PM, Chris Forbes wrote:
> If you're going to do that, you'd really want to add draw buffer count
> to the cache key (and i guess this might be the point where you
> convert the blit shader cache to be a hashtable), to avoid recompiling
> all the time if the app does tw
On Mon, May 19, 2014 at 11:57:58PM +0100, Emil Velikov wrote:
> On 18/05/14 12:22, Jonathan Gray wrote:
> [snip]
> >
> > Currently I run my autotools builds like this:
> >
> > export LDFLAGS=-L/usr/local/lib
> > export CPPFLAGS="-I/usr/local/include -I/usr/local/include/libelf"
> > export AUTOMAK
In commit 4be146b1, I neglected to add the new property to the strings
array. This leads to the string '(null)' to be printed instead when
converting a GS shader to text.
Signed-off-by: Ilia Mirkin
Cc: "10.2"
---
src/gallium/auxiliary/tgsi/tgsi_strings.c | 3 ++-
1 file changed, 2 insertions(+)
On 05/19/2014 07:51 PM, Ian Romanick wrote:
On 04/09/2014 02:56 AM, Tapani Pälli wrote:
Patch initializes the UniformRemapTable for explicit locations. This
needs to happen before optimizations to make sure all inactive uniforms
get their explicit locations correctly.
Signed-off-by: Tapani Päll
On 05/19/2014 08:07 PM, Ian Romanick wrote:
On 04/09/2014 02:56 AM, Tapani Pälli wrote:
Patch refactors the existing uniform processing so explicit locations
are taken in to account during variable processing. These locations
are temporarily stored in gl_uniform_storage before actual locations
a
On 05/19/2014 08:09 PM, Ian Romanick wrote:
On 04/09/2014 02:56 AM, Tapani Pälli wrote:
Support inactive uniforms that have explicit location set in
glUniform* functions.
Signed-off-by: Tapani Pälli
---
src/mesa/main/uniform_query.cpp | 15 +++
1 file changed, 15 insertions(+)
Hi Ian,
When I was writing the `precise` support I found some error cases in
the GLSL parser where we reject combinations of layout() with
invariant / interpolation / etc qualifiers.
This seems to be consistent with the GLSL 1.50 grammar (or, at least,
admits all the examples that were given in v
On 05/19/2014 08:18 PM, Ian Romanick wrote:
On 04/09/2014 02:56 AM, Tapani Pälli wrote:
Patch adds a preprocessor define for the extension and stores explicit
location data for uniforms during AST->HIR conversion. It also sets
layout token to be available when having the extension in place.
Sig
On 05/19/2014 08:21 PM, Ian Romanick wrote:
Either this patch should:
- Delete the extension enable flag
- Change the table in extensions.c to use dummy_true
or
The next patch needs to not say "all drivers that support GLSL".
I think we should just enable it everywhere.
OK, I was follow
On 05/19/2014 08:26 PM, Ian Romanick wrote:
On 04/09/2014 02:56 AM, Tapani Pälli wrote:
Patch adds new implementation dependent value required by the
GL_ARB_explicit_uniform_location extension. Default value for user
assignable locations is calculated as sum of MaxUniformComponents
for each stag
On 05/19/2014 03:52 PM, Chris Forbes wrote:
> If you're going to do that, you'd really want to add draw buffer count
> to the cache key (and i guess this might be the point where you
> convert the blit shader cache to be a hashtable), to avoid recompiling
> all the time if the app does two blits wi
>> For OpenGL ES, I propose a simpler solution:
>> - don't touch ARB_texture_float at all
>> - add OES_texture_float to gl_extensions
>> - add OES_texture_float_linear to gl_extensions
>> - define OES_texture_half_float as o(OES_texture_float)
>> - define OES_texture_half_float_linear as o(OES_tex
88 matches
Mail list logo
