Hi,
To which failure are you refering? Could you please send me a
test/program that I can try to track this down?
Thanks!
Bruno
On Thu, 2014-06-19 at 10:21 -0400, Jan Vesely wrote:
Signed-off-by: Jan Vesely jan.ves...@rutgers.edu
CC: Bruno Jimenez brunoji...@gmail.com
---
The failure now
Signed-off-by: Jan Vesely jan.ves...@rutgers.edu
CC: Bruno Jimenez brunoji...@gmail.com
---
The failure now hits assertion compute_memory_pool.c:408, instead of
u_inlines.h:275:pipe_buffer_map_range: Assertion `offset buffer-width0'
src/gallium/drivers/r600/evergreen_compute.c | 9 +++--
1
On Thu, 2014-06-19 at 17:12 +0200, Bruno Jimenez wrote:
Hi,
To which failure are you refering? Could you please send me a
test/program that I can try to track this down?
well, the compute_memory_finalize_pending() function can possibly return
-1 so it's prudent to check for it.
as for the
On Thu, Jun 19, 2014 at 11:22:28AM -0400, Jan Vesely wrote:
On Thu, 2014-06-19 at 17:12 +0200, Bruno Jimenez wrote:
Hi,
To which failure are you refering? Could you please send me a
test/program that I can try to track this down?
well, the compute_memory_finalize_pending() function
On Thu, 2014-06-19 at 08:34 -0700, Tom Stellard wrote:
On Thu, Jun 19, 2014 at 11:22:28AM -0400, Jan Vesely wrote:
On Thu, 2014-06-19 at 17:12 +0200, Bruno Jimenez wrote:
Hi,
To which failure are you refering? Could you please send me a
test/program that I can try to track this
