This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PowerPC SPE maintainership (was Re: Obsolete powerpc*-*-*spe*)


On Mon, May 01, 2017 at 10:48:05AM +0000, Joseph Myers wrote:
> On Sat, 29 Apr 2017, Segher Boessenkool wrote:
> 
> > 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.
> 
> It seems fairly obvious that the powerpc-*-eabispe* and 
> powerpc*-*-linux*spe* triples should continue to work while being mapped 
> to the new CPU port.  It's less obvious what triples should be used for 
> SPE versions of other SPE-supporting configurations such as 
> powerpc-*-eabisim*, powerpc-*-rtems*, powerpc-wrs-vxworks*.

My current patches have powerpc*-*-*spe* for the powerpcspe port.
Maybe it should also allow powerpcspe-*-*?  If people are willing
to change the target triple they use.

> Some testcases will be applicable to both ports, some to only one.

Yeah; but we can sort that out later, no change is needed as long as
the new port is essentially a copy of rs6000 :-)

> Maintainers of each port should of course watch the other port for changes 
> that should be carried across, even if we believe, as has been stated in 
> this discussion, that the parts of the code that would be present in both 
> ports are stable and very rarely change.

Right.


Segher


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]