On Wed, May 24, 2023 at 9:56 PM Nomis101 <[email protected]> wrote: > Am 24.05.23 um 10:04 schrieb Sam: > > > > On Wed, May 24, 2023 at 12:55 PM Mario *LigH* Rohkrämer <[email protected]> > wrote: > > > > Yes, it looks a lot more tidy. Just a few warnings left. > > > > > > chen schrieb am 24.05.2023 um 06:13: > > > Hello, > > > > > > Could you please try my local patch? > > > > > > Regards, > > > Min Chen > > > > > > 2023-05-21 17:27:35，"Mario *LigH* Rohkrämer" <[email protected]> > > >>Almost 3 years later, NASM version 2.16.01, and still no solution, > > >>nobody is responsible for "just" warnings. > > >> > > >>-- > > >> > > >>Fun and success! > > >> > > >>Mario *LigH* Rohkrämer > > >>maito:[email protected] <mailto:maito%[email protected]> > > >> > > > > > > > > > _______________________________________________ > > > x265-devel mailing list > > > [email protected] > > > https://mailman.videolan.org/listinfo/x265-devel > > > > > > > > > If you take a look at Patman's x265 mod, there are a couple of fixes > that seem to get rid of the > > warnings. > > > > > https://github.com/Patman86/x265-Mod-by-Patman/commit/1ecd3d79ac5f3f2883650ca8f9b4c18c8f2b864c > > > > This one is similar to the one I submitted 3 years ago and to the fix that > is applied for x264. > https://mailman.videolan.org/pipermail/x265-devel/2020-July/013062.html
Pushed the above patch, fixing warnings in both NASM 2.15.03 and 2.16.01 > > > > > > > Sami > > > > _______________________________________________ > > x265-devel mailing list > > [email protected] > > https://mailman.videolan.org/listinfo/x265-devel > > _______________________________________________ > x265-devel mailing list > [email protected] > https://mailman.videolan.org/listinfo/x265-devel >
_______________________________________________ x265-devel mailing list [email protected] https://mailman.videolan.org/listinfo/x265-devel
