Joey, As you figured out, the machine where it failed does not have avx. Bill pointed out that on linux
...> cat /proc/cpuinfo | grep avx makes this clear. I have not found similar simple ways to determine this on OSX or Windows. I didn't want to delay the beta for this reason, and this needs work. Even in a non-avx binary the code to detect this is surprising complicated and hard to test. For example, hardware may support it, but an older version of an OS doesn't support the required kind of task switch. Your cat/'proc/cpuinfo could report avx and the avx binary would still crash because of lack of OS support. This was complicated by the fact that when doing the release I temporarily didn't have a non-avx machine on which to test. The avx verb does a shell launch of jconsole to run the avx binary with a test that exercises the avx code. I incorrectly thought this would fail on a non-avx machine in a gentler way and avx would report the failure. But I couldn't test it. I have now rounded up an older machine and will make avx verb better behaved in this respect. Again, thanks for the prompt feedback. On Sun, Mar 12, 2017 at 8:36 AM, Eric Iverson <[email protected]> wrote: > Ric, Joey, > > Thanks for the prompt feedback. > > You both report having to update addons before avx was defined. This is > because you guys took some shortcuts in the detail install steps. You went > to running avx in your first 806 session. Too eager! The install steps does > an update of all addons and creates launch icons. If you then stopped J and > restarted you would get the new installer with avx defined. > > > > On Sun, Mar 12, 2017 at 4:23 AM, Joey K Tuttle <[email protected]> wrote: > >> Seems not ... >> >> jkt@set1:~$ cat /proc/cpuinfo | grep avx >> jkt@set1:~$ >> >> No surprise, it's a few years old - >> >> jkt@set1:~$ cat /proc/cpuinfo >> processor : 0 >> vendor_id : GenuineIntel >> cpu family : 6 >> model : 30 >> model name : Intel(R) Xeon(R) CPU X3430 @ 2.40GHz >> >> But it would be good to have a more informative report from avx '' >> >> - joey >> >> > On 2017Mar 12, at 00:16, bill lam <[email protected]> wrote: >> > >> > You can first confirm if your linux box support avx or not, eg >> > >> > cat /proc/cpuinfo | grep avx >> > >> >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm >> > > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
