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

[burek]

[03:19:50 CEST] <cone-460> ffmpeg 03Jun Zhao 07master:3ba09704fafa: doc/build_system: Document checkheaders/alltools and consistency fixes
[03:19:50 CEST] <cone-460> ffmpeg 03Jun Zhao 07master:b63df9b52705: doc/encoders: Document eld_v2 option for libfdk_aac encoder.
[03:19:50 CEST] <cone-460> ffmpeg 03Jun Zhao 07master:b983e71bde6c: lavfi/sr: Remove slice thread flag
[03:19:50 CEST] <cone-460> ffmpeg 03Jun Zhao 07master:9b069eb14e07: lavfi/sr: Change the backend type from flags to int
[08:53:50 CEST] <vtorri99978666> hello
[08:54:27 CEST] <vtorri99978666> while corss compiling on linux for Windows, configure fails because libbluray is not found by pkg-config (libbluray is installed)
[08:54:48 CEST] <vtorri99978666> is it possible to have a configure output (a config.log, or a verbose mode) ?
[08:56:20 CEST] <vtorri99978666> i can also see that bd_open is requested with libbluray, maybe it is the reason of the failure
[08:56:27 CEST] <vtorri99978666> what is bd_open ?
[08:57:25 CEST] <vtorri99978666> maybe a symbol in libblueray...
[08:58:01 CEST] <vtorri99978666> yes, that's it
[09:01:57 CEST] <cone-071> ffmpeg 03Gyan Doshi 07master:eae251ead9e3: avformat/segment: populate empty outer stream extradata from packet
[09:03:32 CEST] <vtorri99978666> bbl
[11:17:07 CEST] <cone-071> ffmpeg 03Paul B Mahol 07master:b16806b09d60: avfilter/avf_avectorscope: make use of av_rescale
[11:17:08 CEST] <cone-071> ffmpeg 03Paul B Mahol 07master:618f8bb0a49e: avfilter/avf_abitscope: make use of av_rescale
[11:17:09 CEST] <cone-071> ffmpeg 03Paul B Mahol 07master:d2e76a1f96d7: avfilter/avf_showvolume: make use of av_rescale
[11:17:10 CEST] <cone-071> ffmpeg 03Paul B Mahol 07master:cd753968976d: avfilter/avf_ahistogram: make use of av_rescale
[11:17:11 CEST] <cone-071> ffmpeg 03Paul B Mahol 07master:62c8707e2ac1: avfilter/avf_showwaves: make use of av_rescale_q
[11:17:12 CEST] <cone-071> ffmpeg 03Paul B Mahol 07master:819ed1df94df: avfilter/avf_aphasemeter: make use of av_rescale
[18:06:42 CEST] <j-b> Does anyone know why the SSE code depends on the MMX one?
[18:08:34 CEST] <jamrial> you mean configure dependency?
[18:10:49 CEST] <j-b> yes
[18:11:02 CEST] <jamrial> that's by design, afaik. an instruction set enables all the previous ones as well
[18:11:15 CEST] <jamrial> so you can't build ffmpeg with ssse3 but no sse2, and such
[18:11:20 CEST] <kurosu> also, maybe, the old constants, stored in a C file, to reduce symbol & data duplication ?
[18:14:02 CEST] <kurosu> also, afaik, it's indeed rare to find a CPU with some set that doesn't have ones (amd 3now various sets maybe being an exception) older that said set
[18:33:54 CEST] <Lynne> we still have fma4 assembly, we can save some kilobytes if we remove it (no fma4-only function exists, they're all templated)
[18:35:09 CEST] <Lynne> its only in avf_showcqt and lavr though
[18:35:48 CEST] <durandal11707> do not make showcqt slow
[18:39:23 CEST] <jamrial> why would we remove fma4? bulldozer based cpus are still pretty widespread
[18:45:49 CEST] <Lynne> doesn't every amd cpu with fma4 also support fma3? if the performance of both is the same then there's no reason to carry both
[18:54:53 CEST] <jamrial> piledriver, steamroller and excavator do, bulldozer does not
[18:55:45 CEST] <jamrial> but in any case, they are all slow when using ymm registers. that's why all the fma4 functions were written using xmm registers
[18:56:06 CEST] <jamrial> none of the fma3 functions are enabled for those cpus, as they use ymm registers
[18:58:13 CEST] <Lynne> oh, makes sense, I thought amd included fma3 when intel refused to use their fma4 encoding
[19:01:34 CEST] <jamrial> they did during the first refresh, with piledriver
[22:02:42 CEST] <mkver> Is there actually an easy way to find out which fate tests might be affected by changes to a certain file?
[22:05:12 CEST] <nevcairiel> not necessarily
[22:05:33 CEST] <nevcairiel> many components have direct tests of course, which are easily identifiable
[22:05:40 CEST] <nevcairiel> but they may also be used in other tests
[22:09:18 CEST] <mkver> Yeah, the easy tests are of course easily identifiable. It's the other tests that worry me.
[22:10:38 CEST] <mkver> E.g. for my matroska demuxer patches I changed the Matroska demuxer to always return -1 on init and the tests that were broken by this were the tests that I am interested in.
[22:22:52 CEST] <nevcairiel> run full fate
[22:22:53 CEST] <nevcairiel> :)
[22:23:14 CEST] <nevcairiel> one should do that once before sending patches anyhow, in my experience
[22:23:17 CEST] <nevcairiel> too many unknowns
[22:26:55 CEST] <mkver> I did it after certain of the big patches; but doing it for every patch in a patchset? That's quite a lot. The other patches were checked with the list of tests known to be affected by the patches in question.
[22:30:22 CEST] <jamrial> what you did by making the demuxer always return -1 is fine. the tests that fail after that are those that use said demuxer. every other test should be unaffected
[00:00:00 CEST] --- Wed May 29 2019