It appears that something goes wrong in old nasm versions when the
%+ operator is used in the last argument of a macro invocation and
this argument is tested with %ifdef within the macro.  This patch
rearranges the macro arguments such that the %+ operator is never
used in the last argument.

nasm does not support 'CPU foonop' directives.  This adds a configure
test for the directive and uses it only if supported.
Signed-off-by: Mans Rullgard <mans@mansr.com>

For some reason, nasm requires this.  No harm done to yasm.
Signed-off-by: Mans Rullgard <mans@mansr.com>

nasm requires a trailing / on paths specified with -I.
It does no harm with yasm.
Signed-off-by: Mans Rullgard <mans@mansr.com>

yasm tolerates mismatch between movd/movq and source register size,
adjusting the instruction according to the register.  nasm is more
strict.
Signed-off-by: Mans Rullgard <mans@mansr.com>

nasm prints a warning if the colon is missing.
Signed-off-by: Mans Rullgard <mans@mansr.com>

This installs libraries using the proper names and locations,
generates an import lib for the DLL, and drops no longer needed
linker flags.
Signed-off-by: Mans Rullgard <mans@mansr.com>

Ensures that the next frame decoded after seeking will be decoded as a
keyframe.

Fixes mpc8 timestamps.

This simplifies adding extra flags for individual programs
and also allows more than one object file per program.
Signed-off-by: Mans Rullgard <mans@mansr.com>

CC: libav-stable@libav.org

The check is bogus since the nuv frameheader is already skipped
and the (decompressed) RTjpeg header is checked.

This reverts commit f6afacdb.

CC: libav-stable@libav.org

Signed-off-by: Mans Rullgard <mans@mansr.com>

IMCContext was changed from an array to a pointer in 66b84e4a,
but this memset() was not updated.
Signed-off-by: Mans Rullgard <mans@mansr.com>

Signed-off-by: Mans Rullgard <mans@mansr.com>

This removes some needless indirection and duplication.
Signed-off-by: Mans Rullgard <mans@mansr.com>

At this place, the normal way of initializing a struct works
fine, there's no need for a struct literal.
Signed-off-by: Martin Storsjö <martin@martin.st>

This allows simplifying a few expressions.
Signed-off-by: Mans Rullgard <mans@mansr.com>

Some corrupted files would end up with a negative offset,
and segfault.

Fixes bug #177.
Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>

Found with a clang-scan report on http://fate.libav.org/csa/

Based on a patch by Piotr Bandurski.
Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>

If there was a failure inflating, or reinitializing
the zstream, the current frame's buffer would be lost.
Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>

Be consistent with error messages and code formatting.
Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>

Adds some validation for changing parameters after setting the matrix and
fixes a bug in the conversion path setup.

This makes big and little endian systems use the same output
format.
Signed-off-by: Mans Rullgard <mans@mansr.com>

Based on patch by Oana Stratulat <oanaandreeastratulat@gmail.com>.

In the GNU assembler, a relational expression, bizarrely, has the
value -1 if true, whereas in Apple's it is +1.  This patch makes
sure the correct expression is used in both cases.
Signed-off-by: Mans Rullgard <mans@mansr.com>

The clang integrated assembler does not support pre-UAL syntax,
while gcc requires pre-UAL syntax for ARM code.  A patch[1] for
clang to support the old syntax as well has been ignored since
January.

This patch chooses the syntax appropriate for each compiler,
allowing both to build the code.  Notably, this change allows
building for iphone with the latest Apple Xcode update.

[1] http://llvm.org/bugs/show_bug.cgi?id=11855Signed-off-by: Mans Rullgard <mans@mansr.com>

Signed-off-by: Diego Biurrun <diego@biurrun.de>

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.

This reverts commit 36936080. It was
already applied; no idea why it didn't error out while re-applying it.

This fixes Bugzilla #327:
Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com>

For left HFYU prediction, we predict from the buffer buf+1 using 8- or
16-byte reads. This means that aligning the buffer by 16 bytes is in
itself not sufficient, because if the width itself is 16- or 8-byte
aligned, the buffer will not be padded, and thus a read of size 16 at
buf+1 will overflow boundaries at the right edge. Padding the buffer by
1 byte is sufficient to not overflow its boundaries.

Fixes bug 342.

This makes add_hfyu_left_prediction_sse4() handle sources that are not
16-byte aligned in its own function rather than by proxying the call to
add_hfyu_left_prediction_ssse3(). This fixes a crash on Win64, since the
sse4 version clobberes xmm6, but the ssse3 version (which uses MMX regs)
does not restore it, thus leading to XMM clobbering and RSP being off.

Fixes bug 342.