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,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 2002:a24:3303:: with SMTP id k3-v6mr298630itk.2.1541601574584;
        Wed, 07 Nov 2018 06:39:34 -0800 (PST)
X-Received: by 2002:aca:37c1:: with SMTP id e184-v6mr44686oia.5.1541601574337;
 Wed, 07 Nov 2018 06:39:34 -0800 (PST)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.166.215.MISMATCH!z5-v6no589061ite.0!news-out.google.com!n199-v6ni503itn.0!nntp.google.com!z5-v6no589060ite.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Wed, 7 Nov 2018 06:39:34 -0800 (PST)
In-Reply-To: <c9ad838b-c59d-4eaf-86f1-ab4eea3c0ef7@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=158.110.28.161;
 posting-account=9fwclgkAAAD6oQ5usUYhee1l39geVY99
NNTP-Posting-Host: 158.110.28.161
References: <3342c624-59c2-4315-8433-a243e483a2e8@googlegroups.com>
 <c9ad838b-c59d-4eaf-86f1-ab4eea3c0ef7@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <258737e7-e243-47a4-87df-3da25fd6d92c@googlegroups.com>
Subject: Re: Body mistaken for specs
From: mockturtle <framefritti@gmail.com>
Injection-Date: Wed, 07 Nov 2018 14:39:34 +0000
Content-Type: text/plain; charset="UTF-8"
Xref: reader02.eternal-september.org comp.lang.ada:54788
Date: 2018-11-07T06:39:34-08:00
List-Id: <comp.lang.ada>

On Tuesday, November 6, 2018 at 6:39:51 PM UTC+1, briot.e...@gmail.com wrote:
> I had indeed a similar error with a compiler that was from 2017-06.
> I had reported that to AdaCore on 2018-05, and it was already fixed in the versions at the time.
> 
> So it might indeed be fixed in the 2017 GPL version, but was buggy in 2016.
> It might also not have made it to a public version yet (I am a supported customer so get access to more recent versions)
> 
> Emmanuel

After a while I have been able to download ad install the latest version and the problem disappeared, so yes, it was a bug.  I wanted to reply to my own question with the result, but I can get on cla joust now.

Riccardo