Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] lavc/vc1dsp: match C block layout in inv_trans_4x8_rvv
Date: Tue, 11 Jun 2024 17:53:04 +0300
Message-ID: <4929107.rjQTLOYEdK@basile.remlab.net> (raw)
In-Reply-To: <e51dd50e-44d5-4393-acd0-c2b16117fb00@gmail.com>

Le tiistaina 11. kesäkuuta 2024, 15.23.11 EEST James Almer a écrit :
> On 6/11/2024 9:19 AM, Rémi Denis-Courmont wrote:
> > Le 11 juin 2024 15:09:42 GMT+03:00, "Ronald S. Bultje" 
<rsbultje@gmail.com> a écrit :
> >> Hi,
> >> 
> >> On Mon, Jun 10, 2024 at 3:20 PM Rémi Denis-Courmont <remi@remlab.net> 
wrote:
> >>> Although checkasm does not verify this, the decoder requires that the
> >>> transform updates the input block exactly like the C code does.
> >> 
> >> Would it be possible to update the checkasm test to verify this?
> > 
> > In theory, it has to be possible. I can't do it for lack of knowledge
> > about VC-1 though. James tried to make such a patch but it ended up
> > failing both AArch64 and RVV 8x4 transforms. I don't know if this points
> > to a latent bug or is a false positive.
> My patch added a memcmp of the block buffer. If it fails, then the asm
> implementation is probably writing more than it should.

The patch has two bugs that end up cancelling one another.

> Can you see what bytes don't match? It might give you an idea of what
> store instruction is touching the wrong bytes.

The RVV transform is failing because it stores different values in the right 
places. I will attach patches here, but it is entirely unclear to me if this 
is necessary at all; at least, it does not seem to fix anything in FATE, and it 
causes the pre-existing AArch64 functions to fail checkasm.

-- 
レミ・デニ-クールモン
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".

  reply	other threads:[~2024-06-11 14:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10 19:03 [FFmpeg-devel] [PATCH] lavc/vc1dsp: match C block layout in inv_trans_4x4_rvv Rémi Denis-Courmont
2024-06-10 19:20 ` [FFmpeg-devel] [PATCH] lavc/vc1dsp: match C block layout in inv_trans_4x8_rvv Rémi Denis-Courmont
2024-06-11 12:09   ` Ronald S. Bultje
2024-06-11 12:19     ` Rémi Denis-Courmont
2024-06-11 12:23       ` James Almer
2024-06-11 14:53         ` Rémi Denis-Courmont [this message]
2024-06-11 14:55           ` [FFmpeg-devel] [PATCH 1/2] lavc/vc1dsp: match C block content in inv_trans_8x4_rvv Rémi Denis-Courmont
2024-06-11 14:55           ` [FFmpeg-devel] [PATCH 2/2] checkasm/vc1dsp: check the not-in-place block content Rémi Denis-Courmont
2024-06-11 15:08             ` James Almer
2024-06-11 15:34               ` Rémi Denis-Courmont

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=4929107.rjQTLOYEdK@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