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:4105:: with SMTP id x5mr4750338ita.33.1546720910293; Sat, 05 Jan 2019 12:41:50 -0800 (PST) X-Received: by 2002:a9d:6f9a:: with SMTP id h26mr1149584otq.0.1546720910055; Sat, 05 Jan 2019 12:41:50 -0800 (PST) Path: eternal-september.org!reader01.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!k10no426995itk.0!news-out.google.com!v71ni432ita.0!nntp.google.com!q69no425944itb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sat, 5 Jan 2019 12:41:49 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=85.168.19.89; posting-account=O_NgcgoAAABs6pgCjroQBmOBL5ZZGPUc NNTP-Posting-Host: 85.168.19.89 References: <2a6929c5-72fa-4d84-953a-44ea4597ab38@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <2aa0a477-1e10-4162-b136-e79db8d068f8@googlegroups.com> Subject: Re: class wide iterable (and indexable) From: George Shapovalov Injection-Date: Sat, 05 Jan 2019 20:41:50 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader01.eternal-september.org comp.lang.ada:55202 Date: 2019-01-05T12:41:49-08:00 List-Id: On Saturday, January 5, 2019 at 9:07:10 PM UTC+1, Simon Wright wrote: > George Shapovalov writes: > > Is this something already well known or should I report this bug to > > AdaCore? > I think you should submit it. This is an ICE, should be of interest to > AdaCore=20 Ok, then I'll try to go about submitting it tomorrow (its getting late here= today already). > even if the circumstances are unusual! Not for me :). This is far from the first gnat bug incidence I observe. One= time it was even much weirder - first it started spitting out compilation = error messages with clearly misplaced line of code references (off by a few= lines, within the block unreachable by the quoted problematic line), and f= inally gave up and went down with another gnat bug message when pushed a bi= t more. At the time, IIRC, I was making another attempt to tie different ty= pe hierarchies together (and I remember child packages affected gnat stabil= ity too, compared to when I tried to pull them all together in one big pack= age instead) while trying to absolutely avoid any code duplication. Similar= to what Dmitry was describing here in this thread only instead of heavy ge= nerics use I was (ab)using interfaces.. But that was already a few years ago, on a much older gnat version (based a= round gcc-4 I think) with both FSF and ACT gnat rather in flux at the momen= t. So I doubt it makes sense at present to try to dig up that code. So, I'll just submit this bug, as it concerns present gnat version (dev-lan= g/gnat-2018-r1 based on gcc-7.3.1 backend).=20