From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/3] riscv: add Zvbb vector bit manipulation extension
Date: Wed, 08 May 2024 09:22:41 +0300
Message-ID: <48C24F9F-9E57-468D-87BC-F32E9718A745@remlab.net> (raw)
In-Reply-To: <589d6294-47a7-c338-2a57-acb8134bd389@martin.st>
Le 7 mai 2024 23:34:14 GMT+03:00, "Martin Storsjö" <martin@martin.st> a écrit :
>On Tue, 7 May 2024, Rémi Denis-Courmont wrote:
>
>> ---
>> Makefile | 2 +-
>> configure | 3 +++
>> doc/APIchanges | 3 +++
>> ffbuild/arch.mak | 1 +
>> libavutil/cpu.h | 1 +
>> libavutil/tests/cpu.c | 1 +
>> tests/checkasm/checkasm.c | 1 +
>> 7 files changed, 11 insertions(+), 1 deletion(-)
>>
>> diff --git a/libavutil/tests/cpu.c b/libavutil/tests/cpu.c
>> index d91bfeab5c..10e620963b 100644
>> --- a/libavutil/tests/cpu.c
>> +++ b/libavutil/tests/cpu.c
>> @@ -94,6 +94,7 @@ static const struct {
>> { AV_CPU_FLAG_RVV_F32, "zve32f" },
>> { AV_CPU_FLAG_RVV_I64, "zve64x" },
>> { AV_CPU_FLAG_RVV_F64, "zve64d" },
>> + { AV_CPU_FLAG_RV_ZVBB, "zvbb" },
>> #endif
>> { 0 }
>> };
>
>Doesn't this test require you to add this extension to the list in libavutil/cpu.c as well?
TBH, I don't see the point of this stuff. These options look like cargo cult to me.
_______________________________________________
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".
prev parent reply other threads:[~2024-05-08 6:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 19:12 Rémi Denis-Courmont
2024-05-07 19:12 ` [FFmpeg-devel] [PATCH 2/3] lavu/riscv: add Zvbb CPU capability detection Rémi Denis-Courmont
2024-05-07 19:12 ` [FFmpeg-devel] [PATCH 3/3] lavc/ac3dsp: add R-V Zvbb extract_exponents Rémi Denis-Courmont
2024-05-07 20:34 ` [FFmpeg-devel] [PATCH 1/3] riscv: add Zvbb vector bit manipulation extension Martin Storsjö
2024-05-08 6:22 ` Rémi Denis-Courmont [this message]
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=48C24F9F-9E57-468D-87BC-F32E9718A745@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