Hi, > I'm getting a build error installing the +asm+universal x264 variant > (x264@20130823+asm+universal) on OS X 10.9.1: > > :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.
>From what I remember these occur because clang's heuristic doesn't necessarily >find a possible solution (remember register allocation is a complex problem); >GCC's algorithms try harder and eventually succeed. Most of these problems >were considered to be caused by upstream and the solution was to remove some >constraints for the inline assembler. > 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? Yes, this is a bug you should report. Maybe updating the port to a more recent version would fix the problem. > (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? ;) ) Due to the whole C++ libc++ situation, this is not going to happen. Clang will be our main compiler suite, and switching now and getting the bugs that still exist fixed is the correct thing to do. Clang is not going away, but GCC on OS X already has. -- Clemens Lang _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
