Re: GLPK memory problem

2022-07-03 Thread Michael Hennebry
This is a bit late. On Wed, 4 May 2022, Domingo Alvarez Duarte wrote: You are right about the maximum index is limited by using an 32 bits integer but that doesn't mean that the memory allocation is also limited, we can have several GigaBytes of allocated memory on 64 bits platforms and still

Re: GLPK memory problem

2022-05-04 Thread Domingo Alvarez Duarte
Hello Andrew ! You are right about the maximum index is limited by using an 32 bits integer but that doesn't mean that the memory allocation is also limited, we can have several GigaBytes of allocated memory on 64 bits platforms and still have less that 2^32 indices. Cheers ! On 4/5/22

Re: GLPK memory problem

2022-05-04 Thread Andrew Makhorin
On Tue, 2022-05-03 at 13:29 +0200, Domingo Alvarez Duarte wrote: > Maybe there is a mistake on the previous reply, GLPK is 32/64 bits  > depending on the compilation/platform/OS on 64 bits operating systems > it  > can allocated more than 4GB of memory. I meant that for indexing arrays glpk

Re: GLPK memory problem

2022-05-03 Thread Domingo Alvarez Duarte
Maybe there is a mistake on the previous reply, GLPK is 32/64 bits depending on the compilation/platform/OS on 64 bits operating systems it can allocated more than 4GB of memory. Can you use gdb to see how much memory was attempted to allocate ? On 3/5/22 13:11, Andrew Makhorin wrote: On

Re: GLPK memory problem

2022-05-03 Thread Andrew Makhorin
On Tue, 2022-05-03 at 06:38 +, Georgios Avgerinopoulos wrote: > Hey Community! >   > Just ran into the following problem >   > >   > glp_alloc: no memory available > Error detected in file ..\src\env\alloc.c at line 91 >   > We've got plenty of memory (both RAM and hard drive). >   > Any