[Ffmpeg-devel-irc] ffmpeg-devel.log.20180630

burek burek021 at gmail.com
Sun Jul 1 03:05:04 EEST 2018


[00:43:20 CEST] <cone-230> ffmpeg 03Wang Cao 07master:5a99e00023c0: libavformat/yuv4mpeg: Add color range support for Y4M Add color_range support in Y4M.
[00:43:20 CEST] <cone-230> ffmpeg 03Michael Niedermayer 07master:d08d4a8c7387: avcodec/vc1_block: Fix mqaunt check for negative values
[01:37:43 CEST] <thardin> woop, figured out how to get gapless clickless CDs going
[01:37:54 CEST] <thardin> and I see some mxfdec patches
[11:08:53 CEST] <atomnuker> durandal_1707: look what hit the ML this morning
[11:17:26 CEST] <JEEB> &/34
[11:17:28 CEST] <JEEB> funky
[16:15:21 CEST] <cone-363> ffmpeg 03Michael Niedermayer 07master:9f0077cc0397: tools/target_dec_fuzzer: Fix parser_avctx memleak on error path
[18:06:25 CEST] <Gramner> c language lawyers: why does gcc complain about casting x** to const x * const *? it makes everything const! I know that casting x** to const x** is an error since that could allow a const pointer to become non-const but I really can't see what's wrong with the former
[18:09:51 CEST] <nevcairiel> i thought that conversion could work
[18:18:13 CEST] <Gramner> x* to const x* and x** to x * const * works. so that narrows it down to x * const * to const x * const * somehow being an error
[18:26:00 CEST] <atomnuker> maybe they forgot to add this case as an exception
[18:47:59 CEST] <Gramner> works with g++ but not gcc which is also interesting. c++ obviously superior! /s
[18:55:19 CEST] <iive> cast giving error instead of warning?
[18:55:48 CEST] <Gramner> it warns when implicitly cast
[18:55:55 CEST] <Gramner> e.g. calling a function
[18:57:09 CEST] <Gramner> https://pastebin.com/jdBYuwX3
[19:00:10 CEST] <Gramner> if you explicitly cast it to be identical to the function arg type it works, but that's super ugly
[21:35:09 CEST] <JEEB> http://up-cat.net/p/3a173449
[21:35:37 CEST] <JEEB> noticed this because I'm not yet specifically disabling avdevice in my test building
[21:36:02 CEST] <JEEB> wonder if this is something that should be poked at towards the NDK people or if this might hit some other clang-based compilation thing as well
[00:00:00 CEST] --- Sun Jul  1 2018


More information about the Ffmpeg-devel-irc mailing list