On Mon, 29 Oct 2012, Ronald S. Bultje wrote:
On Mon, Oct 29, 2012 at 5:15 PM, Diego Biurrun di...@biurrun.de wrote:
This allows using mmxext as name in Libav while staying compatible
with changes to the YASM macro infrastructure imported from x264.
---
libavutil/x86/x86inc.asm |1 +
1
Loren Merritt lor...@u.washington.edu writes:
On Mon, 29 Oct 2012, Ronald S. Bultje wrote:
On Mon, Oct 29, 2012 at 5:15 PM, Diego Biurrun di...@biurrun.de wrote:
This allows using mmxext as name in Libav while staying compatible
with changes to the YASM macro infrastructure imported from
This allows using mmxext as name in Libav while staying compatible
with changes to the YASM macro infrastructure imported from x264.
---
libavutil/x86/x86inc.asm |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/libavutil/x86/x86inc.asm b/libavutil/x86/x86inc.asm
index
Hi,
On Mon, Oct 29, 2012 at 5:15 PM, Diego Biurrun di...@biurrun.de wrote:
This allows using mmxext as name in Libav while staying compatible
with changes to the YASM macro infrastructure imported from x264.
---
libavutil/x86/x86inc.asm |1 +
1 files changed, 1 insertions(+), 0
On Mon, Oct 29, 2012 at 05:25:08PM -0700, Ronald S. Bultje wrote:
On Mon, Oct 29, 2012 at 5:15 PM, Diego Biurrun di...@biurrun.de wrote:
This allows using mmxext as name in Libav while staying compatible
with changes to the YASM macro infrastructure imported from x264.
---
Hi,
On Mon, Oct 29, 2012 at 5:56 PM, Diego Biurrun di...@biurrun.de wrote:
On Mon, Oct 29, 2012 at 05:25:08PM -0700, Ronald S. Bultje wrote:
On Mon, Oct 29, 2012 at 5:15 PM, Diego Biurrun di...@biurrun.de wrote:
This allows using mmxext as name in Libav while staying compatible
with changes
