From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 6/6] lavc/takdsp: R-V V decorrelate_sm
Date: Fri, 22 Dec 2023 17:34:45 +0200
Message-ID: <5998736.lOV4Wx5bFT@basile.remlab.net> (raw)
In-Reply-To: <CAEa-L+v=ijvXNbVUPpOq4D=QEiwsbw42Gco__qwUZzGRMc8W-A@mail.gmail.com>
Le perjantaina 22. joulukuuta 2023, 3.34.39 EET flow gg a écrit :
> func ff_decorrelate_sm_rvv, zve32x
> 1:
> vsetvli t0, a2, e32, m8, ta, ma
> vle32.v v8, (a1)
> sub a2, a2, t0
> vle32.v v0, (a0)
> vssra.vi v8, v8, 1
> vsub.vv v16, v0, v8
> vse32.v v16, (a0)
> sh2add a0, t0, a0
> vadd.vv v16, v0, v8
> vse32.v v16, (a1)
> sh2add a1, t0, a1
> bnez a2, 1b
> ret
> endfunc
>
> Is this way? In this situation, or when using vsra, there will be some
> tests that fail, and the result value differs by 1. I'm not sure where the
> problem..
No, I meant something like this, but it turns out slightly slower anyway.
Saving the data dependency is not worth adding an instruction.
func ff_decorrelate_sm_rvv, zve32x
csrwi vxrm, 0
1:
vsetvli t0, a2, e32, m8, ta, ma
vle32.v v8, (a1)
sub a2, a2, t0
vle32.v v0, (a0)
vsra.vi v16, v8, 1
vssra.vi v8, v8, 1
vsub.vv v16, v0, v16
vadd.vv v8, v0, v8
vse32.v v16, (a0)
sh2add a0, t0, a0
vse32.v v8, (a1)
sh2add a1, t0, a1
bnez a2, 1b
ret
endfunc
--
雷米‧德尼-库尔蒙
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".
prev parent reply other threads:[~2023-12-22 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 15:16 flow gg
2023-12-21 16:07 ` Rémi Denis-Courmont
2023-12-21 16:11 ` Rémi Denis-Courmont
2023-12-22 1:34 ` flow gg
2023-12-22 15:34 ` 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=5998736.lOV4Wx5bFT@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