As well Linux kernel have direct patches from Intel and probably from AMD. FPC
is not in race to outrun some. I have in mind to break one to one relationship
of TAsmOp={$i x8664op.inc} and InsProp : array[tasmop] of TInsProp = {$i
x8664pro.inc} That's what my question is about. ----- Reply to message -----
Subject: Re: [fpc-devel] APX instruction set Date: trešd., 2025. g. 21. maijs
21:37 From: J. Gareth Moreton via fpc-devel < fpc-devel@lists.freepascal.org>
To: < fpc-devel@lists.freepascal.org> FPC is always going to be a bit behind
the curve because gcc, for example, has corporate sponsors. Heck, when I
interviewed for a role at ARM (which I didn't get), they made clear that they
help develop GCC and LLVM directly. Can't easily compete with the actual CPU
manufacturers contributing code! Still, we do our best. One thing I'm trying
to work on at the moment is auto-vectorisation. Currently it's just for
x86_64, but keeping things as generic as possible for AArch64 support too, and
of course, for future Intel instruction sets. Kit _______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
