From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: 103376,19924f2facf8443
X-Google-Attributes: gid103376,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news3.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "Alex R. Mosteo" <devnull@mailinator.com>
Newsgroups: comp.lang.ada
Subject: Re: Larger matrices
Date: Thu, 07 Aug 2008 14:35:38 +0200
Message-ID: <6g08gqFdle1aU1@mid.individual.net>
References: <40ed91c2-3dab-4994-9a7b-4032058f0671@56g2000hsm.googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
X-Trace: individual.net g75ubEaBE4xxKk3eUvn+CgA8v7G5JZ5pxmWbM6BQdSDYDqERY=
Cancel-Lock: sha1:vpEHanjLZW6REMBOfBUtIvCylyM=
User-Agent: KNode/0.10.9
Xref: g2news1.google.com comp.lang.ada:1502
Date: 2008-08-07T14:35:38+02:00
List-Id: <comp.lang.ada>

amado.alves@gmail.com wrote:

> I manage to process 1000 x 1000 matrices with the respective Ada 2005
> standard library with GNAT GPL 2008. Processing includes
> multiplication by a vector.
> 
> Now I want larger matrices, say 5000 x 5000. The objects seem to be
> allocated ok (dynamically), but mutiplication gives a "segmentation
> fault."
> 
> Any tips on how to overcome this?

I will give you all the tips I remember on how to get larger stacks (in linux),
but I'm going from memory so you'll have to double-check:

ulimit -s unlimited at the shell level.

Wrap your program, if not already, in a task to be able to use pragma
Storage_Size for this task. I see in other posts that there are switches in
order to set the stack size of the environment task; make your choice.

The linker settings are the fuzziest part. This old thread can put you in the
good track:

http://groups.google.com/group/comp.lang.ada/browse_thread/thread/73c865853bdc4937

In particular the first reply mentions arguments to the linker that ring a bell
to me, although I'm sure to have seen at least an alternate suggestion for a
set of linker options dealing with the stack.