From: Kieran Kunhya <kierank@obe.tv> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: softworkz <softworkz@hotmail.com> Subject: Re: [FFmpeg-devel] [PATCH v2] tests/fate/vcodec: Limit mem alignment for vsynth..mpeg2-422 tests Date: Sat, 28 May 2022 14:10:59 +0100 Message-ID: <CAK+ULv5+4dWbvr_YZQqox7Odb_Q=j5v_jb0kMJuypQ2_MLP6iA@mail.gmail.com> (raw) In-Reply-To: <pull.32.v2.ffstaging.FFmpeg.1653733190354.ffmpegagent@gmail.com> On Sat, 28 May 2022, 11:20 softworkz, <ffmpegagent@gmail.com> wrote: > From: softworkz <softworkz@hotmail.com> > > These 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> > --- > tests/fate/vcodec: Limit mem alignment for vsynth..mpeg2-422 tests > > Fix FATE tests which are failing on newer x86 CPUs. > > v2: Add the flag on x86 platforms only > > Published-As: > https://github.com/ffstaging/FFmpeg/releases/tag/pr-ffstaging-32%2Fsoftworkz%2Fsubmit_alignment-v2 > Fetch-It-Via > <https://github.com/ffstaging/FFmpeg/releases/tag/pr-ffstaging-32%2Fsoftworkz%2Fsubmit_alignment-v2Fetch-It-Via>: > git fetch https://github.com/ffstaging/FFmpeg > pr-ffstaging-32/softworkz/submit_alignment-v2 > Pull-Request: https://github.com/ffstaging/FFmpeg/pull/32 > > Range-diff vs v1: > > 1: c36271eb6b ! 1: 1586956890 tests/fate/vcodec: Limit mem alignment > for vsynth..mpeg2-422 tests > @@ Commit message > > ## tests/fate/vcodec.mak ## > @@ tests/fate/vcodec.mak: fate-vsynth%-mpeg2-422: ENCOPTS = > -b:v 1000k \ > - -trellis 1 > \ > - -flags +ildct+ilme > \ > -mpv_flags +qp_rd+mv0 > \ > -+ -cpuflags -avx512 > \ > -intra_vlc 1 > \ > -mbd rd > \ > - -pix_fmt yuv422p > +- -pix_fmt yuv422p > ++ -pix_fmt yuv422p > \ > ++ > $(if $(HAVE_MMX), -cpuflags -avx512 ) > ++ > > + fate-vsynth%-mpeg2-idct-int: ENCOPTS = -qscale 10 -idct int > -dct int > + fate-vsynth%-mpeg2-ilace: ENCOPTS = -qscale 10 -flags > +ildct+ilme > + fate-vsynth%-mpeg2-ivlc-qprd: ENCOPTS = -b:v 500k > \ > > > tests/fate/vcodec.mak | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/tests/fate/vcodec.mak b/tests/fate/vcodec.mak > index 8ca17950ea..91228237bd 100644 > --- a/tests/fate/vcodec.mak > +++ b/tests/fate/vcodec.mak > @@ -264,7 +264,9 @@ fate-vsynth%-mpeg2-422: ENCOPTS = -b:v 1000k > \ > -mpv_flags +qp_rd+mv0 \ > -intra_vlc 1 \ > -mbd rd \ > - -pix_fmt yuv422p > + -pix_fmt yuv422p \ > + > $(if $(HAVE_MMX), -cpuflags -avx512 ) > + > > fate-vsynth%-mpeg2-idct-int: ENCOPTS = -qscale 10 -idct int -dct int > fate-vsynth%-mpeg2-ilace: ENCOPTS = -qscale 10 -flags +ildct+ilme > fate-vsynth%-mpeg2-ivlc-qprd: ENCOPTS = -b:v 500k \ > > base-commit: 9fba0b8a8c754a012fc74c90ffb7c26a56be8ca0 > -- > ffmpeg-codebot > _______________________________________________ > Huh, this is horrible. Kieran > _______________________________________________ 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-28 13:11 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 [this message] 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
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='CAK+ULv5+4dWbvr_YZQqox7Odb_Q=j5v_jb0kMJuypQ2_MLP6iA@mail.gmail.com' \ --to=kierank@obe.tv \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=softworkz@hotmail.com \ /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