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,bdebc54a485c13a4
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.202.168 with SMTP id kj8mr1437296pbc.1.1333009515002;
        Thu, 29 Mar 2012 01:25:15 -0700 (PDT)
Path: 
 z9ni14301pbe.0!nntp.google.com!news2.google.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
From: Ludovic Brenta <ludovic@ludovic-brenta.org>
Newsgroups: comp.lang.ada
Subject: Re: My first compiler bug: work around or redesign?
Date: Thu, 29 Mar 2012 01:25:14 -0700 (PDT)
Organization: http://groups.google.com
Message-ID: <19538743.70.1333009514665.JavaMail.geo-discussion-forums@ynes7>
References: <slrnjmp96d.1lme.lithiumcat@sigil.instinctive.eu>
 <slrnjn1ch7.1lme.lithiumcat@sigil.instinctive.eu>
 <2229037.332.1332788108220.JavaMail.geo-discussion-forums@vbht7>
 <slrnjn6bki.1lme.lithiumcat@sigil.instinctive.eu>
NNTP-Posting-Host: 153.98.68.197
Mime-Version: 1.0
X-Trace: posting.google.com 1333009514 11029 127.0.0.1 (29 Mar 2012 08:25:14
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 29 Mar 2012 08:25:14 +0000 (UTC)
In-Reply-To: <slrnjn6bki.1lme.lithiumcat@sigil.instinctive.eu>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=153.98.68.197;
 posting-account=pcLQNgkAAAD9TrXkhkIgiY6-MDtJjIlC
User-Agent: G2/1.0
Content-Type: text/plain; charset=ISO-8859-1
Date: 2012-03-29T01:25:14-07:00
List-Id: <comp.lang.ada>

Natasha Kerensikova wrote on comp.lang.ada:
> Ludovic Brenta wrote:
>> Report it to the FSF at http://gcc.gnu.org/bugzilla. IMHO, a public bug
>> database is worth a thousand private ones.
> 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52752
> 
> Below is the minimal testcase I have worked out.
> 
> Is there anything I should do at this point? Or will everything leading
> to a fix be handled from there?

Just wait for someone to fix the bug and then consider backporting
the fix into your distribution's version of GNAT.

But Per Sandberg wrote the day before on comp.lang.ada:
> Any way it is reported.

which pointed me to http://gcc.gnu.org/PR52735

So you should indicate that your bug is a duplicate with a more
minimal test case.

-- 
Ludovic Brenta.