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
