Forgive me for piggy-backing on OP, but would upstream be interested in work on merging the separate non-avx, avx, and avx2 outputs into a single libj.so that auto-detects cpu features at startup and sets up the primitive-to-function map accordingly?
I don't have concrete work in this direction, but I do have some bit of background in doing things like this. As the package manager of J for a couple Linux distros, we have to ship all the binaries anyway and write a wrapper script to detect CPU features at startup anyway, so along this single dimension it would be a win. My question is which way upstream's cost-benefit scale tips when considering everything else. Cheers! Raul Miller <[email protected]> wrote: > Wikipedia concurs: > https://en.wikipedia.org/wiki/List_of_Intel_Core_M_microprocessors > > Also, on a macbook, you can run this command line in terminal to see > what cpu features are supported on your machine: > > sysctl machdep.cpu.features > > Thanks, ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
