From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] tests/checkasm: add a test for VorbisDSPContext Date: Mon, 19 Sep 2022 15:00:14 -0300 Message-ID: <a0e14b3c-034e-2ba1-3bf2-28c8f778c06b@gmail.com> (raw) In-Reply-To: <1827436.tdWV9SEqCh@basile.remlab.net> On 9/19/2022 2:57 PM, Rémi Denis-Courmont wrote: >> +void checkasm_check_vorbisdsp(void) >> +{ >> + VorbisDSPContext dsp; >> + >> + ff_vorbisdsp_init(&dsp); >> + >> + if (check_func(dsp.vorbis_inverse_coupling, "vorbis_inverse_coupling")) >> + test_inverse_coupling(); >> + report("vorbis_inverse_coupling"); > > Should these not be just "inverse_coupling" seen as there is already a > "vorbisdsp" prefix in the logs? It can, if anything so the relevant line is shorter when the report is printed. Changed locally. I just went and used the name of the function pointer as it's in VorbisDSPContext. A name that could be changed too, for that matter. > > Other than that, this is very much welcome for me. > >> +} >> diff --git a/tests/fate/checkasm.mak b/tests/fate/checkasm.mak >> index 4d2f321e84..fbba0b5b8f 100644 >> --- a/tests/fate/checkasm.mak >> +++ b/tests/fate/checkasm.mak >> @@ -43,6 +43,7 @@ FATE_CHECKASM = fate-checkasm-aacpsdsp >> \ fate-checkasm-vf_nlmeans \ >> fate-checkasm-vf_threshold \ >> fate-checkasm-videodsp \ + >> fate-checkasm-vorbisdsp \ >> fate-checkasm-vp8dsp \ >> fate-checkasm-vp9dsp \ > > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2022-09-19 18:00 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-19 17:04 James Almer 2022-09-19 17:55 ` Ronald S. Bultje 2022-09-19 17:57 ` James Almer 2022-09-19 17:57 ` Rémi Denis-Courmont 2022-09-19 18:00 ` James Almer [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=a0e14b3c-034e-2ba1-3bf2-28c8f778c06b@gmail.com \ --to=jamrial@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git