From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93748] [r600g]OpenCL driver causes ImageMagick to segfault
Date: Mon, 30 May 2016 18:34:47 +0000 [thread overview]
Message-ID: <bug-93748-502-1cZKJS57Br@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93748-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 564 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93748
--- Comment #6 from Jan Vesely <jan.vesely@rutgers.edu> ---
based on the LLVM dump something is trying to do v2 load.
Do you know what noise type is used?
Guassian noise in that kernel uses sinpi and cospi which use v2float (float
load is the same as int).
can you try newer llvm version?
proper constant address space loads were implemented in r269481. it fixed
builtin functions that rely on tables, like sinpi/cospi.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1350 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-05-30 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 0:39 [Bug 93748] [r600g]OpenCL driver causes ImageMagick to segfault bugzilla-daemon
2016-01-18 15:57 ` bugzilla-daemon
2016-01-19 2:33 ` bugzilla-daemon
2016-05-30 17:44 ` bugzilla-daemon
2016-05-30 17:48 ` bugzilla-daemon
2016-05-30 17:56 ` bugzilla-daemon
2016-05-30 18:34 ` bugzilla-daemon [this message]
2016-05-30 20:27 ` [Bug 93748] [r600g]OpenCL driver causes ImageMagick display command " bugzilla-daemon
2016-05-30 20:27 ` 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-93748-502-1cZKJS57Br@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).