All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 74140] New: scrypt mining via bfgminer generates a too large opencl kernel
Date: Tue, 28 Jan 2014 07:29:42 +0000	[thread overview]
Message-ID: <bug-74140-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 74140
                CC: tstellar@gmail.com
          Assignee: dri-devel@lists.freedesktop.org
           Summary: scrypt mining via bfgminer generates a too large
                    opencl kernel
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: slicksam@gmx.com
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/Gallium/r600
           Product: Mesa

Needs less aggressive unrolling and/or opencl function call support.

Posted as a bug by request of tstellar

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

[-- Attachment #1.2: Type: text/html, Size: 2108 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-01-28  7:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28  7:29 bugzilla-daemon [this message]
2014-02-24  9:05 ` [Bug 74140] scrypt mining via bfgminer generates a too large opencl kernel bugzilla-daemon
2017-01-27 19:11 ` bugzilla-daemon
2019-09-18 19:13 ` 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-74140-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.