From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99510] cl_khr_fp64 is reported as supported, but is not, on CAYMAN
Date: Tue, 24 Jan 2017 01:15:06 +0000 [thread overview]
Message-ID: <bug-99510-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1016 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99510
Bug ID: 99510
Summary: cl_khr_fp64 is reported as supported, but is not, on
CAYMAN
Product: Mesa
Version: 13.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: benjiwiebe14@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
On CAYMAN, cl_khr_fp64 is listed as a supported extension in clinfo, and
therefore also makes some kernels fail to compile due to their trying to
compile in things that need cl_khr_fp64 support. This causes clpeak to fail
with 'unsupported call to function __floatunsidf in compute_dp_v1'.
If you need more information I will be happy to provide more.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2379 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-01-24 1:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 1:15 bugzilla-daemon [this message]
2017-01-27 15:04 ` [Bug 99510] cl_khr_fp64 is reported as supported, but is not, on CAYMAN bugzilla-daemon
2018-09-12 20:16 ` bugzilla-daemon
2018-10-08 21:08 ` bugzilla-daemon
2018-10-08 21:10 ` bugzilla-daemon
2019-09-18 19:22 ` 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-99510-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