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 <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Precisely why can't official FSF GNAT maintainers copy bug fixes
 in GNAT & its GCC-contained runtime en masse from GNAT GPL Community Edition?
Date: Sat, 05 May 2018 22:46:49 +0100
Organization: A noiseless patient Spider
Message-ID: <ly6041zsfq.fsf@pushface.org>
References: <9c3a75d6-a01f-4cfa-9493-10b8b082ead8@googlegroups.com>
	<114db2c4-1e8c-4506-8d7c-df955dd9f808@googlegroups.com>
	<87d0yc1lsq.fsf@nightsong.com>
	<a181b4df-ceec-4d3e-8669-19ee8f268e56@googlegroups.com>
	<878t901jp4.fsf@nightsong.com>
	<bb2cbfdf-abb3-4b59-9ded-ce27bb98144b@googlegroups.com>
	<pchk2s$co5$1@dont-email.me> <lyr2mrz8mx.fsf@pushface.org>
	<pci51h$uir$2@dont-email.me>
	<670085384.547216974.759926.laguest-archeia.com@nntp.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Info: reader02.eternal-september.org;
 posting-host="4e9ac54f5fe97487ef701cdb12a6f4d6";
	logging-data="10767"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX19FwHBceDhJ7HyIo3YvtZek5wvK5ARTA8o="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (darwin)
Cancel-Lock: sha1:jzkPSxmgbwy1GxSKZzVPBDGFp24=
	sha1:6p+/dDsm0YoEv6PxHDIBw4aGVXI=
Xref: reader02.eternal-september.org comp.lang.ada:52020
Date: 2018-05-05T22:46:49+01:00
List-Id: <comp.lang.ada>

Luke A. Guest <laguest@archeia.com> writes:

> Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> wrote:
>
>> Yes, that would be a far better way to put it, thanks.
>> 
>> What I was trying to say was that there are two distinct versions
>> of the GNAT compiler and that changes are pushed in one direction only.
>
> It’s more likely to be three branches with the CODE flowing like:
>
> GNAT Pro -> GNAT GPL -> FSF GNAT

Considering the timing, I'd think each GPL release is a bookmark (tag)
in the GNAT Pro repo, somewhat after the Pro=>FSF merge.

Hard to say really about the relative dates: GCC 8.1.0 has just been
released, and there has been no massive activity in the repo since. Only
a few days, though, give it time!

Things do happen between releases, though: for instance, when I started
following GCC 8 for Cortex GNAT RTS, the interface for task creation in
s-tarest.ads was the same as GPL 2017; now it isn't
(Create_Restricted_Task has new parameter Sec_Stack_Address).