[vorbis-dev] Optimisations

[Timothy J. Wood]

> >   One benefit of this approach would be to make it easier to compare the results of the C 
> version with a particular 
> > optimization. 
>  
> What would be the difference? 
>  

  Well, ideally the output would be the same.  This would allow developers to have a much easier time testing since they wouldn't have to rebuild to switch to a different optimization path.

> > (leaving that to the maintainer of that function), and people can still compile stuff and 
> just select the 'use only C'  
>  
> Leaving stuff to the maintainer of a particular function, will make progress of 
> Vorbis as slow as the slowest of the developers (at least for some people). 
>  

  No, actually, it would make development faster since Monty or other codec developers wouldn't have to worry so much (or at all) about their changes impacting optimized work -- they could just commit them and send out mail letting the optimized path people know something has changed.  When release time comes around, any optimized paths that don't work would simply be disabled (since obviously they aren't getting enough support) rather than begin shipped broken.

-tim

--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.