From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v3 1/9] lavc/vp9dsp: R-V ipred vert
Date: Tue, 14 May 2024 20:00:16 +0300
Message-ID: <2106469.utUORKxbUX@basile.remlab.net> (raw)
In-Reply-To: <CAEa-L+su4qdONZxe6yDifT5Y-ZBFZhcU98Kj2gqJgOXQZqjZFA@mail.gmail.com>
Le tiistaina 14. toukokuuta 2024, 7.45.29 EEST flow gg a écrit :
> I am locally using:
> if (bpp == 8 && (flags & AV_CPU_FLAG_RVI) && (flags &
> AV_CPU_FLAG_RVB_ADDR)) {
There is no point testing the I flag if you test any other flag. The I flag is
always set (since we don't, and probably never will, support RV32E) and only
exists for the benefit of checkasm.
> this performs better on k230/banana_f3 than C.
It also performs better than C on SiFive U74, even though that design has
veeeeeery slow unaligned access (emulated in SBI). Of course, it could just be
that checkasm only tests aligned accesses and unaligned accesses are legal,
hence my earlier question.
--
レミ・デニ-クールモン
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-14 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 16:59 uk7b
2024-05-13 17:01 ` flow gg
2024-05-13 19:47 ` Rémi Denis-Courmont
2024-05-13 19:53 ` Rémi Denis-Courmont
2024-05-14 4:45 ` flow gg
2024-05-14 17:00 ` Rémi Denis-Courmont [this message]
2024-05-14 17:22 ` flow gg
-- strict thread matches above, loose matches on Subject: below --
2024-05-12 10:03 uk7b
2024-05-12 10:06 ` 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=2106469.utUORKxbUX@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