This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: PowerPC SPE maintainership (was Re: Obsolete powerpc*-*-*spe*)
- From: Segher Boessenkool <segher at kernel dot crashing dot org>
- To: Andrew Jenner <andrew at codesourcery dot com>
- Cc: David Edelsohn <dje dot gcc at gmail dot com>, GCC Development <gcc at gcc dot gnu dot org>, Olivier Hainque <hainque at adacore dot com>, Sandra Loosemore <sandra at codesourcery dot com>, Arnaud Charlet <charlet at adacore dot com>, Joel Brobecker <brobecker at adacore dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Fri, 28 Apr 2017 18:15:45 -0500
- Subject: Re: PowerPC SPE maintainership (was Re: Obsolete powerpc*-*-*spe*)
- Authentication-results: sourceware.org; auth=none
- References: <20170214030703.GS21840@gate.crashing.org> <58A61E7B.4060903@codesourcery.com> <20170216221937.GB21840@gate.crashing.org> <58A63B91.1040102@codesourcery.com> <CAGWvny=aWTzSta=jwZS8HwmWU4riN7ee46CZP8MwS2PcYPC0mw@mail.gmail.com> <452E2837-FC8A-4DA2-A2B9-F58151841F58@adacore.com> <CAGWvnymQjd=k4Hv6PgWW2kuCinQTOQvSRvSEnVRN-C-RnvmKig@mail.gmail.com> <45cf27b1-2e27-460c-cb32-3be93f16b6d2@codesourcery.com> <7b2eb145-f07a-bced-9ff4-941aa12521d1@codesourcery.com>
Hi Andrew,
On Wed, Apr 26, 2017 at 10:18:55AM +0100, Andrew Jenner wrote:
> On 13/03/2017 18:01, Andrew Jenner wrote:
> >I volunteer to be the point of contact for the SPE port.
> >
> >Over here at CodeSourcery/Mentor Embedded, we have a strong interest in
> >SPE *not* being deprecated (we actively ship toolchain products with SPE
> >multilibs, and have customers for which these are important). We are
> >therefore volunteering resources (specifically, me) to maintain SPE
> >upstream as well.
>
> Ping.
>
> My understanding is that I need to be appointed by the steering
> committee to become a maintainer, but I have not yet heard anything from
> them.
>
> Either way, I will work on cleaning up the SPE test results and getting
> some patches sent upstream to make sure this part of the port is in good
> shape.
Here's the sequence of things that should happen:
1) Test results are posted to gcc-testresults@, ideally regularly.
Without test results no one can know if they break things.
2) The port has to be created. I volunteered to do that. This can
start soon after the GCC 7 release. It will be hard to do without
having test results.
We also still have to agree on the target triples for the new port.
If you have any thoughts on this, I'd love to hear them.
3) The port has to be accepted by the steering committee, and you
appointed the maintainer. This should be just a formality after 1)
and 2).
Segher