.. |
amp_a0.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
amp_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
amp_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
inc_cipher_aes.cl
|
Workaround ROCm compiler error in aes256_ExpandKey()
|
7 years ago |
inc_cipher_serpent.cl
|
Make all the OpenCL kernel function includes static
|
7 years ago |
inc_cipher_twofish.cl
|
Make all the OpenCL kernel function includes static
|
7 years ago |
inc_common.cl
|
Improve rule engine performance by improving append_0x80_xxx() performance by using precomputed values from constant memory
|
7 years ago |
inc_comp_multi.cl
|
Fixes https://github.com/hashcat/hashcat/issues/1123
|
8 years ago |
inc_comp_multi_bs.cl
|
Fixes https://github.com/hashcat/hashcat/issues/1123
|
8 years ago |
inc_comp_single.cl
|
Fixes https://github.com/hashcat/hashcat/issues/1123
|
8 years ago |
inc_comp_single_bs.cl
|
Fixes https://github.com/hashcat/hashcat/issues/1123
|
8 years ago |
inc_hash_constants.h
|
Moved init params in CPU (interface.c). Fixed vector-type problem in kernel a0.
|
7 years ago |
inc_hash_functions.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
inc_hash_md4.cl
|
Resurrect some volatile variables in order to correctly compile pure kernels on AMD drivers
|
7 years ago |
inc_hash_md5.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
inc_hash_ripemd160.cl
|
Resurrect some volatile variables in order to correctly compile pure kernels on AMD drivers
|
7 years ago |
inc_hash_sha1.cl
|
Resurrect some volatile variables in order to correctly compile pure kernels on AMD drivers
|
7 years ago |
inc_hash_sha224.cl
|
Resurrect some volatile variables in order to correctly compile pure kernels on AMD drivers
|
7 years ago |
inc_hash_sha256.cl
|
Resurrect some volatile variables in order to correctly compile pure kernels on AMD drivers
|
7 years ago |
inc_hash_sha384.cl
|
Resurrect some volatile variables in order to correctly compile pure kernels on AMD drivers
|
7 years ago |
inc_hash_sha512.cl
|
Resurrect some volatile variables in order to correctly compile pure kernels on AMD drivers
|
7 years ago |
inc_hash_whirlpool.cl
|
Resurrect some volatile variables in order to correctly compile pure kernels on AMD drivers
|
7 years ago |
inc_luks_aes.cl
|
Make all the OpenCL kernel function includes static
|
7 years ago |
inc_luks_af.cl
|
Make all the OpenCL kernel function includes static
|
7 years ago |
inc_luks_essiv.cl
|
Make all the OpenCL kernel function includes static
|
7 years ago |
inc_luks_serpent.cl
|
Make all the OpenCL kernel function includes static
|
7 years ago |
inc_luks_twofish.cl
|
Make all the OpenCL kernel function includes static
|
7 years ago |
inc_luks_xts.cl
|
Make all the OpenCL kernel function includes static
|
7 years ago |
inc_rp.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
inc_rp.h
|
Optimized a0 pure kernel for AMD
|
7 years ago |
inc_rp_optimized.cl
|
Optimized rule_op_mangle_dupechar_last(), rule_op_mangle_rotate_right(), rule_op_mangle_rotate_left() and append_block1() in rule engine
|
7 years ago |
inc_rp_optimized.h
|
Rename inc_rp.X to inc_rp_optimized.X
|
7 years ago |
inc_scalar.cl
|
Multiple changes:
|
7 years ago |
inc_simd.cl
|
Make all the OpenCL kernel function includes static
|
7 years ago |
inc_truecrypt_crc32.cl
|
Make all the OpenCL kernel function includes static
|
7 years ago |
inc_truecrypt_xts.cl
|
Make all the OpenCL kernel function includes static
|
7 years ago |
inc_types.cl
|
Fix typo
|
7 years ago |
inc_vendor.cl
|
Add VEGA specific inline assembly to improve all MD4, MD5, SHA1 and SHA256 based kernels
|
7 years ago |
m00000_a0-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m00000_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m00000_a1-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m00000_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00000_a3-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m00000_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00010_a0-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m00010_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m00010_a1-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m00010_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00010_a3-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m00010_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00020_a0-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m00020_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m00020_a1-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m00020_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00020_a3-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m00020_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00030_a0-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m00030_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m00030_a1-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m00030_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00030_a3-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m00030_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00040_a0-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m00040_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m00040_a1-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m00040_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00040_a3-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m00040_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00050_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m00050_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m00050_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00050_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00050_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00050_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00060_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m00060_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m00060_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00060_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00060_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00060_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00100_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m00100_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m00100_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00100_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00100_a3-optimized.cl
|
More VEGA specific inline assembly to improve SHA1 based kernels
|
7 years ago |
m00100_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00110_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m00110_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m00110_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00110_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00110_a3-optimized.cl
|
More VEGA specific inline assembly to improve SHA1 based kernels
|
7 years ago |
m00110_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00120_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m00120_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m00120_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00120_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00120_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00120_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00130_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m00130_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m00130_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00130_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00130_a3-optimized.cl
|
More VEGA specific inline assembly to improve SHA1 based kernels
|
7 years ago |
m00130_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00140_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m00140_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m00140_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00140_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00140_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00140_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00150_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m00150_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m00150_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00150_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00150_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00150_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00160_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m00160_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m00160_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00160_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00160_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00160_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00200_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m00200_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00200_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00300_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m00300_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m00300_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00300_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00300_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00300_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00400-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00400.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00500-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00500.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00600_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m00600_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00600_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00900_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m00900_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m00900_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00900_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00900_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m00900_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01000_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m01000_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m01000_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01000_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01000_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01000_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01100_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m01100_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m01100_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01100_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01100_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01100_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01300_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m01300_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m01300_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01300_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01300_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01300_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01400_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m01400_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m01400_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01400_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01400_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01400_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01410_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m01410_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m01410_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01410_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01410_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01410_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01420_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m01420_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m01420_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01420_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01420_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01420_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01430_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m01430_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m01430_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01430_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01430_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01430_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01440_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m01440_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m01440_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01440_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01440_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01440_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01450_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m01450_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m01450_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01450_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01450_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01450_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01460_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m01460_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m01460_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01460_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01460_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01460_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01500_a0.cl
|
Refactor some u32x to u32 where u32x is not needed
|
7 years ago |
m01500_a1.cl
|
Refactor some u32x to u32 where u32x is not needed
|
7 years ago |
m01500_a3.cl
|
Make -m 14000 a pure kernel only and add volatile for asm statement
|
7 years ago |
m01600-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01600.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01700_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m01700_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m01700_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01700_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01700_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01700_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01710_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m01710_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m01710_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01710_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01710_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01710_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01720_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m01720_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m01720_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01720_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01720_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01720_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01730_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m01730_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m01730_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01730_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01730_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01730_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01740_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m01740_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m01740_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01740_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01740_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01740_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01750_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m01750_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m01750_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01750_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01750_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01750_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01760_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m01760_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m01760_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01760_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01760_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01760_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01800-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m01800.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m02000_a0.cl
|
Fix --stdout kernels, gid_max was still set to u32
|
7 years ago |
m02000_a1.cl
|
Fix --stdout kernels, gid_max was still set to u32
|
7 years ago |
m02000_a3.cl
|
Fix --stdout kernels, gid_max was still set to u32
|
7 years ago |
m02100.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m02400_a0-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m02400_a1-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m02400_a3-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m02410_a0-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m02410_a1-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m02410_a3-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m02500.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m02501.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m02610_a0-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m02610_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m02610_a1-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m02610_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m02610_a3-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m02610_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m02710_a0-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m02710_a1-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m02710_a3-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m02810_a0-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m02810_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m02810_a1-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m02810_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m02810_a3-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m02810_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m03000_a0.cl
|
Fix some use of pw_t tmp variable
|
7 years ago |
m03000_a1.cl
|
Refactor some u32x to u32 where u32x is not needed
|
7 years ago |
m03000_a3.cl
|
Make -m 14000 a pure kernel only and add volatile for asm statement
|
7 years ago |
m03100_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m03100_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m03100_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m03200.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m03710_a0-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m03710_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m03710_a1-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m03710_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m03710_a3-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m03710_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m03800_a0-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m03800_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m03800_a1-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m03800_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m03800_a3-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m03800_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m03910_a0-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m03910_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m03910_a1-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m03910_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m03910_a3-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m03910_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04010_a0-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m04010_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m04010_a1-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m04010_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04010_a3-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m04010_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04110_a0-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m04110_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m04110_a1-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m04110_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04110_a3-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m04110_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04310_a0-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m04310_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m04310_a1-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m04310_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04310_a3-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m04310_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04400_a0-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m04400_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m04400_a1-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m04400_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04400_a3-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m04400_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04500_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m04500_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m04500_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04500_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04500_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04500_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04520_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m04520_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m04520_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04520_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04520_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04520_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04700_a0-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m04700_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m04700_a1-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m04700_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04700_a3-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m04700_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04800_a0-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m04800_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m04800_a1-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m04800_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04800_a3-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m04800_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04900_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m04900_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m04900_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04900_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04900_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m04900_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m05000_a0-optimized.cl
|
OpenCL Kernels: Rewritten Keccak kernel to run fully on registers and partially reversed last round
|
7 years ago |
m05000_a1-optimized.cl
|
OpenCL Kernels: Rewritten Keccak kernel to run fully on registers and partially reversed last round
|
7 years ago |
m05000_a3-optimized.cl
|
OpenCL Kernels: Rewritten Keccak kernel to run fully on registers and partially reversed last round
|
7 years ago |
m05100_a0-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m05100_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m05100_a1-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m05100_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m05100_a3-optimized.cl
|
OpenCL Kernels: Reactivate Dalibors XOR optimization on MD5_H on all MD5 based algorithms
|
7 years ago |
m05100_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m05200.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m05300_a0-optimized.cl
|
Improve some NVidia specific inline assembly
|
7 years ago |
m05300_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m05300_a1-optimized.cl
|
Improve some NVidia specific inline assembly
|
7 years ago |
m05300_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m05300_a3-optimized.cl
|
Improve some NVidia specific inline assembly
|
7 years ago |
m05300_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m05400_a0-optimized.cl
|
Improve some NVidia specific inline assembly
|
7 years ago |
m05400_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m05400_a1-optimized.cl
|
Improve some NVidia specific inline assembly
|
7 years ago |
m05400_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m05400_a3-optimized.cl
|
Improve some NVidia specific inline assembly
|
7 years ago |
m05400_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m05500_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m05500_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m05500_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m05500_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m05500_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m05500_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m05600_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m05600_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m05600_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m05600_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m05600_a3-optimized.cl
|
Improve some NVidia specific inline assembly
|
7 years ago |
m05600_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m05800-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m05800.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06000_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m06000_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m06000_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06000_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06000_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06000_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06100_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m06100_a0.cl
|
Fix whirlpool pure kernel in -a 0 mode
|
7 years ago |
m06100_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06100_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06100_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06100_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06211.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06212.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06213.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06221.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06222.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06223.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06231.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06232.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06233.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06300-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06300.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06400.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06500.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06600.cl
|
Add missing NEW_SIMD_CODE in -m 6600
|
7 years ago |
m06700.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06800.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06900_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m06900_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m06900_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07000_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m07000_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m07000_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07000_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07000_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07000_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07100.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07300_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m07300_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m07300_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07300_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07300_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07300_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07400-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07400.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07500_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m07500_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m07500_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07500_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07500_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07500_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07700_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m07700_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07700_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07800_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m07800_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07800_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m07900.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08000_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m08000_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08000_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08100_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m08100_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m08100_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08100_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08100_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08100_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08200.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08300_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m08300_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m08300_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08300_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08300_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08300_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08400_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m08400_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m08400_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08400_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08400_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08400_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08500_a0.cl
|
Refactor some u32x to u32 where u32x is not needed
|
7 years ago |
m08500_a1.cl
|
Refactor some u32x to u32 where u32x is not needed
|
7 years ago |
m08500_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08600_a0.cl
|
Fix some use of pw_t tmp variable
|
7 years ago |
m08600_a1.cl
|
Refactor some u32x to u32 where u32x is not needed
|
7 years ago |
m08600_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08700_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m08700_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08700_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08800.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m08900.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09000.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09100.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09400.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09500.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09600.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09700_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m09700_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09700_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09710_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m09710_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09710_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09720_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m09720_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09720_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09800_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m09800_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09800_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09810_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m09810_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09810_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09820_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m09820_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09820_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09900_a0-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m09900_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m09900_a1-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m09900_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m09900_a3-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m09900_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m10100_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m10100_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m10100_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m10300.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m10400_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m10400_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m10400_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m10410_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m10410_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m10410_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m10420_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m10420_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m10420_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m10500.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m10700-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m10700.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m10800_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m10800_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m10800_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m10800_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m10800_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m10800_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m10900.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11000_a0-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m11000_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m11000_a1-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m11000_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11000_a3-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m11000_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11100_a0-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m11100_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m11100_a1-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m11100_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11100_a3-optimized.cl
|
Fix some double variable declarations
|
7 years ago |
m11100_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11200_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m11200_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m11200_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11200_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11200_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11200_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11300.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11400_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m11400_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11400_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11500_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m11500_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11500_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11600.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11700_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m11700_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11700_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11800_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m11800_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11800_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m11900.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m12000.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m12200.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m12300.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m12400.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m12500.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m12600_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m12600_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m12600_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m12600_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m12600_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m12600_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m12700.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m12800.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m12900.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13000.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13100_a0-optimized.cl
|
Remove unused truncate_block_xxx_xx() functions and update kernels to use the _S function
|
7 years ago |
m13100_a0.cl
|
Remove unused truncate_block_xxx_xx() functions and update kernels to use the _S function
|
7 years ago |
m13100_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13100_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13100_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13100_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13200.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13300_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m13300_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m13300_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13300_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13300_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13300_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13400.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13500_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m13500_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m13500_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13500_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13500_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13500_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13600.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13751.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13752.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13753.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13800_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m13800_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m13800_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13800_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13800_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13800_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13900_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m13900_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m13900_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13900_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13900_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m13900_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14000_a0.cl
|
Make -m 14000 a pure kernel only and add volatile for asm statement
|
7 years ago |
m14000_a1.cl
|
Make -m 14000 a pure kernel only and add volatile for asm statement
|
7 years ago |
m14000_a3.cl
|
Make -m 14000 a pure kernel only and add volatile for asm statement
|
7 years ago |
m14100_a0.cl
|
Make -m 14100 a pure kernel only
|
7 years ago |
m14100_a1.cl
|
Make -m 14100 a pure kernel only
|
7 years ago |
m14100_a3.cl
|
Make -m 14100 a pure kernel only
|
7 years ago |
m14400_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m14400_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m14400_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14400_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14400_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14400_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14611.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14612.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14613.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14621.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14622.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14623.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14631.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14632.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14633.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14641.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14642.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14643.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14700.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14800.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14900_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m14900_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m14900_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m15000_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m15000_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m15000_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m15000_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m15000_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m15000_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m15100.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m15300.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m15400_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m15400_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m15400_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m15500_a0-optimized.cl
|
Limit kernel-loops in straight-mode to 256, therefore allow rules to be stored in constant memory
|
7 years ago |
m15500_a0.cl
|
Optimized a0 pure kernel for AMD
|
7 years ago |
m15500_a1-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m15500_a1.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m15500_a3-optimized.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m15500_a3.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m15600.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m15700.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
m15800.cl
|
Refactor use of __constant to match up with the user selected attack mode
|
7 years ago |
markov_be.cl
|
Switch the datatypes of the variables responsible for work-item count and work-item size from u32 to u64
|
7 years ago |
markov_le.cl
|
Switch the datatypes of the variables responsible for work-item count and work-item size from u32 to u64
|
7 years ago |