8 Commits (eea3424c3875c3285d0d1c3f0d2bdbcb4bfcb53d)

Author	SHA1	Message	Date
jsteube	c79bed3b7d	Prepare for a more dynamic #pragma unroll use	9 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	9 years ago
Jens Steube	23efa03209	Cleanup -m 131xx kernels to latest standard	9 years ago
Gabriele 'matrix' Gristina	c2a32eddb3	Fix build failure for -m 13100 on Apple Platform	9 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.	9 years ago
Fist0urs	62bed36638	Add verification of checksum for -m 13100 ... This avoid collisions by arc4'ing all data then hmac-md5 when valid ASN1 structures headers are found. Performance should not be impacted.	9 years ago
Fist0urs	223ab0b3db	Cosmetic change -m 13100 ... Removed commented part (the commented part was there to implement full last arc4'ing + hmac-md5) We will see if some people find collision. In this case we will add this last check	9 years ago
Fist0urs	c3dabdd69e	Initial commit	9 years ago