From: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "Zhao Zhili" <quinkblack@foxmail.com>,
"Rémi Denis-Courmont" <remi@remlab.net>
Subject: [FFmpeg-devel] Re: [Question] Learning about VVC and wasm
Date: Fri, 14 Nov 2025 13:30:51 +0200
Message-ID: <1F2CC6B5-1B4E-4412-8A4D-299517E66ABE@remlab.net> (raw)
In-Reply-To: <tencent_5D67803A34C93E8F573F9CAAE0C65AE83509@qq.com>
Le 14 novembre 2025 06:09:25 GMT+02:00, Zhao Zhili via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> a écrit :
>> For FFmpeg, WASM optimisations are embryonic at best. There is no
>> documentation since there is very little experience with them as yet.
>
>The wasm and wasm simd has already reached a considerable level of maturity.
There is only HEVC IDCT for 8- and 10-bit, and SAO for 8-bit. I don't doubt that those optimisations are good and mature. But in terms of coverage, compared to x86 and AArch64. That is embryonic IMO.
There are also no WASM guidelines in the optimisation doxygen file. How to write good assembler that runs fast on x86 and on AArch64 with intrinsics is not explained or referenced either.
To be clear, I'm not *faulting* anyone, and the RISC-V stuff, that I've been involved with, is also in many ways "embryonic" if less so than WASM's.
Br,
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-11-14 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 16:46 [FFmpeg-devel] " Sidd via ffmpeg-devel
2025-11-13 17:42 ` [FFmpeg-devel] " Frank Plowman via ffmpeg-devel
2025-11-13 17:56 ` Sidd via ffmpeg-devel
2025-11-13 18:10 ` Frank Plowman via ffmpeg-devel
2025-11-13 18:16 ` Sidd via ffmpeg-devel
2025-11-13 18:19 ` Rémi Denis-Courmont via ffmpeg-devel
2025-11-14 4:09 ` Zhao Zhili via ffmpeg-devel
2025-11-14 11:30 ` Rémi Denis-Courmont via ffmpeg-devel [this message]
2025-11-14 11:59 ` Zhao Zhili via ffmpeg-devel
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=1F2CC6B5-1B4E-4412-8A4D-299517E66ABE@remlab.net \
--to=ffmpeg-devel@ffmpeg.org \
--cc=quinkblack@foxmail.com \
--cc=remi@remlab.net \
/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