{"push_id":874596244,"size":4,"distinct_size":4,"ref":"refs/heads/master","head":"401c93ddb76fb213b858ad722c83cdb4a510dc52","before":"6662ca28d4c03c2f45fdba3945c7f0e7bdf64264","commits":[{"sha":"8ffb3f08c6d44fe9ce7076288b1cd63edc56dad7","author":{"email":"bd30873f3039d227f2d43dffb4a4261325de676f@gmail.com","name":"Ganesh Ajjanagadde"},"message":"avcodec/amr: replace #define by typedef\n\nSee e.g https://stackoverflow.com/questions/1666353/are-typedef-and-define-the-same-in-c\nfor rationale.\n\nReviewed-by: Michael Niedermayer <michael@niedermayer.cc>\nSigned-off-by: Ganesh Ajjanagadde <gajjanagadde@gmail.com>","distinct":true,"url":"https://api.github.com/repos/herrnst/ffmpeg/commits/8ffb3f08c6d44fe9ce7076288b1cd63edc56dad7"},{"sha":"14ea4151d7c3c26500193f11ac661ed20c7c2b9c","author":{"email":"bd30873f3039d227f2d43dffb4a4261325de676f@gmail.com","name":"Ganesh Ajjanagadde"},"message":"avutil/libm: correct isnan, isinf compat hacks\n\nisnan and isinf are actually macros as per the standard. In particular,\nthe existing implementation has incorrect signature. Furthermore, this\nresults in undefined behavior for e.g double values outside float range\nas per the standard.\n\nThis patch corrects the undefined behavior for all usage within FFmpeg.\n\nNote that long double is not handled as it is not used in FFmpeg.\nFurthermore, even if at some point long double gets used, it is likely\nnot needed to modify the macro in practice for usage in FFmpeg. See\nbelow for analysis.\n\nGetting long double to work strictly per the spec is significantly harder\nsince a long double may be an IEEE 128 bit quad (very rare), 80 bit\nextended precision value (on GCC/Clang), or simply double (on recent Microsoft).\nOn the other hand, any potential future usage of long double is likely\nfor precision (when a platform offers extra precision) and not for range, since\nthe range anyway varies and is not as portable as IEEE 754 single/double\nprecision. In such cases, the implicit cast to a double is well defined\nand isinf and isnan should work as intended.\n\nReviewed-by: Michael Niedermayer <michael@niedermayer.cc>\nSigned-off-by: Ganesh Ajjanagadde <gajjanagadde@gmail.com>","distinct":true,"url":"https://api.github.com/repos/herrnst/ffmpeg/commits/14ea4151d7c3c26500193f11ac661ed20c7c2b9c"},{"sha":"275aca8fba50e77af16627d8d5db4b3d4987d889","author":{"email":"bd30873f3039d227f2d43dffb4a4261325de676f@gmail.com","name":"Ganesh Ajjanagadde"},"message":"configure+libm.h: add hypot emulation\n\nIt is known that the naive sqrt(x*x + y*y) approach for computing the\nhypotenuse suffers from overflow and accuracy issues, see e.g\nhttp://www.johndcook.com/blog/2010/06/02/whats-so-hard-about-finding-a-hypotenuse/.\nThis adds hypot support to FFmpeg, a C99 function.\n\nOn platforms without hypot, this patch does a reaonable workaround, that\nalthough not as accurate as GNU libm, is readable and does not suffer\nfrom the overflow issue. Improvements can be made separately.\n\nReviewed-by: Michael Niedermayer <michael@niedermayer.cc>\nSigned-off-by: Ganesh Ajjanagadde <gajjanagadde@gmail.com>","distinct":true,"url":"https://api.github.com/repos/herrnst/ffmpeg/commits/275aca8fba50e77af16627d8d5db4b3d4987d889"},{"sha":"401c93ddb76fb213b858ad722c83cdb4a510dc52","author":{"email":"bd30873f3039d227f2d43dffb4a4261325de676f@gmail.com","name":"Ganesh Ajjanagadde"},"message":"avutil/eval: change sqrt to hypot\n\nThis improves the mathematical behavior of hypotenuse computation.\n\nReviewed-by: Michael Niedermayer <michael@niedermayer.cc>\nSigned-off-by: Ganesh Ajjanagadde <gajjanagadde@gmail.com>","distinct":true,"url":"https://api.github.com/repos/herrnst/ffmpeg/commits/401c93ddb76fb213b858ad722c83cdb4a510dc52"}]}