This aligns it to work similarly to nv50. However there's no library
code there, so the whole thing can be freed. Here we end up with an
allocated node that's not attached to a specific program.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=86792
Signed-off-by: Ilia Mirkin
Cc: mesa-sta..
https://bugs.freedesktop.org/show_bug.cgi?id=90383
--- Comment #2 from Michel Dänzer ---
Please attach a backtrace of the crash, preferably from gdb.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
On Fri, May 8, 2015 at 11:15 PM, Jason Ekstrand wrote:
> On Fri, May 8, 2015 at 10:03 PM, Connor Abbott wrote:
>> This series implements a bunch of related optimizations that run at
>> once as part of the same pass to eliminate control flow that is
>> useless. This includes both unreachable code
https://bugs.freedesktop.org/show_bug.cgi?id=90383
--- Comment #1 from Sylvain BERTRAND ---
http://filebin.ca/21BLOQZgI8Xh/mesa.conf
http://filebin.ca/21BLZM5UsAmW/dmesg
http://filebin.ca/21BLfuazDXEf/Xorg.0.log
linux (radeon drm git), llvm git, xserver git, ati xorg drv git, mesa git
--
You a
https://bugs.freedesktop.org/show_bug.cgi?id=90383
Bug ID: 90383
Summary: assembly enabled mesa crashes dota2
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Reviewed-by: Tobias Klausmann
On 09.05.2015 09:31, Ilia Mirkin wrote:
Commit 44673512a84 enabled support for saturating fmul. However
experimentally this does not seem to work on the older chips. Restrict
the feature to G200 (NVA0) and later.
Reported-by: Pierre Moreau
Bugzilla: https://bugs.
Refactor ::trigger and ::abort to split out the operations that access
concurrently modified data members and require locking from the
recursive and possibly re-entrant part of these methods. This will
avoid some deadlock situations when locking is implemented.
---
src/gallium/state_trackers/clov
---
src/gallium/state_trackers/clover/core/event.cpp | 15 ++-
src/gallium/state_trackers/clover/core/event.hpp | 4 ++--
2 files changed, 12 insertions(+), 7 deletions(-)
diff --git a/src/gallium/state_trackers/clover/core/event.cpp
b/src/gallium/state_trackers/clover/core/event.cp
---
src/gallium/state_trackers/clover/core/event.cpp | 8
1 file changed, 8 insertions(+)
diff --git a/src/gallium/state_trackers/clover/core/event.cpp
b/src/gallium/state_trackers/clover/core/event.cpp
index 969d19a..e1f9de0 100644
--- a/src/gallium/state_trackers/clover/core/event.cpp
Tom Stellard writes:
> This mutex effectively prevents an event's chain or wait_count from
> being updated while it is in the process of triggering. Otherwise it
> may be possible to add to an event's chain after it has been triggered,
> which causes the chained event to never be triggered.
> --
It is possible the server advertises a render-node.
In that case no authentication is needed,
and Gem names are forbidden.
Reviewed-by: Dave Airlie
Reviewed-by: Daniel Stone
Signed-off-by: Axel Davy
v2: do not check for __DRI_IMAGE_DRIVER, but instead
do not advertise __DRI_DRI2_LOADER when o
On 08/05/2015 18:07, Emil Velikov a wrote :
Let's use drmGetNodeTypeFromFd(), rather than hard-coding this ?
+
+ for (i = 0; extensions[i]; i++) {
+ if (strcmp(extensions[i]->name, __DRI_IMAGE_DRIVER) == 0)
+ return EGL_TRUE;
If memory serves me right__DRI_IMAGE_DRIVER is a cl
Tom Stellard writes:
> It was possible for some events never to get triggered if one thread
> was creating events and another threads was waiting for them.
>
> This patch consolidates soft_event::wait() and hard_event::wait()
> into event::wait() so that hard_event objects will now wait for
> all
Hey Tom,
Tom Stellard writes:
> This consolidates signalled checks into the same place.
> ---
> src/gallium/state_trackers/clover/core/event.cpp | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/gallium/state_trackers/clover/core/event.cpp
> b/src/gallium/state_track
Commit 44673512a84 enabled support for saturating fmul. However
experimentally this does not seem to work on the older chips. Restrict
the feature to G200 (NVA0) and later.
Reported-by: Pierre Moreau
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=90350
Signed-off-by: Ilia Mirkin
Cc: mesa
https://bugs.freedesktop.org/show_bug.cgi?id=90311
Julien Isorce changed:
What|Removed |Added
CC||bri...@vmware.com,
|
16 matches
Mail list logo