[Ffmpeg-cvslog] r6338 - in trunk: ffmpeg.c libavcodec/mpegvideo.c libavcodec/ratecontrol.c libavcodec/snow.c

Guillaume POIRIER poirierg
Sat Sep 30 18:55:01 CEST 2006


Hi,

On 9/29/06, Michael Niedermayer <michaelni at gmx.at> wrote:
> On Thu, Sep 28, 2006 at 06:28:55PM +0200, Guillaume POIRIER wrote:
> > On 9/28/06, Panagiotis Issaris <takis.issaris at uhasselt.be> wrote:
> > >On wo, 2006-09-27 at 23:17 +0100, M?ns Rullg?rd wrote:
> >
> > [..]
> >
> > >> To takis: please pay attention to compiler warnings when you make
> > >changes.
> > >You are right. But, "make mpegvideo.o | grep warning|wc -l" returns 324 on
> > >my
> > >system, which makes it difficult to see the new ones in the pages of
> > >existing warnings...
> >
> > I guess it's high time to have regression tests check for the number
> > of warnings ;-P
>
> wont work as different gcc versions will produce different warnings,
> actualy even the same gcc will produce different ones depending
> on optimization levels (and no i dont mean -Winline related ones)
>
> a better and more generically useable solution would be to change
> colorgcc (which is a simple perl script which colorizes gcc output)
> so that it caches the output of the last time or of some reference run
> and makes new warnings blink or so ...
>
> <OT>attached is a little old patch to colorgcc which makes it colorize
> different warnings differently</OT>

Actually, I wasn't being serious when I said that (I did figure out
the problems of different compiler version ;-).... but it's good to be
taken somewhat seriously sometimes ;-)))))



Guillaume
-- 
With DADVSI (http://en.wikipedia.org/wiki/DADVSI), France finally has
a lead on USA on selling out individuals right to corporations!
Vive la France!




More information about the ffmpeg-cvslog mailing list