New port for Kalray processors

New port for Kalray processors

[Paul Iannetta]

On behalf of Kalray Inc., I would like to contribute our port of the binutils
for the Kalray MPPA Coolidge.

We would like to know the requirements needed to be integrated within
the binutils official repository.  Currently, we have a fairly
complete port only missing the simulator since we use qemu.  However,
our version of gdb is behind the version you provide and we would like
to know whether it would be possible to upstream our ports in two
steps.  First, the core part and, in a second time, our gdb port.

You can have a preview of our code on github:
    https://github.com/kalray

Kalray's has yet to complete the copyright assignment forms from FSF.

Thanks,

Paul Iannetta
Kalray

Re: New port for Kalray processors

[Nick Clifton]

Hi Paul,

> On behalf of Kalray Inc., I would like to contribute our port of the binutils
> for the Kalray MPPA Coolidge.

Thank you very much for doing this.

> We would like to know the requirements needed to be integrated within
> the binutils official repository.

Essentially there are three steps:

   1. Complete a FSF copyright assignment.
   2. Submit the code for review.
   3. Nominate one or more people who are willing to act as maintainers for the port.

It helps a great deal if the code follows the GNU coding standard:

   http://savannah.gnu.org/projects/gnustandards

It is also very useful if the code includes additions to the testsuites
to check the functionality of the port, and ensure that it continues to
work in the future.

Cheers
   Nick

Re: New port for Kalray processors

[Paul Iannetta]

On Fri, Jul 01, 2022 at 03:47:16PM +0100, Nick Clifton wrote:
> Hi Paul,
> 
> > On behalf of Kalray Inc., I would like to contribute our port of the binutils
> > for the Kalray MPPA Coolidge.
> 
> Thank you very much for doing this.
> 
> > We would like to know the requirements needed to be integrated within
> > the binutils official repository.
> 
> Essentially there are three steps:
> 
>   1. Complete a FSF copyright assignment.
>   2. Submit the code for review.
>   3. Nominate one or more people who are willing to act as maintainers for the port.
> 
> It helps a great deal if the code follows the GNU coding standard:
> 
>   http://savannah.gnu.org/projects/gnustandards
> 
> It is also very useful if the code includes additions to the testsuites
> to check the functionality of the port, and ensure that it continues to
> work in the future.
> 
> Cheers
>   Nick

Hi Nick,

Thank you very much for you kind answer.  If I understood correctly,
the FSF copyright assignment form should be provided by the maintainer
of the project? If so, could you provide us the assignment so that we
can complete it.

We already follow the GNU coding standard, our only point of
divergence is that we do not use the Changelog and that most of the
commit message do not follow the GNU standard (which means I will
have to rewrite most of the commits to include the Changelog entries
and rewrite the commit messages).

Once, we complete the FSF copyright assignment form I will send in the
patches.

I will act as a maintainer for the port.

Thanks,

Paul Iannetta
Kalray

Re: New port for Kalray processors

[Nick Clifton]

Hi Paul,

>>    1. Complete a FSF copyright assignment.


> Thank you very much for you kind answer.  If I understood correctly,
> the FSF copyright assignment form should be provided by the maintainer
> of the project? If so, could you provide us the assignment so that we
> can complete it.

Certainly.  There are four different versions of the form available,
depending upon your wishes:

   https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=tree;f=doc/Copyright

I suggest the request-assign.future version which requests a copyright
assignment for past and future changes.

The request-assign.changes only requests a copyright assignment for past
changes, not future ones.  The request-assign.program form requests an
assignment for a completely new program, not just a port of an existing
program to a new target.  The request-disclaim.changes form is for when
you only have small changes to contribute.

Cheers
   Nick