Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2] tests/fate/vcodec: Limit mem alignment for vsynth..mpeg2-422 tests
Date: Mon, 30 May 2022 12:50:51 +0200
Message-ID: <DB6PR0101MB2214E83FE17FCF3BD3A947C98FDD9@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <165390646557.5088.1947053732972422450@lain.red.khirnov.net>

Anton Khirnov:
> Quoting Soft Works (2022-05-30 10:35:26)
>>
>>
>>> -----Original Message-----
>>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
>>> Anton Khirnov
>>> Sent: Monday, May 30, 2022 9:35 AM
>>> To: FFmpeg development discussions and patches <ffmpeg-
>>> devel@ffmpeg.org>
>>> Subject: Re: [FFmpeg-devel] [PATCH v2] tests/fate/vcodec: Limit mem
>>> alignment for vsynth..mpeg2-422 tests
>>>
>>> Quoting Soft Works (2022-05-28 15:17:54)
>>>> Do you have a better idea?
>>>>
>>>> The one advantage of this method is that you don’t need to change
>>> compilation parameters
>>>> nor  any source code. It’s only a runtime flag being set only for
>>> this specific family of tests.
>>>
>>> At the very least, I would expect the commit message to explain what
>>> exactly the problem is, and why is it fixed in this seemingly ad-hoc
>>> manner.
>>>
>>> "limit mem alignment to fix failing tests" explains nothing.
>>
>> BTW, that's not the actual commit message.
>> What I have submitted is this:
> 
> It's effectively equivalent to my summary.
> 
>> ------------------------
>>
>> tests/fate/vcodec: Limit mem alignment for vsynth..mpeg2-422 tests
>>
>> The tests:
>>
>> - vsynth2-mpeg2-422
>> - vsynth1-mpeg2-422
>> - vsynth_lena-mpeg2-422
>>
>> were failing on newer CPUs where av_cpu_max_align() returns
>> values > 32. This patch sets cpuflags to disable avx512
>> extensions for those tests only.
>>
>> Signed-off-by: softworkz <softworkz@hotmail.com>
>>
>> ------------------------
>>
>> What do you want me to add to it?
> 
> Why are those specific tests failing?
> 
> Why is the failure fixed in this specific way.
> 

The only thing known is that always using direct = 0 in
load_input_picture in mpegvideo_enc.c causes the bug to disappear.
Looking at the code shows that the code that is run when direct == 0
sometimes expects a vertical alignment of 32, whereas the check for
whether direct should be set to zero always checks for a vertical
alignment of 16. Yet fixing this discrepancy by setting vpad earlier and
using this at both places does not fix the issue.
To be honest, everything that has to do with whether or not to reuse the
picture (and the padding/edges of the pictures the code can rely upon)
feels like black magic to me.

- Andreas
_______________________________________________
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:[~2022-05-30 10:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-28  9:08 [FFmpeg-devel] [PATCH] " softworkz
2022-05-28 10:19 ` [FFmpeg-devel] [PATCH v2] " softworkz
2022-05-28 13:10   ` Kieran Kunhya
2022-05-28 13:17     ` Soft Works
2022-05-30  7:35     ` Anton Khirnov
2022-05-30  8:08       ` Soft Works
2022-05-30  8:17         ` Soft Works
2022-05-30  8:35       ` Soft Works
2022-05-30  9:06         ` Paul B Mahol
2022-05-30  9:26           ` Soft Works
2022-05-30 10:31           ` Anton Khirnov
2022-05-30 10:24       ` Anton Khirnov
2022-05-30 10:56         ` Soft Works
2022-05-30 10:27       ` Anton Khirnov
2022-05-30 10:50         ` Andreas Rheinhardt [this message]

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=DB6PR0101MB2214E83FE17FCF3BD3A947C98FDD9@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com \
    --to=andreas.rheinhardt@outlook.com \
    --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