dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82717] OpenCL support for mandelbulber-opencl
Date: Sun, 17 Aug 2014 08:26:07 +0000	[thread overview]
Message-ID: <bug-82717-502-rUhjLHRX8p@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-82717-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1828 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=82717

--- Comment #1 from Christoph Haag <haagch@frickel.club> ---
Small additions:

With these patches the binary garbage from the build log is gone:
http://patchwork.freedesktop.org/patch/31309/
http://patchwork.freedesktop.org/patch/31311/
http://patchwork.freedesktop.org/patch/31310/
So this is already fixed.

Problem 4 is not related to mesa I think. The problem is that there is a huge
buffer because CL_DEVICE_MAX_COMPUTE_UNITS is so big.

Curiously CL_DEVICE_MAX_COMPUTE_UNITS gets increased by 100 every time my gpu
wakes up from runpm. I have reduced it to this program:

#include <CL/cl.hpp>
#include <iostream>
int main() {
  int err, numberOfComputeUnits = 0;
  std::vector<cl::Platform> platformList;
  cl::Platform::get(&platformList);
  cl_context_properties cprops[3] = { CL_CONTEXT_PLATFORM,
(cl_context_properties) (platformList[0])(), 0 };
  cl::Context *context = new cl::Context(CL_DEVICE_TYPE_GPU, cprops, NULL,
NULL, &err);
  std::vector<cl::Device> devices = context->getInfo<CL_CONTEXT_DEVICES>();
  devices[0].getInfo(CL_DEVICE_MAX_COMPUTE_UNITS, &numberOfComputeUnits);
  std::cout << "OpenCL Number of compute units: " << numberOfComputeUnits <<
std::endl;;
  return 0;
}

Every time my gpu goes to sleep and wakes up this increases by 100.

I have reduced numberOfComputeUnits in the code to 1.
Then it finally correctly says "clCreateImage() not supported by OpenCL 1.1."
So this will then have to wait for OpenCL 1.2.

But to me it seems these two things should be addressed for 1.0/1.1 already:
* "-cl-denorms-are-zero"
* "cannot combine with previous 'type-name' declaration specifier" (at least
get a better error message into clang)
* CL_DEVICE_MAX_COMPUTE_UNITS (??)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2864 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2014-08-17  8:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-17  0:56 [Bug 82717] New: OpenCL support for mandelbulber-opencl bugzilla-daemon
2014-08-17  8:26 ` bugzilla-daemon [this message]
2014-08-19  9:34 ` [Bug 82717] " bugzilla-daemon
2014-08-19 18:29 ` bugzilla-daemon
2014-08-19 19:58 ` bugzilla-daemon
2014-08-21 18:40 ` bugzilla-daemon
2014-08-22 17:09 ` bugzilla-daemon
2014-08-22 17:51 ` bugzilla-daemon
2017-01-27 14:57 ` bugzilla-daemon
2017-03-22 16:01 ` bugzilla-daemon
2017-03-22 16:43 ` bugzilla-daemon
2018-05-30 14:08 ` bugzilla-daemon
2018-09-09 22:39 ` 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-82717-502-rUhjLHRX8p@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).