From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70779] OpenCL hangs with big kernels
Date: Sun, 14 Feb 2016 11:41:38 +0000 [thread overview]
Message-ID: <bug-70779-502-r82ZH8NOpY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-70779-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 958 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=70779
--- Comment #5 from EoD <EoD@xmw.de> ---
Created attachment 121742
--> https://bugs.freedesktop.org/attachment.cgi?id=121742&action=edit
dmesg after running the uint_add16() kernel
(In reply to Hristo Venev from comment #4)
> Here are two kernels that fail:
> __kernel void uint_div(__global const uint *a, __global const uint *b,
> __global uint *c){
> c[0]=a[0]/b[0];
> }
> __kernel void uint_add16(__global const uint *a, __global const uint *b,
> __global uint *c){
> for(uint i=0;i<16;i++) c[i]=a[i]+b[i];
> }
I actually can confirm that the 2nd kernel does cause a GPU stall in the radeon
driver (r600/Barts). It causes no problem with amdgpu (radeonsi/Tonga).
I am using kernel 4.5.0-rc3, current llvm 3.8 branch and current mesa git.
As I am not overly good with OpenCL, is this kernel somehow problematic?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1941 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 prev parent reply other threads:[~2016-02-14 11:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 19:36 [Bug 70779] New: OpenCL hangs with big kernels bugzilla-daemon
2013-11-06 9:38 ` [Bug 70779] " bugzilla-daemon
2014-01-08 19:38 ` bugzilla-daemon
2016-02-14 4:39 ` bugzilla-daemon
2016-02-14 7:11 ` bugzilla-daemon
2016-02-14 11:41 ` bugzilla-daemon [this message]
2016-02-15 6:11 ` bugzilla-daemon
2016-02-15 6:13 ` bugzilla-daemon
2017-03-22 16:05 ` 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-70779-502-r82ZH8NOpY@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).