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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,6b93224dbe2bb55b X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.224.173.202 with SMTP id q10mr6738314qaz.3.1354582786929; Mon, 03 Dec 2012 16:59:46 -0800 (PST) Received: by 10.49.60.40 with SMTP id e8mr2596472qer.40.1354582786905; Mon, 03 Dec 2012 16:59:46 -0800 (PST) Path: gf5ni47564750qab.0!nntp.google.com!c8no133319qao.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 3 Dec 2012 16:59:46 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=201.26.49.235; posting-account=TRgI1QoAAABSsYi-ox3Pi6N-JEKKU0cu NNTP-Posting-Host: 201.26.49.235 References: <3254b304-ed8b-4601-8a3c-ab3df74d84ad@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Return unconstrained types in ZFP From: "Rego, P." Injection-Date: Tue, 04 Dec 2012 00:59:46 +0000 Content-Type: text/plain; charset=ISO-8859-1 Date: 2012-12-03T16:59:46-08:00 List-Id: On Sunday, December 2, 2012 4:13:39 PM UTC-2, Luke A. Guest wrote: > You need to define a small secondary stack, this can be defined in the linker > script and then imported into the correct package. This is the only way to > return unconstrained types. If you look in s-secsta you will see what needs to > be defined, you can implement it in a very basic way, it does not need to be > as complex as the system version. > > Also, you need the memory allocation functions, if AVR Ada provides memcpy, > bzero, etc. just import them, see the runtime sources again for how it does this on Linux. Otherwise, you will have to write your own. I will very keep this info, it sure can be very useful in near future (but now Stephen made a very good suggestion, I am very inclined to use it :-) ). Thanks Luke.