16 Commits (a415ec7afb939f7f1cfd894afc92dcbaf2b236cf)

Author	SHA1	Message	Date
jsteube	2ece9742e1	Compress multiple newlines to one	7 years ago
jsteube	d0fa9d059d	Remove some unused macros	7 years ago
jsteube	6401c58568	Align all the __constant buffers to workaround OpenCL JIT compiler errors in NV drivers 378.x	7 years ago
jsteube	bbb4c74e85	OpenCL Kernel: Remove "static" keyword from function declarations; Causes older Intel OpenCL runtimes to fail compiling	7 years ago
Gabriele Gristina	26a9c27eff	Fix kernel build warnings (no previous prototypes and/or incompatible function parameters ...	8 years ago
Jens Steube	7fe575e204	Add const qualifier to variable declaration of matching global memory objects	8 years ago
jsteube	3daf0af480	Added docs/credits.txt ... Added docs/team.txt	8 years ago
jsteube	8702d0e3e1	Workaround memory allocation limit from OpenCL by using multiple buffers for scrypt	8 years ago
Jens Steube	ed1863c263	Move macros DGST_R0 - DGST_R3 to host, define dgst_size for opencl kernel from host; both at runtime	8 years ago
Jens Steube	2899f53a15	Move files from include/ to OpenCL/ if they are used within kernels ... Rename includes in OpenCL so that it's easier to recognize them as such	8 years ago
jsteube	c79bed3b7d	Prepare for a more dynamic #pragma unroll use	8 years ago
Jens Steube	0b3743ce94	- Added inline declaration to functions from simd.c, common.c, rp.c and types_ocl.c to increase performance ... - Dropped static declaration from functions in all kernel to achieve OpenCL 1.1 compatibility - Added -cl-std=CL1.1 to all kernel build options - Created environment variable to inform NVidia OpenCL runtime to not create its own kernel cache - Created environment variable to inform pocl OpenCL runtime to not create its own kernel cache	8 years ago
jsteube	dad03e394d	Fixed two major problems ... 1) SIMD code for all attack-mode Macro vector_accessible() was not refactored and missing completely. Had to rename variables rules_cnt, combs_cnt and bfs_cnt into il_cnt which was a good thing anyway as with new SIMD code they all act in the same way. 2) SIMD code for attack-mode 0 With new SIMD code, apply_rules_vect() has to return u32 not u32x. This has massive impact on all *_a0 kernels. I've rewritten most of them. Deep testing using test.sh is still required. Some kernel need more fixes: - Some are kind of completely incompatible like m10400 but they still use old check_* includes, we should get rid of them as they are no longer neccessary as we have simd.c - Some have a chance but require additional effort like m11500. We can use commented out "#define NEW_SIMD_CODE" to find them This change can have negative impact on -a0 performance for device that require vectorization. That is mostly CPU devices. New GPU's are all scalar, so they wont get hurt by this. This change also proofes that there's no way to efficiently vectorize kernel rules with new SIMD code, but it enables the addition of the rule functions like @ that we were missing for some long time. This is a TODO.	8 years ago
Gabriele 'matrix' Gristina	44c3f16bcb	Fixed compiler warnings (unused variable)	9 years ago
Jens Steube	a62b7ed06e	Upgrade kernel to support dynamic local work sizes	9 years ago
jsteube	332b3c35e5	Added new hash mode -m 12900 = Android FDE (Samsung DEK)	9 years ago