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
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail
From: =?windows-1252?Q?Markus_Sch=F6pflin?= <no.spam@spam.spam>
Newsgroups: comp.lang.ada
Subject: Re: How do typical Ada calling conventions work ?
Date: Fri, 21 Aug 2015 12:41:01 +0200
Organization: Aioe.org NNTP Server
Message-ID: <mr6v7s$ouc$1@speranza.aioe.org>
References: <2a592336-034f-4483-9aed-b5a1d997f902@googlegroups.com>
NNTP-Posting-Host: MdpKeRr+sx3LK7JQiK5aNw.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.7.0
X-Notice: Filtered by postfilter v. 0.8.2
Xref: news.eternal-september.org comp.lang.ada:27549
Date: 2015-08-21T12:41:01+02:00
List-Id: <comp.lang.ada>

Am 21.08.2015 um 10:37 schrieb Hadrien Grasland:

> Does someone know how typical Ada implementations manage to cope with this, and if it varies a lot from one implementation to another ?

GNAT allocates such objects on the secondary stack. Quote from the user guide:

---%<---
`-Dnn[k|m]'
This switch can be used to change the default secondary stack size value to a 
specified size nn, which is expressed in bytes by default, or in kilobytes 
when suffixed with k or in megabytes when suffixed with m.

The secondary stack is used to deal with functions that return a variable 
sized result, for example a function returning an unconstrained String. There 
are two ways in which this secondary stack is allocated.

For most targets, the secondary stack is growing on demand and is allocated as 
a chain of blocks in the heap. The -D option is not very relevant. It only 
give some control over the size of the allocated blocks (whose size is the 
minimum of the default secondary stack size value, and the actual size needed 
for the current allocation request).

For certain targets, notably VxWorks 653, the secondary stack is allocated by 
carving off a fixed ratio chunk of the primary task stack. The -D option is 
used to define the size of the environment task's secondary stack.
--->%---