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:7699:: with SMTP id g25mr13750346qtr.75.1575899097241; Mon, 09 Dec 2019 05:44:57 -0800 (PST) X-Received: by 2002:aca:1c0d:: with SMTP id c13mr22871692oic.44.1575899096790; Mon, 09 Dec 2019 05:44:56 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.unit0.net!feeder1.cambriumusenet.nl!feed.tweak.nl!209.85.160.216.MISMATCH!g89no9145719qtd.0!news-out.google.com!w29ni686qtc.0!nntp.google.com!g89no9145710qtd.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 9 Dec 2019 05:44:56 -0800 (PST) In-Reply-To: <0f310d51-978b-463a-941e-a8d60b798fcc@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2a02:2ab8:224:1:61e0:1844:acaf:fc7d; posting-account=VpkXKAoAAACJdJbPSrB2RRuO-i3D4Q8l NNTP-Posting-Host: 2a02:2ab8:224:1:61e0:1844:acaf:fc7d References: <9bee64ac-42c4-495e-9ce6-69c306b8e3a5@googlegroups.com> <1f64ab89-81b4-4f26-a414-f3e1f53507ca@googlegroups.com> <0f310d51-978b-463a-941e-a8d60b798fcc@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <5644d8ca-4841-447d-ab61-49b71b4b1094@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: Mon, 09 Dec 2019 13:44:57 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader01.eternal-september.org comp.lang.ada:57697 Date: 2019-12-09T05:44:56-08:00 List-Id: > > That wouldn't be a fair comparison, nor a useful one. >=20 > Quit putting words in my mouth. I never said that all AdaCore customers = have this fix delivered to them today. I effectively said that > 1) we know for a (purported reported) fact that the fix hit AdaCore's int= ernal codebase today; > 2) we can eventually observe the date at which this defect's fix hits FSF= GNAT to see when OP's original symptoms are no longer exhibited by FSF GNA= T. We regularly merge changes in our GNAT repository to the FSF GCC repository (almost every week, as witnessed by the gcc/gcc/ada/ChangeLog file), but al= so have to obey GCC's release schedule and in particular currently GCC is i= n stage 3, which means basically only regressions are fixed, so our changes= are currently on hold and will resume whenever GCC is back to stage 1. See= https://gcc.gnu.org/develop.html#timeline for more details on GCC's releas= e timeline. > 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