From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100288] clover unable to run OpenCL kernels since 03127bb radeonsi: compile all TGSI compute shaders asynchronously
Date: Mon, 20 Mar 2017 15:52:34 +0000 [thread overview]
Message-ID: <bug-100288-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1077 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100288
Bug ID: 100288
Summary: clover unable to run OpenCL kernels since 03127bb
radeonsi: compile all TGSI compute shaders
asynchronously
Product: Mesa
Version: git
Hardware: All
OS: All
Status: NEW
Severity: blocker
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: vedran@miletic.net
QA Contact: dri-devel@lists.freedesktop.org
Piglit's cl-custom-run-simple-kernel just waits endlessly. Bisected to:
commit 03127bb6d5454002b3d9c3a542f3ff1a5f1e91d9
Author: Marek Olšák <marek.olsak@amd.com>
Date: Sun Mar 5 01:14:51 2017 +0100
radeonsi: compile all TGSI compute shaders asynchronously
required by threaded gallium
Reviewed-by: Timothy Arceri <tarceri@itsqueeze.com>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2579 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-03-20 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 15:52 bugzilla-daemon [this message]
2017-03-20 23:04 ` [Bug 100288] clover unable to run OpenCL kernels since 03127bb radeonsi: compile all TGSI compute shaders asynchronously bugzilla-daemon
2017-03-21 1:21 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-100288-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).