That really sounds promising.
All previous Windows builds were done by houz in a virtual machine. As I see by default the build tries to use -march=native and -mtune=native
Now my build machine has an Intel Core i5 4690k, which does indeed support AVX2, and that would explain the phenomena we see (aka: AVX2 instructions in the executable, which fails on non AVX2 hardware)
if u can just render several versions, and we test them (on the same pc i am using also hachintosh, and the there is working, (but no opencl nevermind i am on windows now)
That’s perfect. I have checked and gcc -march=x86-64 -Q --help=target and gcc -mtune=generic -Q --help=target are resulting the same (for all settings), so in fact I think simply I should ahve passed -DBINARY_PACKAGE_BUILD=ON, and that’s would have solved the problem. New build is on it’s way
Some good news: I have convfigured my Hyper-V to use limited processor features set (like not having AVX2). Booting in and launching the original RC2 build I have expereinced the same crash issue as you reported here earlier.
I have now built an -mtune=generic version, and that is working without crash now even with this limited VM. Once @Pascal_Obry confirms that it is working with him as well, we’ll figure out how to share this upated RC2 version with you.