The Octane is (and always was) a 64bit system (native o64, with n32 supported). 
If you ran this on an SGI O2, it would come up as 32bit (but same MIPS4 CPU 
family), with n32 only. 
The "n32" datatype is really a "compatibility type" to efficiently run 32bit 
apps on that 64bit CPU. 
The "o32" is what the older MIPS I and MIPS II 32bit CPUs (e.g. R2000) would 
natively run, they would not be able to run n32. 
Starting with MIPS III the CPUs were 64bit and supported n32, but not all of 
them would do 64bit (the native o64 type) based on their hardware architecture 
and IRIX kernel flavor (those would not be IRIX64). 
I'm not aware of a "n64" ABI type for SGI Irix, this sounds more like the NEC 
VR300i CPU (afaik not used in SGI workstations). 

In the past (that means up to Pd0.40) I have forced Pd installs to n32 (what 
pd_irix6 used) and that's also what the configure script defaulted to for 
Pd0.56 (so I left it at that). 
I can gladly re-visit the 64bit ABI, since Pd can do that now, hopefully I 
don't run into any dependencies that only support n32. Not sure if that buy any 
extra performance (actually it might be opposite for some operations). 

Will get you more of the requested info later. 

Wolfgang
---
[email protected] - the Pure Data mailinglist
https://lists.iem.at/hyperkitty/list/[email protected]/message/SF4HRETB3Q2XL2ZR2AUVBLYMBPMB7L7R/

To unsubscribe send an email to [email protected] mailing list
UNSUBSCRIBE and account-management -> https://lists.iem.at/

Reply via email to