search for: iphoneos

Hi, I’ve stumbled across something curious with the Relase_40 I have built here: I tried to build for aarch64-apple-iphoneos, but ended up getting ELF objects $ clang -target aarch64-apple-iphoneos -c tmp.ll -o tmp.o warning: overriding the module target triple with aarch64-apple-iphoneos [-Woverride-module] 1 warning generated. bin $ file tmp.o tmp.o: ELF 64-bit LSB relocatable, ARM aarch64, version 1 (SYSV), not strip...

...raries to my application, and it was successfully compiled and linked, but once the application start it immediately crash (even if I am not using any of the CELT functions) this is how the libraries were configured ... #iPad - libOgg ./configure --host=arm-apple-darwin10 CC=/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/arm-apple-darwin10-gcc-4.2.1 CFLAGS="-isysroot /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS4.2.sdk -march=armv7 -mcpu=cortex-a8" #libCelt - Mac ./configure --host=arm-apple-darwin10 CC=/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/ar...

Hi, When compiling mumble-iphone from https://github.com/mumble-voip/mumble-iphoneos <https://github.com/mumble-voip/mumble-iphoneos> I had a parser error on the file CodeOutputStream.m (form https://github.com/booyah/protobuf-objc/tree/696b7b61cdd4e8d77c55ace98b3119194fa04b7f <https://github.com/booyah/protobuf-objc/tree/696b7b61cdd4e8d77c55ace98b3119194fa04b7f>). I k...

...1] ("<mypath>/testprogram_lucidDreams/iOS_APP/LucidDreams/DreamListViewControllerModel.swift") DW_AT_call_line [DW_FORM_data1] (61) while processing <mypath>/testprogram_lucidDreams/iOS_APP/DerivedData/iOS_APP/Build/Intermediates.noindex/iOS_APP.build/Debug-iphoneos/iOS_APP.build/Objects-normal/arm64/iOS_APP.bc.o: All the errors reference DreamListViewControllerModel.swift and have todo with inlining, but if I remove enough of the input bitcode objects from the llvm-link the error goes away even though DreamListViewControllerModel is still included. Here are...

...; context = llvm::getGlobalContext(); llvm::Module *module = new llvm::Module("top", context); llvm::IRBuilder<> builder(context); llvm::Value *helloWorld = builder.CreateGlobalStringPtr("hello world!\n"); } And here's the error: g++ e.cpp /Developer/Platforms/iPhoneOS.platform/Developer/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin10/4.2.1/libllvmgcc.dylib Undefined symbols for architecture x86_64: "llvm::ConstantExpr::getGetElementPtr(llvm::Constant*, llvm::ArrayRef<llvm::Value*>, bool)", referenced from: llvm::ConstantExpr::getInBounds...

Probably your g++ compiles x86_64 binary by default, but i686 dylib is supplied? Try: g++ -m32 e.cpp /Developer/Platforms/iPhoneOS.platform/Developer/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin10/4.2.1/libllvmgcc.dylib - D. 2012/1/22 Arpan Sen <arpansen at gmail.com>: > Hi, > > I am trying to use some LLVM API in my C++ code, and I end up getting linker > errors. I am working on Apple MacOSX Lion. Using...

...r directives that the GNU assembler does. I suspect this is a combination of the fact that Apple platforms are Mach-O rather than Elf, and just the fact that Apple?s assembler is extremely divergent from the mainline GNU one. Specifically, if I configure with: ../configure -C CC="xcrun --sdk iphoneos clang -arch armv7" --build=x86_64-apple-darwin13.1.0 --host=arm-apple-darwin11 --enable-fixed-point I get: $ make V=1 /Applications/Xcode.app/Contents/Developer/usr/bin/make all-recursive depbase=`echo celt/arm/celt_pitch_xcorr_arm-gnu.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ /...

...please help, thanks. ld: bad codegen, pointer diff in ___cxx_global_var_init79 to global weak symbol __ZN5boost16exception_detail23exception_ptr_bad_allocILi42EE1eE for architecture armv7 clang: error: linker command failed with exit code 1 (use -v to see invocation) Command /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/clang++ failed with exit code 1 ENV: yuma:MyApp yujianhuayu$ clang -v Apple clang version 2.0 (tags/Apple/clang-138) (based on LLVM 2.9svn) Target: x86_64-apple-darwin10 Thread model: posix BTW: Seems link well for simulator but bad for device. -------------- next par...

Hi, There is still tinc-1.1pre7-1-iphoneos-arm.deb, but it can not connect 1.1pre9 server. Error log shows Peer tries to roll back protocol version to 17.0. Is it possible compile 1.1pre9 for iOS? Thank you. -- @hshh -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/...

...("<mypath>/testprogram_lucidDreams/iOS_APP/LucidDreams/DreamListViewControllerModel.swift")                     DW_AT_call_line [DW_FORM_data1]    (61) while processing <mypath>/testprogram_lucidDreams/iOS_APP/DerivedData/iOS_APP/Build/Intermediates.noindex/iOS_APP.build/Debug-iphoneos/iOS_APP.build/Objects-normal/arm64/iOS_APP.bc.o: All the errors reference DreamListViewControllerModel.swift and have todo with inlining, but if I remove enough of the input bitcode objects from the llvm-link the error goes away even though DreamListViewControllerModel is still included. Here are...

...edefinition of 'px' does not match original. > > 3 .end > clang also doesn't recognize .end directive > > all my code is compiled by: clang -arch armv7 -v -integrated-as -g > -mcpu=cortex-a9 -mfpu=neon -isysroot > /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS6.1.sdk/ > > my clang version is: Apple LLVM version 4.2 (clang-425.0.24) (based on > LLVM 3.2svn) > > BTW, could any tell me which files implement integrated-as in clang source > code, I think it may also help me by looking the source code(I've...

...x px .req r1 clang give error: redefinition of 'px' does not match original. 3 .end clang also doesn't recognize .end directive all my code is compiled by: clang -arch armv7 -v -integrated-as -g -mcpu=cortex-a9 -mfpu=neon -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS6.1.sdk/ my clang version is: Apple LLVM version 4.2 (clang-425.0.24) (based on LLVM 3.2svn) BTW, could any tell me which files implement integrated-as in clang source code, I think it may also help me by looking the source code(I've tried 'grep', but w...

...tion.h> #import <UIKit/UIKit.h> int main(void) {         NSString *str = [NSString stringWithCString:"TEST"];         NSLog(@"test object %@", str);         return 0; } Compilation in xcode's clang xcrun -sdk iphoneos clang -arch armv7s -mios-version-min=6.1 -c test_foundation.m -o test_foundation_apple.o gives following result: 1. object file has only 3156 bytes size 2. and in disassembler only main function 3. the final executable will be 49992 bytes size in this case But compilation in llvm's...

...e-bindings --{build,host,target}=i686-apple-darwin --enable-targets=x86,x86_64,cbe --enable-optimized $ make $ make install It will eventually error out with: /Users/erickt/Projects/llvm/gcc-i386/llvm-build-Release/Release+Asserts/bin/clang -no-integrated-as -ccc-install-dir /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/ -arch armv6 -fvisibility=hidden -DVISIBILITY_HIDDEN -mkernel -DKERNEL_USE -Wall -Werror -O3 -fomit-frame-pointer -miphoneos-version-min=1.0 -isysroot /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS4.3.sdk -mthumb -c -o /Users/erickt/Projects/llvm/gcc-i386/...

Hi, Jim, Why "asm" name is a horrible hack? Do you have any suggestion for cross-platform support of my ARM assembly code? Thanks! ashi On Feb 21, 2013, at 2:00 AM, Jim Grosbach <grosbach at apple.com> wrote: > You were correct the first time. That post is talking about a Windows target. Ashi is working on iOS. Underscores are normal and expected. Using an "asm" name

...does not match original. >> >> 3 .end >> clang also doesn't recognize .end directive >> >> all my code is compiled by: clang -arch armv7 -v -integrated-as -g >> -mcpu=cortex-a9 -mfpu=neon -isysroot >> /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS6.1.sdk/ >> >> my clang version is: Apple LLVM version 4.2 (clang-425.0.24) (based on >> LLVM 3.2svn) >> >> BTW, could any tell me which files implement integrated-as in clang >> source code, I think it may also help me by looking...

...ct format properly belongs to the environment concept or whether it should be a new triple component. Looking at the uses in the LLVM code base, it seems that the environment element has been used specifically to enable generation of MachO objects on non-Darwin OSes. I see that clang recognizes “iphoneos” as a value (though it’s not in the Triple::EnvironmentType enum), and it’s not clear to me what it uses it for. Beyond that, the environment seems to be used to influence ABI selection, which would seem to have some degree of overlap with object format selection while being essentially different....

...ct format properly belongs to the environment concept or whether it should be a new triple component. Looking at the uses in the LLVM code base, it seems that the environment element has been used specifically to enable generation of MachO objects on non-Darwin OSes. I see that clang recognizes “iphoneos” as a value (though it’s not in the Triple::EnvironmentType enum), and it’s not clear to me what it uses it for. Beyond that, the environment seems to be used to influence ABI selection, which would seem to have some degree of overlap with object format selection while being essentially different....

...x px .req r1 clang give error: redefinition of 'px' does not match original. 3 .end clang also doesn't recognize .end directive all my code is compiled by: clang -arch armv7 -v -integrated-as -g -mcpu=cortex-a9 -mfpu=neon -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS6.1.sdk/ my clang version is: Apple LLVM version 4.2 (clang-425.0.24) (based on LLVM 3.2svn) BTW, could any tell me which files implement integrated-as in clang source code, I think it may also help me by looking the source code(I've tried 'grep', but w...

...elongs to the environment concept or > whether it should be a new triple component. Looking at the uses in the > LLVM code base, it seems that the environment element has been used > specifically to enable generation of MachO objects on non-Darwin OSes. I > see that clang recognizes “iphoneos” as a value (though it’s not in the > Triple::EnvironmentType enum), and it’s not clear to me what it uses it > for. Beyond that, the environment seems to be used to influence ABI > selection, which would seem to have some degree of overlap with object > format selection while being es...