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: altivec triplets: comments?


On Nov  7, 2001, Geoff Keating <geoffk@geoffk.org> wrote:

> Daniel commented that

>> For instance, there aren't triplets for every new MIPS
>> processor supported by GCC

> but actually, when we build a special version of Linux for some weird
> MIPS ABI, a different triplet _is_ used.  For instance,

> mips-linux-gnu
> mipsisa32-linux-gnu

In this case, wouldn't it make sense for powerpc-linux-gnualtivec be
spelled powerpcaltivec-linux-gnu?  Otherwise, you wouldn't be able to
do something like powerpc-linux-gnulibc2.2.

I don't like powerpcaltivec much, but I think it's better than
gnualtivec, and, at least, there's more tradition to encode this kind
of change in the machine type than in the kernel-OS type.

powerpc-eabi* are more of an exception than a rule, IMO.

> and in fact there are a bunch of triplets for particular MIPS
> processors, although most of these don't change the ABI they just
> change the ISA.

Indeed.  I don't recall any precedent to changing the triplet to
accomodate an ABI change.  Most often, trailing text has been added to
indicate a change in object format, not ABI.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me


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