* Update to the current lavf API and fix memory leak when using --seek
* x86inc: Make INIT_CPUFLAGS support an arbitrary number of cpuflags
* x86: Minor pixel_ssim_end4 improvements
* x86: Faster quant_4x4x4
* configure: improve cc_check for clang and ICL to not ignore unknown options
* checkasm: Only call x264_cpu_detect() once
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
* Fix AVX2 detection bug with "limit CPUID" enabled in BIOS
* Fix a few minor bugs found with a static analyzer
* Fix cases in which intra refresh allowed prediction from disallowed pixels
* x86inc: Check for __OUTPUT_FORMAT__ having a value of "x64"
* configure: Support cygwin64
* x86: Faster AVX2 pixel_sad_x3 and pixel_sad_x4
* x86: SSSE3 implementation of pixel_sad_x3 and pixel_sad_x4
* Transparent hugepage support
* AVC-Intra support
* Windows Unicode support
* Fix GPAC support on Windows
* Fix masked access violation in KERNEL32
Onno van der Linden <o.vd.linden@quicknet.nl>
in private mail.
Similar to mplayer and ffmpeg fixes.
XXX: Probably NetBSD-5.99.* could use the CFLAGS too instead
of the --disable-asm, but neither me nor Onno can test.
Someone who groks linker issues should try to make the asm code
position independent. Until then I suspect we will end up using
--disable-asm everywhere.
The snapshot date is chosen for some reason:
-vlc-1.0.6 (which I'll commit soon) needs an API change which
was introduced on 20090813
-pkgsrc's ffmpeg can't deal with an API change which was done 20090921
(and is not easily updated)
was a period of relative quietness in x264 development, and I've been
testing this snapshot for some weeks (on i386).
There are too many changes to list here.
This changes the buildlink3.mk files to use an include guard for the
recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS,
BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new
variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of
enter/exit marker, which can be used to reconstruct the tree and
to determine first level includes. Avoiding := for large variables
(BUILDLINK_ORDER) speeds up parse time as += has linear complexity.
The include guard reduces system time by avoiding reading files over and
over again. For complex packages this reduces both %user and %sys time to
half of the former time.
please see the repository for more information. I'm doing this update
our version is over a year old and some software is starting to require
a newer version.