After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 727696 - x264 fails to build on iOS
x264 fails to build on iOS
Status: RESOLVED DUPLICATE of bug 727079
Product: GStreamer
Classification: Platform
Component: packages
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-04-06 07:15 UTC by Sebastian Dröge (slomo)
Modified: 2014-04-07 07:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastian Dröge (slomo) 2014-04-06 07:15:11 UTC 
git master version of cerbero:

clang -Wshadow -O3 -ffast-math -m32  -arch i386  -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.0.sdk -miphoneos-version-min=5.1 -D__IPHONE_OS_VERSION_MIN_REQUIRED=510000 -Wall -I. -I. -falign-loops=16 -march=i686 -mfpmath=sse -msse -std=gnu99 -mpreferred-stack-boundary=5 -fPIC -fomit-frame-pointer -fno-tree-vectorize  -arch i386  -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.0.sdk  -c -o common/x86/mc-c.o common/x86/mc-c.c
clang: warning: argument unused during compilation: '-falign-loops=16'
clang: warning: argument unused during compilation: '-mfpmath=sse'
clang: warning: argument unused during compilation: '-mpreferred-stack-boundary=5'
In file included from encoder/me.c:28:
In file included from ./common/common.h:1014:
./common/x86/util.h:131:9: error: ran out of registers during register allocation
        "movq       (%2), %%mm5 \n"
        ^
./common/x86/util.h:194:9: error: ran out of registers during register allocation
        "movq       (%2), %%mm5 \n"
        ^
Comment 1 Edward Hervey 2014-04-07 06:56:56 UTC 
Seems to be identical to the failure in bug #727079
Comment 2 Sebastian Dröge (slomo) 2014-04-07 07:10:20 UTC 
Looks a bit different though, for you it doesn't print any of the code as part f the error messages. Might be related though.
Comment 3 Sebastian Dröge (slomo) 2014-04-07 07:15:30 UTC 
Looking at the mailing list thread you linked, this is the exact same issue. And all the solutions mentioned there are not really solutions

*** This bug has been marked as a duplicate of bug 727079 ***