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,6c7dea22b75ba442
X-Google-Attributes: gid103376,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news4.google.com!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Date: Thu, 15 Nov 2007 10:59:48 +0100
From: Georg Bauhaus <rm.tsoh+bauhaus@maps.futureapps.de>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: ada compiler?
References: <TYbZi.77377$kj1.12383@bgtnsc04-news.ops.worldnet.att.net>
	<QPednZmRA_Te8KjanZ2dnUVZ_jednZ2d@comcast.com>
	<IooZi.12685$if6.3756@bgtnsc05-news.ops.worldnet.att.net>
	<uklh05-6gt.ln1@newserver.thecreems.com>
	<lvsZi.13247$if6.1368@bgtnsc05-news.ops.worldnet.att.net>
	<1194747665.6151.31.camel@K72>
 <_evZi.177931$Xa3.50640@attbi_s22>	<87hcjq46t4.fsf@ludovic-brenta.org>
	<yger6ite2fu.fsf@hugsarin.dmusyd.edu>
	<473abc9d$0$13104$9b4e6d93@newsspool2.arcor-online.net>
	<1195035988.599522.87580@50g2000hsm.googlegroups.com>
	<1195043147.1007.263.camel@kartoffel>
	<1195052954.315227.220840@o3g2000hsb.googlegroups.com>
	<1195056238.1007.317.camel@kartoffel>
	<1195058211.682783.288340@d55g2000hsg.googlegroups.com>
	<1195061973.1007.342.camel@kartoffel> <87zlxg36hx.fsf@ludovic-brenta.org>
In-Reply-To: <87zlxg36hx.fsf@ludovic-brenta.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <473c189a$0$4360$9b4e6d93@newsspool4.arcor-online.net>
Organization: Arcor
NNTP-Posting-Date: 15 Nov 2007 10:59:54 CET
NNTP-Posting-Host: bfc39ead.newsspool4.arcor-online.net
X-Trace: 
 DXC=DoQ2oYL2b@Xf8j24CD<3lP4IUK<Cl32<Q4Fo<]lROoRQ^;5]aA^R6>R;HaXY?nB1aWPCY\c7>ejVX9SmE5741NoT?I`c5o2X?g[
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news1.google.com comp.lang.ada:18418
Date: 2007-11-15T10:59:54+01:00
List-Id: <comp.lang.ada>

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!