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 87071] LLVM triggered Diagnostic Handler: unsupported call to function S2KItSaltedSHA1Generator in gpg
Date: Sun, 07 Dec 2014 13:03:05 +0000	[thread overview]
Message-ID: <bug-87071-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 87071
           Summary: LLVM triggered Diagnostic Handler: unsupported call to
                    function S2KItSaltedSHA1Generator in gpg
           Product: Mesa
           Version: 10.3
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: devurandom@gmx.net

Mesa 10.3.4 / LLVM 3.5.0 / libclc 0.0.1_pre20141027 seems to be unable to
compile the OpenCL function S2KItSaltedSHA1Generator from current
John-The-Ripper Git [1].

The function is too long to quote here, but the signature is:
inline void S2KItSaltedSHA1Generator(__global const uchar *password, int
password_length, __global const uchar *salt, int count, __global uchar *key,
int length)

My hardware as reported by JTR is:
# /usr/sbin/john -list=opencl-devices
Platform #0 name: Default
Platform version: OpenCL 1.1 MESA 10.3.4
        Device #0 (0) name:     AMD REDWOOD
        Device vendor:          X.Org
        Device type:            GPU (LE)
        Device version:         OpenCL 1.1 MESA 10.3.4
        Driver version:         10.3.4
        Native vector widths:   char 16, short 8, int 4, long 2
        Preferred vector width: char 16, short 8, int 4, long 2
        Global Memory:          1024.0 MB
        Local Memory:           32.0 KB (Local)
        Max memory alloc. size: 256.2 MB
        Max clock (MHz):        700
        Max Work Group Size:    256
        Parallel compute cores: 5

[1]
https://github.com/magnumripper/JohnTheRipper/blob/bleeding-jumbo/src/opencl/gpg_kernel.cl#L369

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

[-- Attachment #1.2: Type: text/html, Size: 3197 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-12-07 13:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-07 13:03 bugzilla-daemon [this message]
2014-12-07 13:04 ` [Bug 87071] LLVM triggered Diagnostic Handler: unsupported call to function S2KItSaltedSHA1Generator in gpg bugzilla-daemon
2016-08-25  2:16 ` bugzilla-daemon
2017-03-15 14:16 ` bugzilla-daemon
2018-05-30  7:09 ` [Bug 87071] [clover/redwood] John the Ripper: " bugzilla-daemon
2019-09-18 19:18 ` 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-87071-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;
as well as URLs for NNTP newsgroup(s).