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: Thu, 03 May 2018 22:48:23 +0100
Organization: A noiseless patient Spider
Message-ID: <lyk1sk1kd4.fsf@pushface.org>
References: <9c3a75d6-a01f-4cfa-9493-10b8b082ead8@googlegroups.com>
	<114db2c4-1e8c-4506-8d7c-df955dd9f808@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Info: reader02.eternal-september.org;
 posting-host="78d2d68a408b43f79301a0588058ab88";
	logging-data="32584"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX19g8d0RA58myW+xS4dhpW8aqyPMvCE1VNE="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (darwin)
Cancel-Lock: sha1:4CCV0QT4oLFYiq0s2Q09FKlhZY8=
	sha1:alUtLGvHqqxuq8LhmyALW1gLZWk=
Xref: reader02.eternal-september.org comp.lang.ada:51949
Date: 2018-05-03T22:48:23+01:00
List-Id: <comp.lang.ada>

"Dan'l Miller" <optikos@verizon.net> writes:

> … or brand new features, for that matter?
>
> Precisely why can't official FSF GNAT maintainers copy bug fixes ••and
> brand new features•• in GNAT & its GCC-contained runtime en masse from
> GNAT GPL Community Edition?

I haven't read much of your walls of text (where do you find the time?)
but this is confused.

-----------------

(1) Someone (Randy? one of us?) finds a bug in CE & reports it to
AdaCore.

(2a) It's already fixed in their internal repo: they may tell the
reporter.

(2b) It's new. Entered into their tracking system, prioritised, fixed.

(3) It's released to their customers. Repeat from (1) until ...

(4) Feature freeze for CE release.

-----------------

(1) Start of new FSF major release: grand port of AdaCore changes to FSF
repo.

(2) Integration with parallel changes in GCC backend etc

(3) People build for their weird architectures (incl. Darwin! my
personal interest), find & report problems; sometimes they propose
patches, sometimes they get accepted (internal compiler errors and
bootstrap failures get priority)

(3a) I hove no evidence for this, but I'd expect that serious bugs get
fed back to AdaCore's own system.

(3b) Nor have I evidence that new AdaCore work trickles through into the
FSF system. I did report one bug (80888) and submitted a patch; when the
code was eventually patched, an AdaCore engineer had developed an
identical patch. Not bitter, no! so long as the product is improved.

(4) Repeat from (2) until ...

(5) Release (current is 8.1, just yesterday).

(6) Repeat from (2) for minor releases (next will be 8.2).

-----------------

The thing to remember that AdaCore don't have separate people working on
customer, CE, or FSF compilers.