Re: gnat and heap size

[erij@online.no]

Dr Adrian Wrigley <amtw@linuxchip.demon.co.uk> writes:

> Erik Johannessen wrote:
> ...
> > The fun part here is that you can stay within the bounds you've
> > declared for the array, but access memory outside of the area
> > allocated for the array.  If you've got other data on the heap after
> > the array you'll get some interesting bugs. :)
> ...
> 
> This seems to be the same problem I had, except I was finding
> unexpected "aliases" between different fields in a record.
> Potentially nasty, because it can happen in otherwise well tested
> code used with unusually large data.  Be aware of and work around
> the various limitations.  Doesn't GNAT 3.14 fix some of these?

As I wrote in my first post, this was tested with gnat-3.14.  I'm not
sure if ACT is aware of this (they should be now).  Our main gnat
person at work wasn't there today so I couldn't write a bug report.

-Erik
-- 
/d{def}def/m{mul}d/a{add}d/q{repeat}d/y 1 d 300{/x 1 d 600{/c x 600 div 4 m 2
sub d/z y 300 div 2 m 1 sub d/r 0 d/i 0 d/t 0 d{t 1 le{/n r r m i i m sub c a
d/b 2 r m i m z a d/r n d/i b d r r m i i m a 16 gt{exit}if} {exit}ifelse/t t 
.01 a d}loop t setgray x y moveto 1 1 rlineto stroke/x x 1 a d}q /y y 1 a d}q