From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v4 1/9] lavc/vp8dsp: R-V put_vp8_pixels
Date: Tue, 07 May 2024 21:25:33 +0300
Message-ID: <2951543.e9J7NaK4W3@basile.remlab.net> (raw)
In-Reply-To: <NxJ8Ln2--B-9@lynne.ee>
Le tiistaina 7. toukokuuta 2024, 20.41.30 EEST Lynne a écrit :
> May 7, 2024, 18:54 by uk7b@foxmail.com:
> > From: sunyuechi <sunyuechi@iscas.ac.cn>
> >
> > C908:
> > vp8_put_pixels4_c: 78.0
> > vp8_put_pixels4_rvi: 33.7
> > vp8_put_pixels8_c: 278.0
> > vp8_put_pixels8_rvi: 55.0
> > vp8_put_pixels16_c: 999.0
> > vp8_put_pixels16_rvi: 86.7
> > ---
> >
> > libavcodec/riscv/Makefile | 1 +
> > libavcodec/riscv/vp8dsp.h | 75 ++++++++++++++++++++++++++++++++++
> > libavcodec/riscv/vp8dsp_init.c | 22 ++++++++++
> > libavcodec/riscv/vp8dsp_rvi.S | 61 +++++++++++++++++++++++++++
> > libavcodec/vp8dsp.c | 2 +
> > libavcodec/vp8dsp.h | 1 +
> > 6 files changed, 162 insertions(+)
> > create mode 100644 libavcodec/riscv/vp8dsp.h
> > create mode 100644 libavcodec/riscv/vp8dsp_rvi.S
> >
> > +
> > +av_cold void ff_vp78dsp_init_riscv(VP8DSPContext *c)
> > +{
> > +#if HAVE_RV
> > + int flags = av_get_cpu_flags();
> > + if (flags & AV_CPU_FLAG_RVI) {
> > +#if __riscv_xlen >= 64
>
> Why are you not detecting this at runtime?
XLEN is a compile time constant of the ABI. You cannot run 32-bit code in 64-
bit mode, and the ELF loader will not allow you to do so.
--
Rémi Denis-Courmont
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:[~2024-05-07 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 16:54 uk7b
2024-05-07 17:41 ` Lynne
2024-05-07 18:25 ` Rémi Denis-Courmont [this message]
2024-05-07 19:25 ` Lynne
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=2951543.e9J7NaK4W3@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