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=ham 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.233.170 with SMTP id tx10mr9088505pbc.0.1335116346697; Sun, 22 Apr 2012 10:39:06 -0700 (PDT) Path: r9ni86257pbh.0!nntp.google.com!news2.google.com!news.glorb.com!feeder.erje.net!nuzba.szn.dk!news.jacob-sparre.dk!munin.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail From: Jacob Sparre Andersen Newsgroups: comp.lang.ada Subject: Re: GNAT and register allocation Date: Sun, 22 Apr 2012 19:39:04 +0200 Organization: Jacob Sparre Andersen Research & Innovation Message-ID: <87aa23d5tz.fsf@adaheads.sparre-andersen.dk> References: <4f9138c2$0$6628$9b4e6d93@newsspool2.arcor-online.net> <4f9145b5$0$6557$9b4e6d93@newsspool4.arcor-online.net> <4f918218$0$6557$9b4e6d93@newsspool4.arcor-online.net> <82r4vhi8v4.fsf@stephe-leake.org> <4f94352f$0$6625$9b4e6d93@newsspool2.arcor-online.net> NNTP-Posting-Host: 212.27.23.251.bredband.3.dk Mime-Version: 1.0 X-Trace: munin.nbi.dk 1335116345 22858 212.27.23.251 (22 Apr 2012 17:39:05 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Sun, 22 Apr 2012 17:39:05 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) Cancel-Lock: sha1:FQCmSvADuLZIDmzWQaXnD9cT9Yk= Content-Type: text/plain; charset=us-ascii Date: 2012-04-22T19:39:04+02:00 List-Id: Georg Bauhaus wrote: >>> I must use one set of options for an entire program in this case. > This requirement is likely a fact (external) that we can't change. But aren't you adhering to the requirement, if you execute "gnatmake -P some_project_file" to build the entire program? Or is it mandated that each child process of "gnatmake" should have the same build options? Do you know (and are you free to tell us) the rationale for the requirement? Greetings, Jacob -- recursive, adj.; see recursive