At 12:13 PM -0800 3/1/14, David Evans wrote:
On 3/1/14 6:48 AM, "René J.V. Bertin" wrote:
I'm getting a build error installing the
+asm+universal x264 variant
(x264@20130823+asm+universal) on OS X 10.9.1:
:info:build /usr/bin/clang -Wshadow -O3
-ffast-math -m32 -I. -fno-common
-read_only_relocs suppress -arch i386 -Wall -I.
-I. -falign-loops=16 -march=i686 -mfpmath=sse
-msse -std=gnu99 -mpreferred-stack-boundary=5
-fPIC -fomit-frame-pointer -fno-tree-vectorize
-c -o encoder/me.o encoder/me.c
:info:build clang: warning: argument unused
during compilation: '-read_only_relocs suppress'
:info:build clang: warning: argument unused
during compilation: '-falign-loops=16'
:info:build clang: warning: argument unused
during compilation: '-mfpmath=sse'
:info:build clang: warning: argument unused
during compilation:
'-mpreferred-stack-boundary=5'
:info:build In file included from encoder/me.c:28:
:info:build In file included from ./common/common.h:987:
:info:build ./common/x86/util.h:131:9: error:
ran out of registers during register allocation
:info:build "movq (%2), %%mm5 \n"
:info:build ^
:info:build ./common/x86/util.h:194:9: error:
ran out of registers during register allocation
:info:build "movq (%2), %%mm5 \n"
:info:build ^
:info:build 2 errors generated.
with /usr/bin/clang being
Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
Target: x86_64-apple-darwin13.0.0
Thread model: posix
Building with configure.compiler=macports-gcc-4.7 succeeds fine.
Is this a bug I should report? (Or should I
make an "official" suggestion to use gcc
everywhere where Apple-specific options aren't
required as long as clang isn't completely
ready to be the main compiler on linux? ;) )
Although this thread has turned into more of a clang++ discussion, I'll
just mention to that I am currently upgrading x264 to a more recent
version as part of upgrading ffmpeg to version 2.1.4 and will look into
this issue as part of that up upgrade.
While looking at some other stuff, I noticed that
libvpx to 1.3.0 (we currently have 1.2.0)
apparently including the VP9 codec.
http://blog.webmproject.org/2013/07/vp9-lands-in-chrome-dev-channel.html
Would you consider looking at upgrading libvpx, as well?
Craig
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
