From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96488] [r600g]OpenCL driver causes segfault in ImageMagick's Histogram kernel
Date: Fri, 23 Dec 2016 15:28:19 +0000 [thread overview]
Message-ID: <bug-96488-502-hEhQUliroL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96488-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1134 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=96488
--- Comment #8 from Jan Vesely <jv356@scarletmail.rutgers.edu> ---
(In reply to nixscripter from comment #7)
> Normally, I would be asking in this comment if there is any progress on
> this, but I can tell there has been... change, at least.
>
> Now instead of crashing, it deadlocks the calling process waiting on a
> mutex. Forever, as far as I can tell.
>
> LLVM version: r289770
> Mesa version: commit 47351b843a
>
> Perhaps this is more easily fixed? Or is this getting to the heart of the
> matter implied in comment 2?
the hang is probably a separate bug. ImageMagick test suite results on my Turks
GPU are:
# TOTAL: 86
# PASS: 78
# SKIP: 0
# XFAIL: 0
# FAIL: 3
# XPASS: 0
# ERROR: 5
the errors and failures are accompanied by:
Assertion `i < getNumRegs() && "Register number out of range!"' failed.
The patches to add support for noret atomics (should be good enough for
histogram) are at:
https://reviews.llvm.org/D27989
https://reviews.llvm.org/D28067
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2217 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-12-23 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 0:55 [Bug 96488] [r600g]OpenCL driver causes segfault in ImageMagick's Histogram kernel bugzilla-daemon
2016-06-11 0:55 ` bugzilla-daemon
2016-06-11 3:26 ` bugzilla-daemon
2016-06-11 11:45 ` bugzilla-daemon
2016-06-11 13:47 ` bugzilla-daemon
2016-06-11 19:15 ` bugzilla-daemon
2016-06-12 12:41 ` bugzilla-daemon
2016-06-12 23:13 ` bugzilla-daemon
2016-12-23 5:45 ` bugzilla-daemon
2016-12-23 15:28 ` bugzilla-daemon [this message]
2016-12-29 3:25 ` bugzilla-daemon
2017-01-16 21:36 ` bugzilla-daemon
2017-01-22 6:59 ` 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-96488-502-hEhQUliroL@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