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?

[Simon Wright <simon@pushface.org>]

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).