On 09/04/2015 08:57 PM, Benjamin Bellec wrote:
Currently, the temperature is displayed with a "%" symbol in
gallium/hud, which is quite odd.
Marek suggested to only change the value "100" to another value so
that this symbol is no more displayed. That works very well. This is
the patch #1. I
Cuts compile/link time of the fragment shader in #91857 by 19%
(16.28 -> 13.05).
I didn't bother with the acp sets because they're smaller, but it
might be worth doing as well.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=91857
Signed-off-by: Kenneth Graunke
---
src/glsl/opt_constant_
Cuts compile/link time of the fragment shader in #91857 by 25%
(21.64 -> 16.28).
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=91857
Signed-off-by: Kenneth Graunke
---
.../drivers/dri/i965/brw_fs_vector_splitting.cpp | 48 --
1 file changed, 26 insertions(+), 22 de
Cuts compile/link time of the fragment shader in bug #91857 by 31%
(31.79 -> 21.64). It has over 8,000 variables so linked lists are
terrible.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=91857
Signed-off-by: Kenneth Graunke
---
src/glsl/opt_constant_variable.cpp | 39
On Fri, Sep 04, 2015 at 02:40:54PM -0700, Jason Ekstrand wrote:
> On Fri, Sep 4, 2015 at 1:22 PM, Chris Wilson wrote:
> > With the introduction of ARB_shader_image_load_store, shaders
> > are able to perform random memory accesses to texture that
> > are not easily tracked by the driver. Rather th
Subject has glsl as "area-tag" on this patch. Guess that should
be i965. With that fixed, and if you've tested that this does not
significantly regress smaller shaders, the series is:
Reviewed-by: Thomas Helland
___
mesa-dev mailing list
mesa-dev@lists.
On Sat, 2015-09-05 at 02:21 -0700, Kenneth Graunke wrote:
> Cuts compile/link time of the fragment shader in bug #91857 by 31%
> (31.79 -> 21.64). It has over 8,000 variables so linked lists are
> terrible.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=91857
> Signed-off-by: Kenneth
On Sat, 2015-09-05 at 02:21 -0700, Kenneth Graunke wrote:
> Cuts compile/link time of the fragment shader in #91857 by 25%
> (21.64 -> 16.28).
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=91857
> Signed-off-by: Kenneth Graunke
> ---
> .../drivers/dri/i965/brw_fs_vector_splitting.cp
On Sat, 2015-09-05 at 02:21 -0700, Kenneth Graunke wrote:
> Cuts compile/link time of the fragment shader in #91857 by 19%
> (16.28 -> 13.05).
>
> I didn't bother with the acp sets because they're smaller, but it
> might be worth doing as well.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.
Chris Wilson writes:
> On Fri, Sep 04, 2015 at 02:40:54PM -0700, Jason Ekstrand wrote:
>> On Fri, Sep 4, 2015 at 1:22 PM, Chris Wilson
>> wrote:
>> > With the introduction of ARB_shader_image_load_store, shaders
>> > are able to perform random memory accesses to texture that
>> > are not easily
Mesa 10.6.6 is now available.
This release includes patches for mesa core, i965 (regression fixes), r600
(assertions and crash fixes in the sb backend), radeonsi (workaround for
GPU hang in Unigine Heaven) and nouveau (piglit tests).
Chris Wilson (2):
i965: Prevent coordinate overflow in i
At that point the swizzle should be correct.
---
First versions of commit 19cf9 included some manual
swizzle assignment that got removed after review [1],
as get_nir_src with the right number of components
should set a proper swizzle on most of the cases. This
one was overlooked.
[1] http://lists
Hello Lauri,
I saw that your patch implementing adaptive vsync is not committed to mesa.
Ref,
http://lists.freedesktop.org/archives/mesa-dev/2013-December/050184.html
Why not ? Is there any issue with it ? As a end user, adaptive vsync seems
a nice feature. But maybe I'm not aware of drawbacks.
On Sep 5, 2015 4:45 AM, "Francisco Jerez" wrote:
>
> Chris Wilson writes:
>
> > On Fri, Sep 04, 2015 at 02:40:54PM -0700, Jason Ekstrand wrote:
> >> On Fri, Sep 4, 2015 at 1:22 PM, Chris Wilson
wrote:
> >> > With the introduction of ARB_shader_image_load_store, shaders
> >> > are able to perform
On Sat, Sep 5, 2015 at 2:31 AM, Kenneth Graunke wrote:
> On Friday, September 04, 2015 11:56:29 AM Connor Abbott wrote:
>> On Thu, Sep 3, 2015 at 2:32 PM, Kenneth Graunke
>> wrote:
>> > Prevents regressions in ~128 tests when fixing unlink_block_successors
>> > in the next commit.
>> >
>> > XXX:
On Sat, 5 Sep 2015 15:41:00 +0200
Benjamin Bellec wrote:
> Hello Lauri,
>
> I saw that your patch implementing adaptive vsync is not committed to mesa.
> Ref,
> http://lists.freedesktop.org/archives/mesa-dev/2013-December/050184.html
>
> Why not ? Is there any issue with it ? As a end user, ada
On Wed, Sep 2, 2015 at 2:20 PM, Kenneth Graunke wrote:
> In various versions of OpenGL and GLSL, it's possible to declare
> multiple VS input variables with aliasing attribute locations.
>
> So, when computing the storage requirements for vertex attributes,
> we can't simply add up the sizes. Ins
vbuf is never null. We want to make sure that a resource was allocated
for the vbuf, which is *vbuf.
Signed-off-by: Ilia Mirkin
---
src/mesa/state_tracker/st_cb_bitmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/mesa/state_tracker/st_cb_bitmap.c
b/src/mesa/state_tr
On Sun, Jul 12, 2015 at 4:14 PM, Roland Scheidegger wrote:
> Am 12.07.2015 um 19:30 schrieb Ilia Mirkin:
>> I asked this on IRC, but figured I'd get wider distribution for the
>> question. The situation is that nv50 doesn't support RGBA32 MS8
>> textures. However QuerySamplesForFormat will try its
https://bugs.freedesktop.org/show_bug.cgi?id=91169
--- Comment #2 from Ilia Mirkin ---
Created attachment 118090
--> https://bugs.freedesktop.org/attachment.cgi?id=118090&action=edit
proper patch
Can you see if this helps? I wasn't sure what the binary name was so couldn't
add it to drirc. How
From: Francisco Jerez
Fixes arb_shader_image_load_store/execution/load-from-cleared-image.shader_test
Cc: Chris Wilson
Cc: Jason Ekstrand
Tested-by: Jordan Justen
---
RE: i965: Perform an explicit flush after doing _mesa_meta_pbo_TexSubImage
curro has some concerns about potential perf imp
On Sat, Sep 05, 2015 at 11:30:44AM -0700, Jordan Justen wrote:
> From: Francisco Jerez
>
> Fixes
> arb_shader_image_load_store/execution/load-from-cleared-image.shader_test
>
> Cc: Chris Wilson
> Cc: Jason Ekstrand
> Tested-by: Jordan Justen
> ---
> RE: i965: Perform an explicit flush after
https://bugs.freedesktop.org/show_bug.cgi?id=91888
Bug ID: 91888
Summary: EGL Wayland software rendering no longer work after
regression
Product: Mesa
Version: git
Hardware: Other
OS: All
Status:
https://bugs.freedesktop.org/show_bug.cgi?id=91889
Bug ID: 91889
Summary: Planetary Anihilation: Titans display content of other
processes buffers
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linu
https://bugs.freedesktop.org/show_bug.cgi?id=91889
Krzysztof A. Sobiecki changed:
What|Removed |Added
Priority|medium |highest
--
You are receiving th
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #1 from Krzysztof A. Sobiecki ---
My specs:
OpenGL renderer string: Gallium 0.4 on AMD JUNIPER (DRM 2.43.0, LLVM 3.8.0)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.1.0-devel
VGA compatible controller: Advanced Micro
Hey Kristian, Ander,
Can I convince either/both of you to give this a once over and a r-b ?
--Ray
On Fri, Aug 28, 2015 at 2:15 PM, Ray Strode wrote:
> From: Ray Strode
>
> At the moment if a gbm buffer is imported and the gbm buffer
> has an old-style GBM_BO_FORMAT format, the import will cras
The reply from Eric Anholt made two suggestions that should not be
difficult to implement for someone who made the patch in the first
place. Why would code be committed when improvements could be easily
made? From what I have seen, this kind of thing happens even to
experienced mesa developers who
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #2 from Krzysztof A. Sobiecki ---
Apitrace:
https://drive.google.com/file/d/0B3J0Mg89izcbMVgzMDdWYkxoY3M/view?usp=sharing
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=91889
--- Comment #3 from Albert Freeman ---
The mesa developers are well aware of this and see it all the time in a myriad
of different environments. It isn't only a problem in mesa, but also in other
parts of the linux graphics stack (e.g. X). Not ma
Maybe we should add some kind of prefix to this to indicate a
performance vs security trade off and a more powerful general overide
option to enable/disable all such future flags?
On 4 September 2015 at 09:39, Jeremy Huddleston Sequoia
wrote:
> Wow, that's a blast from the past ;)
>
>> On Sep 3,
On Sep 5, 2015 6:27 AM, "Alejandro Piñeiro" wrote:
>
> At that point the swizzle should be correct.
> ---
>
> First versions of commit 19cf9 included some manual
> swizzle assignment that got removed after review [1],
> as get_nir_src with the right number of components
> should set a proper swizz
https://bugs.freedesktop.org/show_bug.cgi?id=91169
Béla Gyebrószki changed:
What|Removed |Added
CC||gyebr...@gmail.com
--- Comment #3 from
https://bugs.freedesktop.org/show_bug.cgi?id=91169
--- Comment #4 from Ilia Mirkin ---
(In reply to Béla Gyebrószki from comment #3)
> (In reply to Ilia Mirkin from comment #2)
> > Created attachment 118090 [details] [review] [review]
> > proper patch
> >
> > Can you see if this helps? I wasn't
34 matches
Mail list logo
