From: "Rémi Denis-Courmont" <remi@remlab.net>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH 5/6] lavc/idctdsp: improve R-V V add_pixels_clamped
Date: Fri, 27 Oct 2023 22:25:39 +0300
Message-ID: <20231027192540.27373-5-remi@remlab.net> (raw)
---
libavcodec/riscv/idctdsp_rvv.S | 28 ++++++++++++++--------------
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/libavcodec/riscv/idctdsp_rvv.S b/libavcodec/riscv/idctdsp_rvv.S
index 4ff72f48d2..fafdddb174 100644
--- a/libavcodec/riscv/idctdsp_rvv.S
+++ b/libavcodec/riscv/idctdsp_rvv.S
@@ -23,7 +23,6 @@
func ff_put_pixels_clamped_rvv, zve32x
vsetivli zero, 8, e16, m1, ta, ma
vlseg8e16.v v24, (a0)
-1:
/* RVV only has signed-signed and unsigned-unsigned clipping.
* We need two steps for signed-to-unsigned clipping. */
vsetvli t0, zero, e16, m8, ta, ma
@@ -54,17 +53,18 @@ func ff_put_signed_pixels_clamped_rvv, zve64x
ret
endfunc
-func ff_add_pixels_clamped_rvv, zve32x
- vsetivli zero, 8, e8, mf2, ta, ma
- vlseg8e16.v v24, (a0)
- vlsseg8e8.v v16, (a1), a2
- vwaddu.wv v24, v24, v16
- vwaddu.wv v25, v25, v17
- vwaddu.wv v26, v26, v18
- vwaddu.wv v27, v27, v19
- vwaddu.wv v28, v28, v20
- vwaddu.wv v29, v29, v21
- vwaddu.wv v30, v30, v22
- vwaddu.wv v31, v31, v23
- j 1b
+func ff_add_pixels_clamped_rvv, zve64x
+ vsetivli zero, 8, e8, mf2, ta, ma
+ li t0, 8 * 8
+ vlse64.v v16, (a1), a2
+ vsetvli zero, t0, e8, m4, ta, ma
+ vle16.v v24, (a0)
+ vwaddu.wv v24, v24, v16
+ vsetvli zero, zero, e16, m8, ta, ma
+ vmax.vx v24, v24, zero
+ vsetvli zero, zero, e8, m4, ta, ma
+ vnclipu.wi v16, v24, 0
+ vsetivli zero, 8, e8, mf2, ta, ma
+ vsse64.v v16, (a1), a2
+ ret
endfunc
--
2.42.0
_______________________________________________
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".
reply other threads:[~2023-10-27 19:26 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=20231027192540.27373-5-remi@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