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 10.107.18.200 with SMTP id 69mr2289998ios.87.1516486976383; Sat, 20 Jan 2018 14:22:56 -0800 (PST) X-Received: by 10.157.11.12 with SMTP id a12mr130985ota.8.1516486976313; Sat, 20 Jan 2018 14:22:56 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!paganini.bofh.team!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!w142no1262404ita.0!news-out.google.com!s63ni1867itb.0!nntp.google.com!g80no1262360itg.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sat, 20 Jan 2018 14:22:55 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=173.71.208.22; posting-account=QF6XPQoAAABce2NyPxxDAaKdAkN6RgAf NNTP-Posting-Host: 173.71.208.22 References: <21b6b4fb-4648-419e-ae6c-c361d54eaa2f@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <029acbd1-090f-4f55-b9a0-12610c95eb74@googlegroups.com> Subject: Re: Incomplete type generic formal interactions with Implicit_Dereference From: Jere Injection-Date: Sat, 20 Jan 2018 22:22:56 +0000 Content-Type: text/plain; charset="UTF-8" Xref: reader02.eternal-september.org comp.lang.ada:50032 Date: 2018-01-20T14:22:55-08:00 List-Id: On Saturday, January 20, 2018 at 3:25:34 PM UTC-5, Simon Wright wrote: > Jere writes: > > > At some point it led to a crash in GNAT, which I reported to AdaCore, > > and they said they fixed it in a future rev (side note, do I need to > > report that to the FSF team as well and how if so?). > > I don't know how many FSF GNAT contributors aren't AdaCore people, but > it's not many! This sort of problem (deep in the compiler) isn't very > likely to be solved by non-AdaCore folk. > > I've always felt uncomfortable when I report a bug to AdaCore (which > won't contain proprietary info, since I don't have any) that no one else > can see it. Not sure how reporting it to FSF as well as to AdaCore would > be received; I try to go for one or the other. > > In any case, FSF won't accept reports on GNAT GPL (any more than AdaCore > will accept reports on FSF GCC): you'd need to make sure the bug also > happened with FSF GCC. > > To report a GNAT bug to FSF, set up an account on GCC Bugzilla > , and raise the bug on Product: > gcc, Component: ada. There were actually two bugs. One occurred on both GNAT GPL 2017 and GNAT FSF 7.2 on mingw64/msys2 x86_64 A second one only affected GNAT FSF 7.2 on mingw64/msys2 x86_64 The odd thing is for the second bug, GNAT GPL is 6.3, while the FSF is 7.2, yet the bug was fixed for the GPL version (6.3) and not the FSF version (7.2). I also wasn't sure if I should have reported the bug to FSF directly or to the maker of the mingw64 port of it. Based on your reply, it sounds like I should report that second one to FSF directly? Given that they don't seem to be incorporating bug fixes from GPL into FSF, I am concerned that the first bug I submitted to Adacore may not get fixed in the FSF version. It might, I just don't know since one of the bugs is fixed in an earlier version of GNAT but not a later version.