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,fb264cdd67c2f20f
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Newsgroups: comp.lang.ada
Subject: Possibly fixed in gcc 4.1.1,
 but bug box -- Was: Re: A smaller self contained test case ...
References: <05lkrrojfd.fsf@hod.lan.m-e-leypold.de>
 <t3k678yz5g.fsf@hod.lan.m-e-leypold.de>
From: M E Leypold
 <development-2006-8ecbb5cc8aREMOVETHIS@ANDTHATm-e-leypold.de>
Date: 26 Jun 2006 23:53:19 +0200
Message-ID: <16veqny46o.fsf_-_@hod.lan.m-e-leypold.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Some cool user agent (SCUG)
NNTP-Posting-Host: 88.72.218.245
X-Trace: news.arcor-ip.de 1151358430 88.72.218.245 (26 Jun 2006 23:47:10
 +0200)
X-Complaints-To: abuse@arcor-ip.de
Path: 
 g2news2.google.com!news2.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsfeed.arcor-ip.de!news.arcor-ip.de!not-for-mail
Xref: g2news2.google.com comp.lang.ada:5086
Date: 2006-06-26T23:53:19+02:00
List-Id: <comp.lang.ada>



Dear All,

I've been able to compile one of the smaller, selfcontained test cases
with gcc-4.1.1 and it looks as if the Read/Write bug has been
fixed. At least I don't get a SIGSEGV any more.

Unfortunately when compiling the larger program, I now get a bug box,
that starts like this:

  +===========================GNAT BUG DETECTED==============================+
  | 4.1.1 (i686-pc-linux-gnu) in create_tmp_var, at gimplify.c:410           |
  | Error detected at sf-choicetables.adb:485:1                              |


Whereas I'll be trying to report _that_ also to whereever, I'm rapidly
running out of temporal resources, so I'll not follow that new issue
to its logical conclusion.

Just as a message to all those that have been responding that I should
use a newer compiler:

 - gcc 3.4 hadn't fixed it yet.

 - With gcc-4.1.1 I first found a problem with the typing, then

 - I found the bug box above.

I've not been expecting anything else, since I've some experience with
maintaining gcc on various platforms and dread out of experience what
will happen if on tries to change the tool chain in just some hours.

Let that be a lesson to those that don't hold dear their old compiler
versions: Changing to new version will just get you new, different
sneaky bugs, not less :-).

Regards -- Markus