Re: ada compiler?

[Ludovic Brenta <ludovic@ludovic-brenta.org>]

Georg Bauhaus wrote:
> Jacob Sparre Andersen wrote:
> > I can only remember a _warning_ about a too big stack frame; not a
> > plain compilation error.  Are you sure programs actually don't compile
> > because of too big stack frames in some cases?

You are correct; it is only a warning. However, if one subprogram has
"unreliable" (whatever that means) stack checking, then the entire
program has "unreliable" stack checking and I'm not sure it is a good
idea to turn that on by default. Also, if a stack overflow results in
a SEGV (instead of Storage_Error), I don't clearly see the functional
difference i.e. the stack overflow gets caught either way. Unless of
course I'm missing something.

> The message says something to the effect that stack checking
> won't be reliable with large stack frames (where large seems
> to start at N_000 sized arrays, say).
>
> Also, -fstack-check is a GCC option, not GNAT-specific.

Yes and as with all -f options in GCC, one can explicitly turn it off
with -fno-stack-check.

> Maybe some
> new technology is built into GCC (speculation); as always, most
> GCC technologists get inspiration from the Pascal branch of
> languages--later.

Agreed.

--
Ludovic Brenta.