On 1-4-2022 16:04, Marc Weustink via lazarus wrote:
Indeed, I see what I think are avx512 instructions
Yes, CPUID Feature Flag AVX512F
SSE2 has only the signed version CVTSI2SD
This machine is a Ivy Bridge so has Coreavx ( AVX1) enabled, so some VEX
usage is allowed.
I removed some
On 1-4-2022 15:59, Marc Weustink via lazarus wrote:
On 1-4-2022 14:52, Marco van de Voort via lazarus wrote:
On 1-4-2022 12:57, Marc Weustink via lazarus wrote:
The SIGILL here points more to the generated code I think.
Indeed, I see what I think are avx512 instructions
Yes, CPUID
On 1-4-2022 14:52, Marco van de Voort via lazarus wrote:
On 1-4-2022 12:57, Marc Weustink via lazarus wrote:
The SIGILL here points more to the generated code I think.
Indeed, I see what I think are avx512 instructions
Yes, CPUID Feature Flag AVX512F
0x005afb7a <+90>: call
On 1-4-2022 12:57, Marc Weustink via lazarus wrote:
The SIGILL here points more to the generated code I think.
Indeed, I see what I think are avx512 instructions
0x005afb7a <+90>: call 0x5b1040
0x005afb7f <+95>: mov %eax,-0x10(%ebp)
=> 0x005afb82 <+98>: vcvtusi2sd
The SIGILL here points more to the generated code I think.
Marc
On 1-4-2022 12:43, Marco van de Voort via lazarus wrote:
I rebuilt Lazarus today (FPC trunk 2 days old -lazarus trunk today), and
I suddenly got a GPF while starting.
I ran under GDB and the traceback is:
Thread 1 received
I rebuilt Lazarus today (FPC trunk 2 days old -lazarus trunk today), and
I suddenly got a GPF while starting.
I ran under GDB and the traceback is:
Thread 1 received signal SIGILL, Illegal instruction.
DOAUTOADJUSTLAYOUT (this=0x1cb26440, AMODE=LAPAUTOADJUSTFORDPI,
