Quote:
Originally Posted by Loomes
Confirmed. I tried again on Windows 10 64bit with an 7820x using the command line shown above.
|
Thanks for confirmation -- it looks like your CPU & OS supporting avx512.
I've prepared some binaries to narrow this bug --
avx512-bisect2.7z.
x265-0.exe -- 10-bit encoder with commented out all avx512 function pointers (it works on my i7 8700 with --asm avx512 option). It is for check if the bug is before avx512 code is running but the execution path is exactly like in avx512 case.
x265-01.exe -- assigned only first 1/4 function pointers with avx512 code.
x265-02.exe -- assigned only second 1/4 function pointers with avx512 code.
x265-03.exe -- assigned only third 1/4 function pointers with avx512 code.
x265-04.exe -- assigned only last 1/4 function pointers with avx512 code.
Could you test these 5 exe's and report back which works and which not?