<html dir="ltr"><head><title></title><style type="text/css">#fastmail-quoted #fastmail-quoted-fastmail-quoted #fastmail-quoted-fastmail-quoted-fastmail-quoted p.fastmail-quoted-fastmail-quoted-fastmail-quoted-MsoNormal,#fastmail-quoted #fastmail-quoted-fastmail-quoted #fastmail-quoted-fastmail-quoted-fastmail-quoted p.fastmail-quoted-fastmail-quoted-fastmail-quoted-MsoNoSpacing{margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;}
#fastmail-quoted #fastmail-quoted-fastmail-quoted p.fastmail-quoted-fastmail-quoted-MsoNormal,#fastmail-quoted #fastmail-quoted-fastmail-quoted p.fastmail-quoted-fastmail-quoted-MsoNoSpacing{margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;}
#fastmail-quoted p.fastmail-quoted-MsoNormal,#fastmail-quoted p.fastmail-quoted-MsoNoSpacing{margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;}
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body style="text-align: left; direction: ltr; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div>Ok, I have looked into and addressed:</div><div>1) The misunderstanding around use of NASM. The attached patch set discussed below goes back to using MASM for the big chroma AVX2 enhancement as originally used, (a proper switch to separate NASM based asm files can be perhaps done later), and otherwise drops the other invalid NASM syntax conversion patches.</div><div>2) The compilation failures pointed out with #17 of the earlier set</div><div>3) The compilation issue seen by Remi (someone else's patch already merged may have also helped)</div><div><br></div><div>I have also found and corrected a few other small mistakes I found whilst ensuring that this latest revision compiles correctly.</div><div><br></div><div>Working and writing this offline, I am out of sync with any corrective changes made to git-master regarding the troublesome commits causing compilation issues... When I last was online yesterday no corrective action had yet been taken, except one tiny new configure patch added. So the first few patches in the attached set focus on getting in sync...</div><div><br></div><div>#1 reverts the MMX purge patch (clashes with the next revert)</div><div>#2 reverts the big chroma AVX2 enhancement that we now know to have been fundamentally flawed (nasm misunderstanding)</div><div><br></div><div>of course feel completely free to instead just drop the two respective merged commits (11fc7ec9835e47a8a8cd56a1e0b71a209f1e517b and e04412a31bf8bc246b076843ff8eeb6d7ad1cf1b) and force-update the repo (preferred) or make your own revert commits (to save reviewing my revert commit changes), if you haven't already taken such action...</div><div><br></div><div>#3 is the packetizer startcode-helper AVX2 enhancement patch (unchanged from that merged)</div><div><br></div><div>I mistakenly suggested in my previous email (and in separate public discussion) that this was one to revert/remove, thinking it contained a NASM syntax conversion when actually that was done later; so here it is again in case it has already been incorrectly removed/reverted, otherwise just ignore it...</div><div><br></div><div>#4: fixes the AVX/AVX2 configure inline asm support check, which was actually broken (I overlooked that it used a bad early attempt at AVX/VEX asm)</div><div>#5: addresses the fact that the VLC_AVX define was missing</div><div>#6: applies the revised now MASM based big chroma AVX2 enhancement (and includes a few other compilation fixes)</div><div>#7: fixes broken compilation of the packetizer startcode-helper</div><div>#8: reapplies the MMX purge</div><div>#9: applies a fixed version of #17 from the previous set<br></div><div>#10-17: are the remainder of the not-yet merged patches from before, up to the nasm conversions which are now dropped</div><div><br></div><div>I have checked that this compiles successfully.</div><div><br></div><div>Regards,</div><div><br></div><div>On Wed, 2019-03-06 at 11:17 -0500, Jean-Baptiste Kempf wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Hello Lyndon,<br></div><div><br></div><div>I applied what I could, aka 1-16.<br></div><div><br></div><div>17 does not work, because it fails to compile<br></div><div><br></div><div>CC video_filter/deinterlace/libdeinterlace_plugin_la-helpers.lo<br>../../modules/video_filter/deinterlace/helpers.c: In function ‘EstimateNumBlocksWithMotion’:<br>../../modules/video_filter/deinterlace/helpers.c:243:5: error: output number 0 not directly addressable<br>__asm__ volatile (<br>^~~~~~~<br>../../modules/video_filter/deinterlace/helpers.c:243:5: error: output number 1 not directly addressable<br>../../modules/video_filter/deinterlace/helpers.c:243:5: error: output number 2 not directly addressable<br>../../modules/video_filter/deinterlace/helpers.c: In function ‘CalculateInterlaceScore’:<br>../../modules/video_filter/deinterlace/helpers.c:607:5: error: output number 0 not directly addressable<br>__asm__ volatile ("movd %%xmm7, %0\n" : "=" (i_score_sse) :: "memory");<br>^~~~~~~<br>make[4]: *** [Makefile:21748: video_filter/deinterlace/libdeinterlace_plugin_la-helpers.lo] Error 1</div><div><br></div><div>Best,<br></div><div><br></div><div><br></div><div>On Sun, 3 Mar 2019, at 12:11, Jean-Baptiste Kempf wrote:<br></div><blockquote type="cite" id="fastmail-quoted" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Btw, you moved to the nasm syntax, but not to nasm files? (patches 26-31)<br></div><div><br></div><div>On Thu, 28 Feb 2019, at 00:54, Jean-Baptiste Kempf wrote:<br></div><blockquote id="fastmail-quoted-fastmail-quoted" type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Merci.<br></div><div><br></div><div>On Wed, 27 Feb 2019, at 19:48, jnqnfe@gmail.com wrote:<br></div><blockquote type="cite" id="fastmail-quoted-fastmail-quoted-fastmail-quoted" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Ok, I've rebased and attached<br></div><div><br></div><div>Regarding your issue applying the previous copy, I wonder whether you perhaps missed the note in the first post which pointed out that this built on other patches submitted days earlier? I had no issues rebasing onto git master (except an expected clash with the subsequent MMX purge with someone else's deinterlace work).<br></div><div><br></div><div>The attached rebased patch collection bundles (in order):<br></div><div>- The initial set of general i420_rgb/i420_yuy2/i422_yuy2 fixes (patches 1-11)<br></div><div>- The i420_rgb intrinsics buffer overflow fix (patch 12)<br></div><div>- The i420_rgb/i420_yuy2/i422_yuy2 AVX2 enhancement (patches 13-14)<br></div><div>- The packetizer/startcode_helper AVX2 enhancement (patch 15)<br></div><div>- The purging of MMX/MMXEXT/3Dnow (patches 16-25)<br></div><div>- The conversion of asm to nasm syntax (patches 26-31)<br></div><div><br></div><div>The first of these was approved of by one person who just had a question about the second patch (removal of what I believe are unused RV24 artifacts, which he may have misunderstood as removing RV24 support), I had responded to clarify but then nothing happened. With the second (buffer overflow patch) there was some discussion, but no merge of the patch...<br></div><div><br></div><div>I have taken the opportunity of bundling all of this together, to:<br></div><div>- fixup one patch (fixed a mistake in a larger previous one)<br></div><div>- fix a few commit message typos and such<br></div><div><br></div><div>I have also reworked the MMX purge with the deinterlace plugin on top of the now merged work of Janne Grunau<br></div><div><br></div><div>Oh, I should point out that with the last set, the nasm conversion, which came about from someone suggesting using this for the AVX2 asm (as I then reworked it to use), all I have done is to switch the syntax itself, I have not made any change to the build files (does a hint not need to be given to the compiler to get it to invoke the right assembler?)<br></div><div><br></div><div>Regards,<br></div><div>Lyndon<br></div><div><br></div><div>On Sat, 2019-02-23 at 12:00 -0500, Jean-Baptiste Kempf wrote:<br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Hello Lyndon,<br></div><div><br></div><div>Can you repost all the patches, in the correct order? I cannot apply any of them, in my tree.<br></div><div><br></div><div>Best,<br></div><div><br></div><div>On Thu, 31 Jan 2019, at 09:39, jnqnfe@gmail.com wrote:<br></div><blockquote id="fastmail-quoted-fastmail-quoted-fastmail-quoted-fastmail-quoted" type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>sigh, so here's v4<br></div><div><br></div><div>v3 did not include a conversion of the RGB15 AVX2 to nasm, while the v2<br></div><div>-> v3 diff patch (sent in case you'd already started reviewing v2) did<br></div><div><br></div><div>I'm perplexed as to how on earth that happened, since the diff patch<br></div><div>was a simple fixup into v2 to produce v3...<br></div><div><br></div><div>_______________________________________________<br></div><div>vlc-devel mailing list<br></div><div>To unsubscribe or modify your subscription options:<br></div><div>https://mailman.videolan.org/listinfo/vlc-devel<br></div><div><br></div><div><b>Attachments:</b><br></div><ul><li>chroma_avx2_v4.patch<br></li></ul></blockquote><div><br></div><div id="fastmail-quoted-fastmail-quoted-fastmail-quoted-sig60240713"><div class="fastmail-quoted-fastmail-quoted-fastmail-quoted-signature">--<br></div><div class="fastmail-quoted-fastmail-quoted-fastmail-quoted-signature">Jean-Baptiste Kempf - President<br></div><div class="fastmail-quoted-fastmail-quoted-fastmail-quoted-signature">+33 672 704 734<br></div><div class="fastmail-quoted-fastmail-quoted-fastmail-quoted-signature"> <br></div><div class="fastmail-quoted-fastmail-quoted-fastmail-quoted-signature"><br></div></div><div><br></div></blockquote><div><br></div><div><b>Attachments:</b><br></div><ul><li>patches.zip<br></li></ul></blockquote><div><br></div><div id="fastmail-quoted-fastmail-quoted-sig60240713"><div class="fastmail-quoted-fastmail-quoted-signature">--<br></div><div class="fastmail-quoted-fastmail-quoted-signature">Jean-Baptiste Kempf - President<br></div><div class="fastmail-quoted-fastmail-quoted-signature">+33 672 704 734<br></div><div class="fastmail-quoted-fastmail-quoted-signature"> <br></div><div class="fastmail-quoted-fastmail-quoted-signature"><br></div></div></blockquote><div><br></div><div id="fastmail-quoted-sig60240713"><div class="fastmail-quoted-signature">--<br></div><div class="fastmail-quoted-signature">Jean-Baptiste Kempf - President<br></div><div class="fastmail-quoted-signature">+33 672 704 734<br></div><div class="fastmail-quoted-signature"> <br></div><div class="fastmail-quoted-signature"><br></div></div><div><br></div></blockquote><div><br></div><div id="sig60240713"><div class="signature">--<br></div><div class="signature">Jean-Baptiste Kempf - President<br></div><div class="signature">+33 672 704 734<br></div><div class="signature"> <br></div><div class="signature"><br></div></div><div><br></div></blockquote></body></html>