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-Language: ENGLISH,ASCII
X-Google-Thread: 103376,f410c814fc533225
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2002-11-19 13:37:50 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!kibo.news.demon.net!news.demon.co.uk!demon!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: ANNOUNCE: GNAT 3.15p release
Date: 19 Nov 2002 21:37:48 +0000
Organization: Pushface
Sender: simon@smaug.pushface.org
Message-ID: <x7vwun96y1f.fsf@smaug.pushface.org>
References: <Pine.LNX.4.44.0211181830001.1388-100000@aix>
 <ard2ba$6hr$1@s1.read.news.oleane.net>
NNTP-Posting-Host: pogner.demon.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: news.demon.co.uk 1037741869 28673 62.49.19.209 (19 Nov 2002 21:37:49
 GMT)
X-Complaints-To: abuse@demon.net
NNTP-Posting-Date: Tue, 19 Nov 2002 21:37:49 +0000 (UTC)
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1
Xref: archiver1.google.com comp.lang.ada:31116
Date: 2002-11-19T21:37:48+00:00
List-Id: <comp.lang.ada>

"J�r�me Haguet" <jeje66@despammed.com> writes:

> We faced a small problem with gnat 3.15p and -s switch for gnatmake.
> For some compiler switches combinations, it does not recongnize that this is
> the same combination.
> See example above.
> This occurs with linux and windows versions.
> 
> Did I miss some changes in this new version ?
> Did I miss something in the documentation ?

I know this problem occurs on 3.15a1 built for Linux from sources, but
thought it was fixed for 3.15a1 binary for Windows. I believe it's
fixed for Linux in a 3.16 wavefront, but that won't help 3.15p users!

(the Linux/Windows business above may be down to my misinterpretation
of an ACT remark and the symptoms, of course. I did wonder why there
would be a difference ..)

For what it's worth, the problem also exists in GCC 3.3 -- at least if
you use any optimisation.

   smaug.pushface.org[19]$ gnatmake -c -u -s -g user.adb -gnatwaL -f
   gcc -c -g -gnatwaL user.adb
   user.adb:10:18: warning: condition is always False
   user.adb:17:16: warning: condition is always False
   smaug.pushface.org[20]$ gnatmake -c -u -s -g user.adb -gnatwaL   
   gnatmake: object up to date.
   smaug.pushface.org[21]$ gnatmake -c -u -s -g user.adb -gnatwaL -O2
   gcc -c -g -gnatwaL -O2 user.adb
   user.adb:10:18: warning: condition is always False
   user.adb:17:16: warning: condition is always False
   smaug.pushface.org[22]$ gnatmake -c -u -s -g user.adb -gnatwaL -O2
   gcc -c -g -gnatwaL -O2 user.adb
   user.adb:10:18: warning: condition is always False
   user.adb:17:16: warning: condition is always False

You see that [20] correctly realised there was nothing to do.