From: Ramiro Polla <ramiro.polla@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v3 1/2] checkasm: add test for fdct Date: Mon, 6 May 2024 19:18:11 +0200 Message-ID: <CALweWgDN1VfBE4rL7Jpz09r1jqyWCxBa=s7WRKXWo56dFyjnog@mail.gmail.com> (raw) In-Reply-To: <12991264.z41PNqO1t7@basile.remlab.net> On Thu, May 2, 2024 at 8:05 PM Rémi Denis-Courmont <remi@remlab.net> wrote: > Le keskiviikkona 17. huhtikuuta 2024, 21.01.37 EEST Ramiro Polla a écrit : [...] > > +static void check_fdct(void) > > +{ > > + LOCAL_ALIGNED_16(int16_t, block0, [64]); > > + LOCAL_ALIGNED_16(int16_t, block1, [64]); > > + > > + AVCodecContext avctx = { 0 }; > > AFAICT, that is not a legal context for ff_fdctdst_init(), which expect > bits_per_raw_sample to be one of 8, 9 or 10. It would also be good manners to > initialise dct_algo. Thanks for spotting it. New patch coming up in a while. I'll send a similar patch to fix checkasm/idctdsp after this is merged. _______________________________________________ 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".
next prev parent reply other threads:[~2024-05-06 17:18 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-17 18:01 [FFmpeg-devel] [PATCH v3 0/2] lavc/aarch64/fdct: add neon-optimized fdct for aarch64 Ramiro Polla 2024-04-17 18:01 ` [FFmpeg-devel] [PATCH v3 1/2] checkasm: add test for fdct Ramiro Polla 2024-05-02 18:04 ` Rémi Denis-Courmont 2024-05-06 17:18 ` Ramiro Polla [this message] 2024-05-06 17:49 ` Rémi Denis-Courmont 2024-05-13 16:49 ` James Almer 2024-05-13 19:14 ` Ramiro Polla 2024-04-17 18:01 ` [FFmpeg-devel] [PATCH v3 2/2] lavc/aarch64/fdct: add neon-optimized fdct for aarch64 Ramiro Polla 2024-04-17 20:49 ` [FFmpeg-devel] [PATCH v3 0/2] " Martin Storsjö 2024-05-13 12:55 ` Ramiro Polla
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='CALweWgDN1VfBE4rL7Jpz09r1jqyWCxBa=s7WRKXWo56dFyjnog@mail.gmail.com' \ --to=ramiro.polla@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