Misleading error about AVX-512 generated by DR's own gencode in debug -loglevel 3
On a machine where the processor and OS have AVX-512 support, DR generates this error on every single run in debug build with loglevel 3
:
$ bin64/drrun -loglevel 3 -- suite/tests/bin/simple_app
<log dir=xxx>
<Starting application suite/tests/bin/simple_app (170518)>
<Application suite/tests/bin/simple_app (170518): AVX-512 was detected at PC 0x00007fe7ef872dbc. AVX-512 is not fully supported yet.>
It is coming from the debug build disassembly of DR's own generated code:
fcache_enter:
0x00005636bf2ead00 48 8b c7 mov %rdi -> %rax
...
0x00005636bf2eadae c5 7d 6f bf 80 04 00 vmovdqa 0x00000480(%rdi)[32byte] -> %ymm15
00
0x00005636bf2eadb6 e9 28 01 00 00 jmp $0x00005636bf2eaee3
SYSLOG_ERROR: Application xxx (nnnn): AVX-512 was detected at PC 0x00005636bf2eadbc. AVX-512 is not fully supported yet.
0x00005636bf2eadbb 62 f1 7c 48 28 47 03 vmovaps {%k0} 0xc0(%rdi)[64byte] -> %zmm0
Needless to say this is misleading (this app does not use AVX-512) and noisy.