Re: error: memory exhausted or requested size too large for range of Octave's index type --

[c.]

On 15 Mar 2011, at 22:04, Przemek Klosowski wrote:

> On 03/15/2011 02:43 PM, Martin Helm wrote:
> 
>> Not a problem at all with 32 bit octave if you use version 3.4 since only the
>> index is limited to 2e9 not the bytesize of the array. An array can have up 
>> to
>> 16 GB (if you have enough RAM + Swap).
> 
> I don't understand that---in a 32-bit environment, the virtual address of 
> each process is limited to 32 bits i.e. 4GB. It's true that you can have 
> multiple processes, each with 32-bit address space, that span 36-bit (64GB) 
> physical memory, but that doesn't help octave.

I think what Martin meant is that you can compile a 64bit version of octave 
whithout enabling 64bit integer indices
so the process will be able to allocate more than 4GB even though the maximum  
size of any single array will still be limited.

> p.klosowski
c.