From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94503] OpenCL kernel segfaults during compilation on Clover RadeonSI with Pitcairn GPU
Date: Wed, 22 Mar 2017 16:26:13 +0000 [thread overview]
Message-ID: <bug-94503-502-t6kTE9uALG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94503-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1471 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94503
Vedran Miletić <vedran@miletic.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |99553
Resolution|--- |FIXED
Assignee|mesa-dev@lists.freedesktop. |dri-devel@lists.freedesktop
|org |.org
QA Contact|mesa-dev@lists.freedesktop. |dri-devel@lists.freedesktop
|org |.org
Status|NEW |RESOLVED
Component|Other |Drivers/Gallium/radeonsi
Summary|OpenCL segfaults during |OpenCL kernel segfaults
|compilation |during compilation on
| |Clover RadeonSI with
| |Pitcairn GPU
--- Comment #4 from Vedran Miletić <vedran@miletic.net> ---
Neither kernel crashes anymore here with Mesa git and LLVM git, but it's
possible that stable versions also work. Please reopen if this is still an
issue.
Referenced Bugs:
https://bugs.freedesktop.org/show_bug.cgi?id=99553
[Bug 99553] Tracker bug for runnning OpenCL applications on Clover
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3840 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
parent reply other threads:[~2017-03-22 16:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-94503-502@http.bugs.freedesktop.org/>]
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-94503-502-t6kTE9uALG@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).