[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Memory exaustion or size too large for index
From: |
Carlo de Falco |
Subject: |
Re: Memory exaustion or size too large for index |
Date: |
Thu, 25 Feb 2010 12:28:34 +0100 |
On 25 Feb 2010, at 11:47, Jaroslav Hajek wrote:
In 3.2.x with 32-bit indexing, the limit is 2GB of memory per array.
The development version has this fixed and the limit is 2^31 elements
per array (so it's 16GB for double real matrix).
mmmhh... you mean the limit is 16GB even if octave is compiled without
--enable-64 ?
with the current development sources (pulled yesterday) indeed
>> version
ans = 3.3.50+
>> a=zeros (1024, 1024, 1024);
does not give a "memory exhausted" error but
>> a(1,1,1)
ans = -2.0000
and
>> whos a
Variables in the current scope:
Attr Name Size Bytes Class
==== ==== ==== ===== =====
a 1024x1024x1024 0 double
Total is 1073741824 elements using 0 bytes
I've built octave on MacOS X 10.5 using gcc 4.2.1 and gfortran 4.2.3
c.
- Memory exaustion or size too large for index, Carnë Draug, 2010/02/24
- Re: Memory exaustion or size too large for index, Jaroslav Hajek, 2010/02/25
- Re: Memory exaustion or size too large for index,
Carlo de Falco <=
- Re: Memory exaustion or size too large for index, Jaroslav Hajek, 2010/02/25
- Re: Memory exaustion or size too large for index, Carlo de Falco, 2010/02/25
- Re: Memory exaustion or size too large for index, Jaroslav Hajek, 2010/02/25
- Re: Memory exaustion or size too large for index, Carlo de Falco, 2010/02/25
- Re: Memory exaustion or size too large for index, Jaroslav Hajek, 2010/02/25
- Re: Memory exaustion or size too large for index, Carlo de Falco, 2010/02/25
- Re: Memory exaustion or size too large for index, Carlo de Falco, 2010/02/25
- Re: Memory exaustion or size too large for index, Jaroslav Hajek, 2010/02/25
- Re: Memory exaustion or size too large for index, Carlo de Falco, 2010/02/25
- Re: Memory exaustion or size too large for index, Jaroslav Hajek, 2010/02/25