From: "Rémi Denis-Courmont" <remi@remlab.net> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH v2] riscv: Tweak names of cpu flags, print flags in libavutil/tests/cpu Date: Sun, 17 Dec 2023 10:37:10 +0200 Message-ID: <9844061.a3KcacsRcm@basile.remlab.net> (raw) In-Reply-To: <20231215205251.189618-1-martin@martin.st> Le perjantaina 15. joulukuuta 2023, 22.52.51 EET Martin Storsjö a écrit : > The names of the cpu flags, when parsed from a string with > av_parse_cpu_caps, are parsed by the libavutil eval functions. These > interpret dashes as subtractions. Therefore, these previous cpu flag > names haven't been possible to set. > > Use the official names for these extensions, as the previous ad-hoc > names wasn't parseable. > > libavutil/tests/cpu tests that the cpu flags can be set, and prints > the detected flags. > --- > libavutil/cpu.c | 12 ++++++------ > libavutil/tests/cpu.c | 10 ++++++++++ > 2 files changed, 16 insertions(+), 6 deletions(-) > > diff --git a/libavutil/cpu.c b/libavutil/cpu.c > index 1e0607d581..f04068acda 100644 > --- a/libavutil/cpu.c > +++ b/libavutil/cpu.c > @@ -186,12 +186,12 @@ int av_parse_cpu_caps(unsigned *flags, const char *s) > { "rvi", NULL, 0, AV_OPT_TYPE_CONST, { .i64 = AV_CPU_FLAG_RVI > }, .unit = "flags" }, { "rvf", NULL, 0, AV_OPT_TYPE_CONST, { > .i64 = AV_CPU_FLAG_RVF }, .unit = "flags" }, { "rvd", NULL, 0, > AV_OPT_TYPE_CONST, { .i64 = AV_CPU_FLAG_RVD }, .unit = "flags" }, - > { "rvv-i32", NULL, 0, AV_OPT_TYPE_CONST, { .i64 = > AV_CPU_FLAG_RVV_I32 }, .unit = "flags" }, - { "rvv-f32", NULL, > 0, AV_OPT_TYPE_CONST, { .i64 = AV_CPU_FLAG_RVV_F32 }, .unit = "flags" > }, - { "rvv-i64", NULL, 0, AV_OPT_TYPE_CONST, { .i64 = > AV_CPU_FLAG_RVV_I64 }, .unit = "flags" }, - { "rvv", NULL, > 0, AV_OPT_TYPE_CONST, { .i64 = AV_CPU_FLAG_RVV_F64 }, .unit = "flags" > }, - { "rvb-addr",NULL, 0, AV_OPT_TYPE_CONST, { .i64 = > AV_CPU_FLAG_RVB_ADDR }, .unit = "flags" }, - { "rvb-basic",NULL, > 0, AV_OPT_TYPE_CONST, { .i64 = AV_CPU_FLAG_RVB_BASIC }, .unit = "flags" > }, + { "zve32x", NULL, 0, AV_OPT_TYPE_CONST, { .i64 = > AV_CPU_FLAG_RVV_I32 }, .unit = "flags" }, + { "zve32f", NULL, > 0, AV_OPT_TYPE_CONST, { .i64 = AV_CPU_FLAG_RVV_F32 }, .unit = "flags" > }, + { "zve64x", NULL, 0, AV_OPT_TYPE_CONST, { .i64 = > AV_CPU_FLAG_RVV_I64 }, .unit = "flags" }, > + { "zve64f", NULL, > 0, AV_OPT_TYPE_CONST, { .i64 = AV_CPU_FLAG_RVV_F64 }, .unit = "flags" That's Zve64d. Or V though strictly speaking V also implies a vector length of at least 128 bits, while Zve64d only implies 64 bits. > }, + { "zba", NULL, 0, AV_OPT_TYPE_CONST, { .i64 = > AV_CPU_FLAG_RVB_ADDR }, .unit = "flags" }, + { "zbb", NULL, > 0, AV_OPT_TYPE_CONST, { .i64 = AV_CPU_FLAG_RVB_BASIC }, .unit = "flags" > }, #endif > { NULL }, > }; > diff --git a/libavutil/tests/cpu.c b/libavutil/tests/cpu.c > index 200f20388a..6b27bcdbad 100644 > --- a/libavutil/tests/cpu.c > +++ b/libavutil/tests/cpu.c > @@ -84,6 +84,16 @@ static const struct { > #elif ARCH_LOONGARCH > { AV_CPU_FLAG_LSX, "lsx" }, > { AV_CPU_FLAG_LASX, "lasx" }, > +#elif ARCH_RISCV > + { AV_CPU_FLAG_RVI, "rvi" }, > + { AV_CPU_FLAG_RVF, "rvf" }, > + { AV_CPU_FLAG_RVD, "rvd" }, > + { AV_CPU_FLAG_RVB_ADDR, "zba" }, > + { AV_CPU_FLAG_RVB_BASIC, "zbb" }, > + { AV_CPU_FLAG_RVV_I32, "zve32x" }, > + { AV_CPU_FLAG_RVV_F32, "zve32f" }, > + { AV_CPU_FLAG_RVV_I64, "zve64x" }, > + { AV_CPU_FLAG_RVV_F64, "zve64f" }, > #endif > { 0 } > }; -- レミ・デニ-クールモン 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".
next prev parent reply other threads:[~2023-12-17 8:37 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-15 20:52 Martin Storsjö 2023-12-17 8:37 ` Rémi Denis-Courmont [this message] 2023-12-17 9:11 ` Martin Storsjö 2023-12-17 9:27 ` 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=9844061.a3KcacsRcm@basile.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