[FFmpeg-devel] [RFC] cpu specific implementation of libavutil functions

Rich Felker dalias
Mon Sep 10 05:25:46 CEST 2007

On Mon, Sep 10, 2007 at 12:30:22PM +1000, Nigel Pearson wrote:
> > fork(), sigill catching or anything similar is not ok in libavutil
> > and actually not in libavcodec (or any other lib) either ...
> What about something Linux-specific, like parsing /proc/cpuinfo ?
> Ugly in a different way, but at least it doesn't use "exceptions"

Poking around the filesystem is also not OK for such a
purely-computational library as libavutil... Actally the headers
should #define all the file io functions to *_is_disabled_in_libavutil
or similar.


More information about the ffmpeg-devel mailing list