From: "Martin Storsjö via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: "Martin Storsjö" <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PATCH] checkasm: Use av_strlcatf for appending SME info after SVE (PR #21214)
Date: Tue, 16 Dec 2025 12:45:35 -0000
Message-ID: <176588913632.60.13047446916896375037@2cb04c0e5124> (raw)
PR #21214 opened by Martin Storsjö (mstorsjo)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21214
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21214.patch
If we had SVE enabled and formatted info about its vector lengths, it would be overwritten by the SME info.
This is only an issue for SME, which can be printed after SVE. Or should we consistently use `av_strlcatf` for all of these printouts for consistency?
From 009fff560c4c44b4adceec0ee3db21e264f77169 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Martin=20Storsj=C3=B6?= <martin@martin.st>
Date: Tue, 16 Dec 2025 14:43:11 +0200
Subject: [PATCH] checkasm: Use av_strlcatf for appending SME info after SVE
If we had SVE enabled and formatted info about its vector lengths,
it would be overwritten by the SME info.
---
tests/checkasm/checkasm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/checkasm/checkasm.c b/tests/checkasm/checkasm.c
index 62fa7fef12..461f1e7e5a 100644
--- a/tests/checkasm/checkasm.c
+++ b/tests/checkasm/checkasm.c
@@ -1049,8 +1049,8 @@ int main(int argc, char *argv[])
#endif
#if ARCH_AARCH64 && HAVE_SME
if (have_sme(av_get_cpu_flags()))
- snprintf(arch_info_buf, sizeof(arch_info_buf),
- "SME %d bits, ", 8 * ff_aarch64_sme_length());
+ av_strlcatf(arch_info_buf, sizeof(arch_info_buf),
+ "SME %d bits, ", 8 * ff_aarch64_sme_length());
#endif
#if ARCH_RISCV && HAVE_RVV
if (av_get_cpu_flags() & AV_CPU_FLAG_RVV_I32)
--
2.49.1
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2025-12-16 12:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=176588913632.60.13047446916896375037@2cb04c0e5124 \
--to=ffmpeg-devel@ffmpeg.org \
--cc=code@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