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 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Incomplete type generic formal interactions with Implicit_Dereference Date: Sun, 21 Jan 2018 10:04:15 +0000 Organization: A noiseless patient Spider Message-ID: References: <21b6b4fb-4648-419e-ae6c-c361d54eaa2f@googlegroups.com> <029acbd1-090f-4f55-b9a0-12610c95eb74@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: reader02.eternal-september.org; posting-host="459587e5fa20f1a7eeae94267930dd32"; logging-data="32380"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18bO8F4IYc8RNokOAjmInP6h2AcHc5Nz6Y=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (darwin) Cancel-Lock: sha1:qfnGzeGF/VS+41jj8IbXMEeLHzA= sha1:lNGg8jPn3a+oC62gd3lwNIGOA14= Xref: reader02.eternal-september.org comp.lang.ada:50034 Date: 2018-01-21T10:04:15+00:00 List-Id: Jere writes: > 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. Under those circumstances I'd report the FSF bugs to FSF (I've been tracking the GCC 8 developments so that I can leap in with macOS binaries ASAP after the release!, so I'd check whether the bug was fixed in 8). AdaCore's timeline vs FSF isn't straighforward (there's some not-up-to-date info at [1]). AdaCore produce a Pro release about once a year, which they base on a well-known GCC release (in the case of GNAT GPL 2017, 6.3). This involves changes to Ada front-end code, to the C back-end code, and to the interface between them (and of course to Ada & C in the runtime). FSF GCC begins a new major release phase (currently for 8) also approximately once a year, not synced with AdaCore's releases. What AdaCore do (visibly, anyway) is to port the changes made in their own source tree at that time to the FSF tree; there's commonly a rush of commits at this point. After that, things slow down and bugs get fixed. So one would expect some of the bugs still present in GCC 7 to have been fixed in the GPL 2017 release (and, hopefully, in GCC 8). [1] https://people.debian.org/~lbrenta/debian-ada-policy.html#Timeline-of-GNAT-releases