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,be7fa91648ac3f12 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news3.google.com!news.glorb.com!wn14feed!worldnet.att.net!12.120.4.37!attcg2!attcg1!ip.att.net!news.binc.net!kilgallen From: Kilgallen@SpamCop.net (Larry Kilgallen) Newsgroups: comp.lang.ada Subject: Re: Large arrays (again), problem case for GNAT Date: 13 Apr 2005 08:10:49 -0500 Organization: LJK Software Message-ID: References: NNTP-Posting-Host: eisner.encompasserve.org X-Trace: grandcanyon.binc.net 1113397799 2048 192.135.80.34 (13 Apr 2005 13:09:59 GMT) X-Complaints-To: abuse@binc.net NNTP-Posting-Date: Wed, 13 Apr 2005 13:09:59 +0000 (UTC) Xref: g2news1.google.com comp.lang.ada:10416 Date: 2005-04-13T08:10:49-05:00 List-Id: In article , "Dr. Adrian Wrigley" writes: > Hi guys! > > A month or two back I hinted that I had been having problems > the GNAT code accessing large data structures. It seemed that > incorrect code was silently being generated. Since I didn't > have a test case available, no progress could be made. > > I have encountered the problem again, and produced a test case. > > In summary: > > Certain uses of arrays over about 800MB cause code to fail. > In particular, 'Address is sometimes incorrect > Accessing high elements is incorrect, depending on exact code to > generate the index. > > The problems only seem to occur if the upper bound of the array > is compile-time constant. > > Can someone test this on later versions of GNAT please? Later than what ?