> evas are named. It is definitely much nicer to not have 30+ character
> types.
That's the Apple notation, and yes it isn't very consistent with evas naming
scheme, but mmx macros aren't either. So ...
>
> > Remark:
> >
> > * I don't know
full or not... Anyway, there's always a common altivec
header to define typedef for vector type (that are otherwise very long to type
...). And i left all the macros in the header, if someone is interested.
Remark:
* I don't know what kind of indentation you use (i suspect emacs' one) but it
sounds wired to me... At least in vim, it's quite difficult to indent
correctly everything... :-/
That should be all i had to say. (as usual, i speak a lot ...)
Benjamin "benoar" Cama
evas_altivec_optimizations.diff.gz
Description: GNU Zip compressed data
> on it myself :)
>
Me too ... too much work for now, and I'm not very interested in it. As
someone said, porting evas to macosx is maybe not very relevant as OSX's
display system is already quite good. But evas will be better ;)
I think it's mostly usefull for linux-p
Selon Nathan Ingersoll <[EMAIL PROTECTED]>:
> > > I recently got a G4 IBook and wanted to test evas on it; after some
> compiling
> > > problems, I get it to run and ... well, that's not bad but I was once
> more
> > > disapointed by its result (the 800MHz G4 that's in this computer doesn't
> see
ay on linuxfr.org, "sapusaipalibre".
> > I forgot one thing: I've got no "direct" access to the net, so the CVS
version
> > I'm working on dates from about 6 months ago (well, it was from the SPLIT
> > branch, but still..). I'll try t
be happy to
get advices if someone is working on one of these topics and wants to help. I
thanks you all for the great work, espacially the Rasterman for giving birth
to this wonderfull project!
I forgot one thing: I've got no "direct" access to the net, so the CVS versio
