Hi, On Fri, Aug 3, 2012 at 5:54 AM, Diego Biurrun <[email protected]> wrote: > On Thu, Aug 02, 2012 at 09:59:54PM -0700, Ronald S. Bultje wrote: >> On Thu, Aug 2, 2012 at 1:45 PM, Diego Biurrun <[email protected]> wrote: >> > Refactoring mmx2/mmxext YASM code with cpuflags will force renames. >> > So switching to a consistent naming scheme beforehand is sensible. >> > The name "mmxext" is more official and widespread and also the name >> > of the CPU flag, as reported e.g. by the Linux kernel. >> >> I have to be honest, I really don't care much for the name of the >> beast, but fine, if this is what people prefer, we can go with it. >> >> Please document it in APIChanges (AV_CPU_FLAG_MMX2 -> MMXEXT), then OK to >> apply. > > I added the following to APIChanges locally: > > 2012-08-03 - xxxxxxx - lavu 54.13.0 - cpu.h > lsws 2.1.1 - swscale.h > Rename AV_CPU_FLAG_MMX2 ---> AV_CPU_FLAG_MMXEXT. > Rename SWS_CPU_CAPS_MMX2 ---> SWS_CPU_CAPS_MMXEXT. > > Does your OK extend to the whole set of mmx2 --> mmxext renames? > And do you guys prefer me to squash those patches into one?
No, I only OK'ed this one. The other ones I still have to review the code. Ronald _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
