From: Anton Khirnov <anton@khirnov.net>
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
Date: Mon, 30 May 2022 12:31:41 +0200
Message-ID: <165390670132.5088.13381302396190365073@lain.red.khirnov.net> (raw)
In-Reply-To: =?utf-8?q?=3CDM8P223MB0365DFCF500101024FBD0854BADD9=40DM8P223MB?= =?utf-8?q?0365=2ENAMP223=2EPROD=2EOUTLOOK=2ECOM=3E?=
Quoting Soft Works (2022-05-30 11:26:56)
> Well, the test .mak files are full of hacks then, with the many super-
> special flags in place that do not reflect any real world use at all.
There are AFAIK zero tests that override cpuflags.
>
> That flag does nothing more than to assure that the tests are run
> under the same conditions under which the ref files were generated.
Most of the code is supposed to be arch-independent. A test producing
different results on different architectures should be considered a bug.
--
Anton Khirnov
_______________________________________________
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:[~2022-05-30 10:31 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 [this message]
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
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=165390670132.5088.13381302396190365073@lain.red.khirnov.net \
--to=anton@khirnov.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