From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavc/rv34dsp: optimise R-V V idct_dc_add
Date: Wed, 22 May 2024 23:34:45 +0300
Message-ID: <48C0CA03-9507-4C31-96A7-2FF7FE23210C@remlab.net> (raw)
In-Reply-To: <20240522202854.15461-1-remi@remlab.net>
Le 22 mai 2024 23:28:54 GMT+03:00, "Rémi Denis-Courmont" <remi@remlab.net> a écrit :
>This removes one stray LI and reworks the vector arithmetic to avoid
>changing the vector configuration. On K230, this takes the 46.5 cycle
>count down from 46.5 to 43.5.
>---
> libavcodec/riscv/rv34dsp_rvv.S | 13 ++++++-------
> 1 file changed, 6 insertions(+), 7 deletions(-)
>
>diff --git a/libavcodec/riscv/rv34dsp_rvv.S b/libavcodec/riscv/rv34dsp_rvv.S
>index f1f6345012..e8aff7e570 100644
>--- a/libavcodec/riscv/rv34dsp_rvv.S
>+++ b/libavcodec/riscv/rv34dsp_rvv.S
>@@ -36,16 +36,15 @@ func ff_rv34_idct_dc_add_rvv, zve32x
> vsetivli zero, 4, e8, mf4, ta, ma
> vlse32.v v0, (a0), a1
> li t1, 169
>+ li t2, 128
> mul t1, t1, a2
>- li a2, 255
>+ vsetivli zero, 4*4, e8, m1, ta, ma
>+ vwsubu.vx v2, v0, t2
> addi t1, t1, 512
> srai t1, t1, 10
>- vsetivli zero, 4*4, e16, m2, ta, ma
>- vzext.vf2 v2, v0
>- vadd.vx v2, v2, t1
>- vmax.vx v2, v2, zero
>- vsetvli zero, zero, e8, m1, ta, ma
>- vnclipu.wi v0, v2, 0
>+ vwadd.wx v2, v2, t1
Hmm, this should not work, as t1 has more than 8 bits. Maybe checkasm is sloppy here.
>+ vnclip.wi v0, v2, 0
>+ vxor.vx v0, v0, t2
> vsetivli zero, 4, e8, mf4, ta, ma
> vsse32.v v0, (a0), a1
>
_______________________________________________
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-05-22 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 20:28 Rémi Denis-Courmont
2024-05-22 20:34 ` Rémi Denis-Courmont [this message]
2024-05-23 3:31 ` flow gg
2024-05-23 8:33 ` 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=48C0CA03-9507-4C31-96A7-2FF7FE23210C@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