Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 9 Nov 2017 17:25:04 +0100
From: Matus UHLAR - fantomas <uhlar@...tomas.sk>
To: john-users@...ts.openwall.com
Subject: Re: Re: opencl on amd (mesa ISC and clc-amd) fails

>On 12.10.17 18:27, Matus UHLAR - fantomas wrote:
>
>> Device 1: AMD ICELAND (DRM 3.8.0 / 4.9.0-4-amd64, LLVM 3.9.1) > 
>Benchmarking: mysql-sha1-opencl, MySQL 4.1+ [SHA1 OpenCL]... Options 
>used: -I /home/uhlar/src/debian/john/bleeding-jumbo/run/kernels 
>-cl-mad-enable -D__MESA__ -D__GPU__ -DDEVICE_INFO=10 
>-DSIZEOF_SIZE_T=8 -DDEV_VER_MAJOR=13 -DDEV_VER_MINOR=0 
>-D_OPENCL_COMPILER -DTWICE -DOFFSET_TABLE_SIZE=14 
>-DHASH_TABLE_SIZE=13 -DSHIFT64_OT_SZ=2 -DSHIFT64_HT_SZ=3 
>-DSHIFT128_OT_SZ=4 -DSHIFT128_HT_SZ=9 -DNUM_LOADED_HASHES=13 
>-DNUM_INT_KEYS=1 -DSELECT_CMP_STEPS=4 
>-DBITMAP_SIZE_BITS_LESS_ONE=32767 -DUSE_LOCAL_BITMAPS=1 
>-DIS_STATIC_GPU_MASK=0 -DCONST_CACHE_SIZE=1925299814 -DLOC_0=-1 
>-DLOC_1=-1 -DLOC_2=-1 -DLOC_3=-1 $JOHN/kernels /sha1_kernel.cl > 
>Build log: input.cl:139:18: warning: unknown attribute 
>'max_constant_size' ignored > <unknown>:0:0: in function sha1 void 
>(i32 addrspace(1)*, i32 addrspace(1)*, i32 addrspace(1)*, i32 
>addrspace(2)*, i32 addrspace(1)*, i32 addrspace(1)*, i32 
>addrspace(1)*, i32 addrspace(1)*, i32 addrspace(1)*, i32 
>addrspace(1)*): unsupported initializer for address space

looking at sha1_kernel.cl:

#if !defined(__OS_X__) && USE_CONST_CACHE && gpu_amd(DEVICE_INFO)
                 __attribute__((max_constant_size (NUM_INT_KEYS * 4)))
#endif

commenting this out didn't help

On 20.10.17 16:52, Claudio André wrote:
>Short answer, MESA is not supported.

that's unfortunate :-( 
I think I've seen mention of this somewhere but it's not said explicitly in
the docs - only recommendation of using vendor-supplied drivers.


>Long answer:
>> unsupported initializer for address space
>
>- Which address space (local or global)? Why is it creating an 
>initializer? Not the place to discuss the specification, but, as far 
>as I know there is no sentence that states "The memory is going to be 
>initialized". On the contrary.
>
>And finally, notice that this patch https://reviews.llvm.org/D6078 states:
>- Sort of depends on clang patch to not emit all LDS objects with 
>zeroinitializer anymore.
>
>I would say: the initialization is NOT expected or desired. 
>MESA/llvm/clang has a bug.

apparently MESA (I don't have llvm nor clang installed, wouldn't help
apparently).

should I try compile with clang? there's 3.9 and 3.9 available in debian
-- 
Matus UHLAR - fantomas, uhlar@...tomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Atheism is a non-prophet organization. 

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ