Skip to content

Commit 3906575

Browse files
committed
Fix a weird problem with handling LWS/GWS reporting
For some reason, bcrypt-opencl's LWS/GWS reporting triggered failure even though there was no problem at all. For the life of my I can't figure out why only bcrypt had the problem - other formats report it the same.
1 parent 7f03e7a commit 3906575

File tree

2 files changed

+3
-2
lines changed

2 files changed

+3
-2
lines changed

.mailmap

+2-2
Original file line numberDiff line numberDiff line change
@@ -6,5 +6,5 @@
66
#
77
88
9-
magnum <john.magnum@hushmail.com> <magnum>
10-
9+
magnum <magnumripper@hushmail.com> <magnum>
10+

jtrts.pl

+1
Original file line numberDiff line numberDiff line change
@@ -819,6 +819,7 @@ sub pot_match_pass {
819819
if (index($line, "Will run ") == 0 && index($line, "OpenMP") > 0) { return 1; }
820820
if (index($line, "Node numbers ") == 0) { return 1; }
821821
if (index($line, "Local worksize") == 0) { return 1; }
822+
if (index($line, "LWS") == 0) { return 1; }
822823
if (index($line, "guesses: ") == 0) { return 1; }
823824
if (index($line, "../run/john") == 0) { return 1; }
824825
my $idx = index($line, " (");

0 commit comments

Comments
 (0)