From: "Martin Storsjö" <martin@martin.st> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v2] checkasm/hevc_deblock: add luma and chroma full Date: Wed, 24 Jan 2024 15:39:05 +0200 (EET) Message-ID: <40f21059-551d-fc6c-ad19-cd5e21da76c0@martin.st> (raw) In-Reply-To: <20240124120634.84237-1-jdek@itanimul.li> On Wed, 24 Jan 2024, J. Dekker wrote: > Signed-off-by: J. Dekker <jdek@itanimul.li> > --- > tests/checkasm/hevc_deblock.c | 225 +++++++++++++++++++++++++++++----- > 1 file changed, 195 insertions(+), 30 deletions(-) > > - added luma 10/12 bit > - supporting full (*_c) luma & chroma functions > - dynamically generating all test data > > Appears to work for me. Testing on x86, hits the filtering decisions correctly. > x86 doesn't have the full asm functions though, need to check a platform which > has them (though the difference is minor, not sure why it wouldn't work). Looks mostly good, although I didn't test it myself. A couple of cosmetic comments below: > +#define RNDDIFF(val, diff) av_clip(((SIZEOF_PIXEL == 1) ? \ > + *(uint8_t*)(&val) : *(uint16_t*)(&val)) - (diff), 0, \ > + (1 << (bit_depth)) - 1) + rnd() % FFMAX(2 * (diff), 1) This macro is quite hard to read - can you indent it semantically based on nesting level or something like that? > +#define TC25(x) ((tc[x] * 5 + 1) >> 1); > + > +static void randomize_luma_buffers(int type, int *beta, int32_t tc[2], uint8_t *buf, ptrdiff_t xstride, ptrdiff_t ystride, int bit_depth) > +{ This one line is quite significantly longer than all the surrounding ones - can you wrap it? (Elsewhere, there are also a couple rather long lines, but they fit in better, but wrapping them is welcome too.) // Martin _______________________________________________ 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-01-24 13:39 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-24 12:06 J. Dekker 2024-01-24 13:39 ` Martin Storsjö [this message] 2024-01-25 0:04 ` Michael Niedermayer
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=40f21059-551d-fc6c-ad19-cd5e21da76c0@martin.st \ --to=martin@martin.st \ --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