Re: ada compiler?

[Georg Bauhaus <rm.tsoh+bauhaus@maps.futureapps.de>]

Ludovic Brenta wrote:
> Georg Bauhaus writes:
>> Heap overflow seems entirely unrelated at first sight, but in
>> two ways it needs to be considered here, I think.
>>
>> First, the -fstack-check warning suggests, in a sense, to use allocators
>> and pointers instead of direct objects. When a programmer interprets
>> the warning this way and starts using pointers, -f[no]-stack-check
>> is likely to affect the structure of his/her Ada program.
> 
> No, I don't think -fstack-check suggests changing the program in any
> way. 

(I thought that the *warning* might suggest that. Like so:
Ehr, not reliable when stack checking is turned on and the
local array is not trivially small? Uhm, o.K., o.K., then
I will use an allocator instead. After all, Ada culture
asks you to be serious about compiler warnings.)

Anyway, some hints in here:
http://gcc.gnu.org/ml/gcc-patches/2006-11/msg01846.html

Perhaps -fstack-check warning is temporary and platform dependent;
can affect interfacing to C programs; introduces surprises when
moving to another platform; makes Ada reputation--to not
generate SEGV but an exception and such--depend on knowing the
switches; ...

My vote would be cast for at least the effect of -gnato in Debian GNAT.
Maybe the gnat installation script can display a warning box
brining this to Debian Ada users' attention.

Big thanks for bringing this up!