From: "Rémi Denis-Courmont" <remi@remlab.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 2/2] lavc/blockdsp: R-V V fill_block Date: Tue, 30 Apr 2024 09:40:31 +0300 Message-ID: <A1BA659F-4798-48CC-A8A8-4EA17465913B@remlab.net> (raw) In-Reply-To: <CAEa-L+vTobhG4o2H9Gm3JmxnUZOFB3W6Rg-TQ+stu47yJ50Ykw@mail.gmail.com> Le 30 avril 2024 03:26:25 GMT+03:00, flow gg <hlefthleft@gmail.com> a écrit : >Hi, I initially used a loop, but according to libavcodec/blockdsp.h, > >the maximum is 8x16 = 128 bytes, so using ff_get_rv_vlenb() >= 16 and m8 >does not require a loop. It's okay to assume that VLENB is at least 16 bytes (as long as it's checked), but the code seems to assume (?) that it's *exactly* 16 bytes, which will break on future hardware. > >``` >/* add and put pixel (decoding) > * Block sizes for op_pixels_func are 8x4,8x8 16x8 16x16. > * h for op_pixels_func is limited to { width / 2, width }, > * but never larger than 16 and never smaller than 4. */ >typedef void (*op_fill_func)(uint8_t *block /* align width (8 or 16) */, > uint8_t value, ptrdiff_t line_size, int h); >``` > >Rémi Denis-Courmont <remi@remlab.net> 于2024年4月30日周二 01:31写道: > >> Le maanantaina 29. huhtikuuta 2024, 10.09.41 EEST flow gg a écrit : >> > >> >> Are you sure that this works with all vector lengths? >> The block8 code looks odd. >> >> -- >> レミ・デニ-クールモン >> http://www.remlab.net/ >> _______________________________________________ >> 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". >> >_______________________________________________ >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". _______________________________________________ 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-04-30 6:40 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-29 7:09 flow gg 2024-04-29 17:31 ` Rémi Denis-Courmont 2024-04-30 0:26 ` flow gg 2024-04-30 1:16 ` flow gg 2024-04-30 6:40 ` Rémi Denis-Courmont [this message] 2024-04-30 8:22 ` flow gg 2024-04-30 12:49 ` Rémi Denis-Courmont
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=A1BA659F-4798-48CC-A8A8-4EA17465913B@remlab.net \ --to=remi@remlab.net \ --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