This is the mail archive of the
mailing list for the GCC project.
Re: Target-specific Front-Ends? (Was: front end changes foraltivec)
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Aldy Hernandez <aldyh at redhat dot com>
- Cc: Stan Shebs <shebs at apple dot com>, Per Bothner <per at bothner dot com>, Ziemowit Laski <zlaski at apple dot com>, Ira Ruben <ira at apple dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Wed, 28 Nov 2001 09:39:45 -0800
- Subject: Re: Target-specific Front-Ends? (Was: front end changes foraltivec)
> > If the latter, then we have a source-incompatible change. Once we
> > do that, all Altivec users have to change their code, and changing
> > "vector int" into "__attribute__((vector(4)) int" is not a whole
> > lot worse.
> See the last response by rth. He came up with a way in which we can
> just specify the total vector size in an attribute and determine the
> vector mode from the type being modified (int, in this case). So, we
> should be able to cater to both parties-- a more generic approach, and
> a few macros to implement altivec syntax, modulo the () initializers.
Good. Note that I (and probably Joseph) are going to get unhappy if
there is not detailed documentation about exactly what the syntax
means, and also exactly what the semantics are for these types. :-)
Mark Mitchell firstname.lastname@example.org
CodeSourcery, LLC http://www.codesourcery.com