re: octave 3.0 / 64bit

[Daniel Heiserer]

hi,

the thread probably started some time ago,
but here are my 2 cents of octave 3.0 features:

As many systems are reaching the 2GB limit
scientific tools should have no problems with 
addressing LARGE memory: ==> 

*** octave should be fully 64bit clean.


I compiled octave 8 months ago on itanium2 (msc-linux)
without any problems. (configure;make;make install; runit)

0) octave could use more then 2GB without any problem
bottleneck was that ONE Object/array could not be larger
then 2GB.

Bottlenecks  to make full usage of arbitrarily large
memory, or at least what mortals could afford nowadays
where:

1) arrays couldn't be larger then 2GB I submitted a
patch from a colleagues work some time ago for that. ==> this
fixes only 2D arrays. Because of the "int4" indexing
of octave, arrays are fixed to 2^31 elements per dimension.

2) replace all "int4" references/indexing by int8/"long long"


-- daniel