<div dir="ltr"><div dir="ltr">On Wed, May 24, 2023 at 9:56 PM Nomis101 <<a href="mailto:Nomis101@web.de">Nomis101@web.de</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Am 24.05.23 um 10:04 schrieb Sam:<br>
><br>
> On Wed, May 24, 2023 at 12:55 PM Mario *LigH* Rohkrämer <<a href="mailto:contact@ligh.de" target="_blank">contact@ligh.de</a>> wrote:<br>
><br>
>     Yes, it looks a lot more tidy. Just a few warnings left.<br>
><br>
><br>
>     chen schrieb am 24.05.2023 um 06:13:<br>
>     > Hello,<br>
>     ><br>
>     > Could you please try my local patch?<br>
>     ><br>
>     > Regards,<br>
>     > Min Chen<br>
>     ><br>
>     > 2023-05-21 17:27:35，"Mario *LigH* Rohkrämer" <<a href="mailto:contact@ligh.de" target="_blank">contact@ligh.de</a>><br>
>     >>Almost 3 years later, NASM version 2.16.01, and still no solution,<br>
>     >>nobody is responsible for "just" warnings.<br>
>     >><br>
>     >>--<br>
>     >><br>
>     >>Fun and success!<br>
>     >><br>
>     >>Mario *LigH* Rohkrämer<br>
>     >><a href="mailto:maito%3Acontact@ligh.de" target="_blank">maito:contact@ligh.de</a> <mailto:<a href="mailto:maito%253Acontact@ligh.de" target="_blank">maito%3Acontact@ligh.de</a>><br>
>     >><br>
>     ><br>
>     ><br>
>     > _______________________________________________<br>
>     > x265-devel mailing list<br>
>     > <a href="mailto:x265-devel@videolan.org" target="_blank">x265-devel@videolan.org</a><br>
>     > <a href="https://mailman.videolan.org/listinfo/x265-devel" rel="noreferrer" target="_blank">https://mailman.videolan.org/listinfo/x265-devel</a><br>
>     ><br>
><br>
><br>
> If you take a look at Patman's x265 mod, there are a couple of fixes that seem to get rid of the <br>
> warnings.<br>
><br>
> <a href="https://github.com/Patman86/x265-Mod-by-Patman/commit/1ecd3d79ac5f3f2883650ca8f9b4c18c8f2b864c" rel="noreferrer" target="_blank">https://github.com/Patman86/x265-Mod-by-Patman/commit/1ecd3d79ac5f3f2883650ca8f9b4c18c8f2b864c</a><br>
><br>
<br>
This one is similar to the one I submitted 3 years ago and to the fix that is applied for x264.<br>
<a href="https://mailman.videolan.org/pipermail/x265-devel/2020-July/013062.html" rel="noreferrer" target="_blank">https://mailman.videolan.org/pipermail/x265-devel/2020-July/013062.html</a></blockquote><div>Pushed the above patch, fixing warnings in both NASM 2.15.03 and 2.16.01</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
<br>
<br>
<br>
> Sami<br>
><br>
> _______________________________________________<br>
> x265-devel mailing list<br>
> <a href="mailto:x265-devel@videolan.org" target="_blank">x265-devel@videolan.org</a><br>
> <a href="https://mailman.videolan.org/listinfo/x265-devel" rel="noreferrer" target="_blank">https://mailman.videolan.org/listinfo/x265-devel</a><br>
<br>
_______________________________________________<br>
x265-devel mailing list<br>
<a href="mailto:x265-devel@videolan.org" target="_blank">x265-devel@videolan.org</a><br>
<a href="https://mailman.videolan.org/listinfo/x265-devel" rel="noreferrer" target="_blank">https://mailman.videolan.org/listinfo/x265-devel</a><br>
</blockquote></div></div>