Dhiru Kholia

Thanks to @claudioandre and @magnumripper, our automated MinGW builds work well now. The only remaining problem with them is that they are not fully optimized (only SSE2, no SSE4, no...

I am going to try https://github.com/magnumripper/JohnTheRipper/wiki/Fallback-binary-chains for MinGW builds too. Once this experiment is successful, we can recommend the MinGW builds to end-users (and close this task).

Testing AVX + AVX2 MinGW builds on Windows 10 64-bit, With AVX, all formats work fine. ``` > ..\run\john.exe --test --format=dmg Will run 4 OpenMP threads Benchmarking: dmg, Apple DMG...

I see, my math was quite off! Can this misalignment explain why the AVX2 build is crashing? Is there something we can do to ensure correct alignment of the data...

It seems that this GCC option does not work with MinGW stuff, ``` $ cat config.log ... configure:4223: checking whether the C compiler works configure:4245: x86_64-w64-mingw32-gcc -mavx2 -mpreferred-stack-boundary=5 conftest.c >&5...

The AVX2 john binary works fine under Wine for descrypt, bsdicrypt and md5crypt (surprising) but it crashes for LM. ``` $ wine john.exe --test ... Benchmarking: LM [DES 256/256 AVX2-16]......

MinGW GCC version is `mingw64-gcc-6.3.0-1.fc25.x86_64`. I can try using MinGW GCC 7.2 which should be installable on our CircleCI build bot. Update: I think in order to test MinGW GCC...

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412 is relevant to this topic. The problem seems complex, and also is unfixed so far.

https://github.com/tpoechtrager/wclang (clang based cross-compiler) - this can be a possible workaround for this problem.

Yes, MinGW does not support `fork` stuff IIRC. Even if we use Cygwin, the AVX2 alignment problem with GCC + Windows combination will remain, correct? I am not sure if...