All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66977] New: get_num_groups not supported by libclc
Date: Tue, 16 Jul 2013 19:40:35 +0000	[thread overview]
Message-ID: <bug-66977-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 66977
          Assignee: dri-devel@lists.freedesktop.org
           Summary: get_num_groups not supported by libclc
          Severity: trivial
    Classification: Unclassified
                OS: Linux (All)
          Reporter: jcharest@gmail.com
          Hardware: All
            Status: NEW
           Version: git
         Component: Drivers/Gallium/r600
           Product: Mesa

Created attachment 82499
  --> https://bugs.freedesktop.org/attachment.cgi?id=82499&action=edit
Here is the patch to call the appropriate intrinsic

Currently libclc does not support get_num_groups on r600 so it will give out an
error when used in an opencl kernel.

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

[-- Attachment #1.2: Type: text/html, Size: 2316 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:[~2013-07-16 19:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16 19:40 bugzilla-daemon [this message]
2013-07-19 15:06 ` [Bug 66977] get_num_groups not supported by libclc bugzilla-daemon
2015-09-28 11:17 ` 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-66977-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.