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.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,a32653cf595422e6
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.135.106 with SMTP id pr10mr11450056pbb.3.1335115853939;
        Sun, 22 Apr 2012 10:30:53 -0700 (PDT)
Path: 
 r9ni86242pbh.0!nntp.google.com!news1.google.com!goblin2!goblin.stu.neva.ru!news.internetdienste.de!noris.net!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Date: Sun, 22 Apr 2012 19:30:52 +0200
From: Georg Bauhaus <rm.dash-bauhaus@futureapps.de>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: GNAT and register allocation
References: <4f9138c2$0$6628$9b4e6d93@newsspool2.arcor-online.net>
 	<4f9145b5$0$6557$9b4e6d93@newsspool4.arcor-online.net>
 	<jmrpej$cao$1@speranza.aioe.org>
 	<4f918218$0$6557$9b4e6d93@newsspool4.arcor-online.net>
 <82r4vhi8v4.fsf@stephe-leake.org>
In-Reply-To: <82r4vhi8v4.fsf@stephe-leake.org>
Message-ID: <4f94404c$0$6622$9b4e6d93@newsspool2.arcor-online.net>
Organization: Arcor
NNTP-Posting-Date: 22 Apr 2012 19:30:52 CEST
NNTP-Posting-Host: 5230ee4e.newsspool2.arcor-online.net
X-Trace: 
 DXC=_Ufh8D?ZD:5RadXUBHgFh3A9EHlD;3Yc24Fo<]lROoR18kF<OcfhCO;RL`mA6GinL=nc\616M64>:Lh>_cHTX3j=I7P7CQ;5<d0
X-Complaints-To: usenet-abuse@arcor.de
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date: 2012-04-22T19:30:52+02:00
List-Id: <comp.lang.ada>

On 21.04.12 14:10, Stephen Leake wrote:
> gpr files give you a way to apply different compilation options to
> different files. There are_lots_  of low-level gcc options controlling
> inline and other optimizations; see gnat user guide, section 3.10.

Wasn't there some message saying,
    "cannot inline before body seen"?

So preventing visibility of bodies might be another way of preventing
inline expansion.