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.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 Path: buffer1.nntp.dca1.giganews.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!newspeer1.nac.net!newsfeed.xs4all.nl!newsfeed3a.news.xs4all.nl!xs4all!news.stack.nl!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: GNAT stuck, any idea on how to diagnose it? Date: Mon, 15 Sep 2014 09:25:19 +0200 Organization: cbb software GmbH Message-ID: References: Reply-To: mailbox@dmitry-kazakov.de NNTP-Posting-Host: yj8+JIQUMOEawvIM7K49kA.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: 40tude_Dialog/2.0.15.1 X-Notice: Filtered by postfilter v. 0.8.2 Xref: number.nntp.dca.giganews.com comp.lang.ada:189009 Date: 2014-09-15T09:25:19+02:00 List-Id: On Sun, 14 Sep 2014 21:45:16 +0000 (UTC), anon@att.net wrote: > One explanation is in translating Ada into the "GCC IR" code the > "gigi" may use or alter the code that makes it difficult for the > GCC optimization to process. Interesting. My impression based on how I dealt with the problem was that it was not the compiler or the code generator which grabbed memory. Maybe it was the symbols cross reference and other stuff that helped generating error messages and prompts. For example, making a separate body or splitting off a child package does not help. I seems that it must be a distance of two or more packages apart from the offending body. So my wild guess was that GNAT grabbed all symbols from all packages at the distance 1, even from the invisible ones and their bodies or ones referenced from the bodies to make suggestions on an error, but did not do that for the packages at the distance 2. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de