From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] ac3dsp: RISC-V V float_to_fixed24
Date: Wed, 22 Nov 2023 15:40:52 +0200
Message-ID: <502DD795-A076-42CF-94EA-11B198219668@remlab.net> (raw)
In-Reply-To: <CAEa-L+uKuW31MEJE=o-DJ58kxPjoWENpJjKdEVfyuPTr-t8=bw@mail.gmail.com>
Hi,
How did you test it? As per http://ffmpeg.org/pipermail/ffmpeg-devel/2023-June/310720.html we still don't have a FATE instance set up with the RISC-V Vector extension. The only testing consists of my manual runs of checkasm on a K230 board. (We *do* have Zba and Zbb now though, hence the existing extract_exponents()).
Also:
- This does not seem according to the C ABI. AFAIK `unsigned` is sign-extended.
- ALU right before dependent conditional branch should be avoided.
- SHxADD can be used advantageously.
Le 22 novembre 2023 14:00:07 GMT+02:00, flow gg <hlefthleft@gmail.com> a écrit :
>c910
> float_to_fixed24_c: 208.2
> float_to_fixed24_rvv_f32: 71.5
_______________________________________________
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-11-22 13:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 12:00 flow gg
2023-11-22 13:40 ` Rémi Denis-Courmont [this message]
2023-11-22 14:30 ` flow gg
2023-11-22 14:35 ` flow gg
2023-11-22 14:51 ` Rémi Denis-Courmont
2023-11-22 16:37 ` flow gg
2023-11-22 16:49 ` James Almer
2023-11-22 23:17 ` flow gg
2023-11-23 17:08 ` Rémi Denis-Courmont
2023-11-23 22:39 ` flow gg
2023-12-01 18:35 ` Rémi Denis-Courmont
2023-12-01 18:38 ` Rémi Denis-Courmont
2023-12-01 19:50 ` flow gg
2023-12-01 20:16 ` flow gg
2023-11-22 17:18 ` James Almer
2023-11-22 17:34 ` flow gg
2023-11-23 7:11 ` flow gg
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=502DD795-A076-42CF-94EA-11B198219668@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