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 development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] swscale/aarch64: Add rgb24 to yuv implementation
Date: Mon, 03 Jun 2024 17:17:32 +0300
Message-ID: <5613793.InHtYnbKhy@basile.remlab.net> (raw)
In-Reply-To: <tencent_5D5D40BD9AD09F69AB094E6570D92DE29A08@qq.com>

Le maanantaina 3. kesäkuuta 2024, 16.11.15 EEST Zhao Zhili a écrit :
> > See https://github.com/mstorsjo/FFmpeg/actions/runs/9346228714 for one
> > example run of these actions with your patches.
> Wow, it’s very helpful. This is the action result of the updated patch:
> 
> https://github.com/quink-black/FFmpeg/actions/runs/9350348848
> 
> https://ffmpeg.org/pipermail/ffmpeg-devel/2024-June/328786.html
> 
> The test still failed on x86, but success on all arm64 platform and
> longarch. I have tried to call rgb24ToY_c and ff_rgb24ToY_avx
> directly and compare the results, they don't match. I’m confused.

As Martin write, some x86 code is imprecise, or even wrong.

I would just disable the test on x86 until some x86 arcane magician fixes it.

-- 
雷米‧德尼-库尔蒙
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-03 14:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240603071732.52523-1-quinkblack@foxmail.com>
2024-06-03  7:17 ` Zhao Zhili
2024-06-03  8:07   ` Martin Storsjö
2024-06-03 13:11     ` Zhao Zhili
2024-06-03 14:17       ` Rémi Denis-Courmont [this message]
2024-06-03 16:14         ` Zhao Zhili
2024-06-03 17:22           ` Ronald S. Bultje

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=5613793.InHtYnbKhy@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