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=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:ac8:7b45:: with SMTP id m5mr30498041qtu.360.1575979924997; Tue, 10 Dec 2019 04:12:04 -0800 (PST) X-Received: by 2002:aca:3b54:: with SMTP id i81mr3745509oia.155.1575979924591; Tue, 10 Dec 2019 04:12:04 -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.160.216.MISMATCH!g89no509924qtd.0!news-out.google.com!w29ni821qtc.0!nntp.google.com!g89no509923qtd.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 10 Dec 2019 04:12:04 -0800 (PST) In-Reply-To: <5644d8ca-4841-447d-ab61-49b71b4b1094@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=82.254.97.253; posting-account=VpkXKAoAAACJdJbPSrB2RRuO-i3D4Q8l NNTP-Posting-Host: 82.254.97.253 References: <9bee64ac-42c4-495e-9ce6-69c306b8e3a5@googlegroups.com> <1f64ab89-81b4-4f26-a414-f3e1f53507ca@googlegroups.com> <0f310d51-978b-463a-941e-a8d60b798fcc@googlegroups.com> <5644d8ca-4841-447d-ab61-49b71b4b1094@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <5ea6d000-7e6a-44b0-b988-b36fc157de83@googlegroups.com> Subject: Re: yes another gnat bug (inherited tagged type as record field is too much for gnat??) From: charlet@adacore.com Injection-Date: Tue, 10 Dec 2019 12:12:04 +0000 Content-Type: text/plain; charset="UTF-8" Xref: reader01.eternal-september.org comp.lang.ada:57704 Date: 2019-12-10T04:12:04-08:00 List-Id: > > 3) we can then accurately calculate the time that it empirically can take for a fix to defect to actually get released to the wild in FSF GNAT. > > You also need to take into account GCC's release constraints, see above. > > Arno Actually I mixed stage 3 and 4, so never mind the above in this case: we're in stage 3 which is general bug fixes and we'll do a merge of our changes soon :-) stage 4