> > More generally though (outside this unsafe flag case) > i do disagree with your argument a bit, performance does matter. > Iam regularly reminded of that for example, so much software becomes > slower on each upgrade with few if any features added the real users > care about. Just to pick one, the editor i use to write replies in mutt > is slower to close than before i upgraded the OS. > > Also again to stay general here, this does not apply to the unsafe flag. > speed / cpu load does add up. Slower code means more CO2 emissions if > the software is used alot. > If you want a real example insetad of this flag where we could improve > IIRC there was some code iterating over options in the iteration over > options resulting in some sort of O(n^3) or so. Thats from memory though > would need to check where that was exactly but thats something we should > fix. >
Please provide evidence that the H.264 Decoder has got slower. Surely by your argument all your fuzzing fixes need an #ifdef to turn them off to save CO2? Kieran _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
