On 05/06/2013 02:48 PM, Diego Biurrun wrote: > On 2013-04-21 09:50, Luca Barbato wrote: >> On 04/21/2013 04:28 AM, Diego Biurrun wrote: >>> >>> Given how small these functions are, placing them inline in a header >>> seemed appropriate. Other suggestions welcome, but I suspect they >>> will be more complicated. >> >> rbelf-size will tell us I guess. Looks fine to me but should be tested. > > I don't have rbelf-size install right now, but here is the (relevant) > output from ls and size: > > before: > > $ ls -l libavcodec/libavcodec.a > -rw-rw-r-- 1 biurrun src-pisa 82353412 May 6 14:41 libavcodec/libavcodec.a > > text data bss dec hex filename > 20288 0 0 20288 4f40 dsputil_mmx.o (ex > libavcodec/libavcodec.a) > 48339 0 0 48339 bcd3 h264_qpel.o (ex > libavcodec/libavcodec.a) > > after: > > $ ls -l libavcodec/libavcodec.a > -rw-rw-r-- 1 biurrun src-pisa 82352708 May 6 14:06 libavcodec/libavcodec.a > > text data bss dec hex filename > 20288 0 0 20288 4f40 dsputil_mmx.o (ex > libavcodec/libavcodec.a) > 48355 0 0 48355 bce3 h264_qpel.o (ex > libavcodec/libavcodec.a) >
negligible as expected. Thanks. _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
