Re: ANN: Cortex GNAT RTS 20180419

[Jere <jhb.chat@gmail.com>]

On Saturday, April 28, 2018 at 12:13:14 PM UTC-4, Simon Wright wrote:
> There are three parallel releases at Github[1], for
> 
> * GNAT GPL 2016/GCC 6
> * GCC 7
> * GNAT GPL 2017
> 
> (three, because of changes to the interface between the compiler and the
> RTS).
> 
> There's not much user-visible change from the last GCC 7 release[2],
> except that all but 2k of free store is available for the heap (the 2k
> is used for startup and interrupt stack).
> 
> [1] https://github.com/simonjwright/cortex-gnat-rts/releases
> [2] https://github.com/simonjwright/cortex-gnat-rts/releases/tag/r20171016

Thank you so much for keeping these up to date.  Question:
Do you have any suggestions for pulling out a ZFP from this repo?  I know
it isn't setup for that, but was curious if you had any tips for what
to mainly look for.  I'm not so much worried about changing the ada files,
but I am more interested in what types of changes (if any) should I be
looking to do to the ld file, the gpr file, the xml file, etc.  So mostly
the build system.  I'm probably gonna try and mod the ardiuno one as it
is closest to my chip (an M0+).  Right now, I have been pulling from one
of your older revisions where the ZFP was still available.

Also, 2 other questions:
If I do get something working, do I use your licensing statement in the
files as is, or should I modify it if I modify the files?  I do plan
on modifying quite a few of the ada ones to fit with my chip, but I had
noticed you seemed to use the vanilla FSF copyright in your license
statement, even though I assume you wrote some of the code in the file.

It looks like you most likely use gcc for some intrinsics like memcpy. 
Do I need to worry about licensing issues if I build with GNAT GPL 2017 
using a modified version of your RTS if it links in functions like memcpy?
I can supply my own if so, they just won't be as efficient if I do.