René J.V. Bertin <rjvbertin@...> writes: > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11203 > > Who cares, as long as they don't release versions > that fail on too many kinds of code?
What about the ~50 (?) releases since this report was opened? [...] > BTW, is there some documentation on ffmpeg.org on how to > create patches after having hacked around in the > source tree? http://ffmpeg.org/developer.html > And a related question: what's a good way to perform > real-world benchmarks on the libraries? Apart from time there are START_TIMER and STOP_TIMER macros in libavutil. > Can ffmpeg be compiled so that it collects performance > statistics on specific operations? Definitely. > Because I presume no one will be interested in patches > that give a performance gain that's significant > (reproducible) but completely irrelevant on the overall > timescale of operations... This is simply plain wrong. Carl Eugen _______________________________________________ Libav-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/libav-user
