So now that there aren't going to be any more wild branches affecting large swaths of the code before 1.0, now is a good time to really start looking at optimization. (Actually, I still need to implement CBR, which will involve a branch and code changes. But this should not affect any of the code where there's serious speed-critical work to do). It seems like a month or two back I was beating off folks hell-bent on optimizing with a large stick... unfortunately I seem to have succeeded. I've put away the stick... Is anyone still interested? ;-) Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/
> It seems like a month or two back I was beating off folks hell-bent on > optimizing with a large stick... unfortunately I seem to have succeeded. I've > put away the stick... Is anyone still interested? ;-)Count me in :-) Dag dag, Segher --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/
>I've >put away the stick... Is anyone still interested? ;-)yummm, sounds fun, how are we going to do this, pure C based optimization or nasty assembler, or seperate branches ??? Anyone know any good profiling software for Linux, prefereably open source and command line based so I can have a shot at recompiling for BeOS. Dave --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/