similar to: Compiling opus for iOS Platform

Hello, I'm having some trouble getting Opus to work in an ARM64 iOS application and I'm wondering if anyone here has any guidance. Maybe I am missing something simple. Specifically, the problem is that Opus running on ARM64 outputs different data than other architectures -- ARMv7, ARMv7s, i386, and x86_64. On all other platforms except ARM64, encoding a 1280 byte slice of audio data

Hi, I was able to compile the sources under Xcode and encode / decode audio on the iPhone. However i could not compile it using the configure/make preocedure. I've noticed that the audio comes out with added noise. Is there a way to compile the library with the configure/make for iOS so i can rule out bad configurations? Regards Filipe

I?m trying to build Opus (git master) for iOS, and it doesn?t build unless I disable the ARM assembly. It looks like the problem is that Apple?s assembler doesn?t support all the assembler 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

Hi, I'm having some troubles getting LLVM compiled for the ARM iOS platform: what I'm trying to achieve is a on-device compiler for C, C++ and possibly ObjC. I tried multiple times to compile it, both using Makefiles and the Xcode project generated from CMake. In the first case the compilation failed with a lipo error that said "no input file specified" related to

Hi Dave, Yep. This is JITLink specific, so we could only have observed it on MachO x86-64 or arm64 until recently. It takes a little bit of poking to get IR to produce a zero-lengh section on MachO, but not much. Jared Wyles recently contributed an initial JITLink ELF implementation, so the fix seems timely -- we might have been about to see more of it. -- Lang. On Fri, Jun 19, 2020 at 4:02 PM

In the failing command (iossim-log) the syslibroot flag is being specified to the linker and the link command still fails, so your patch shouldn’t fix the problem. You can see that listed in iossim-link.txt. The other error is (if anything) more disturbing. You’re generating a malformed libLLVMSupport. Not sure how that’s happening. It looks to me like there is something wrong with your host

I just noticed that the clang in Xcode 3.2.2 was bumped to 1.0.2. How does the Apple clang versioning numbering relate to that used for the llvm.org version of clang? In particular, what version of clang will llvm 2.7 ship with? I assume that Xcode 3.2.2 must be using clang 2.6, no? Jack

On Thu, 8 Jan 2015, Jonathan Lennox wrote: > Every armv7 (and armv8) iOS device has supported Neon, and Xcode support for > armv6 was dropped with Xcode 4.5. > > Even if you?re compiling with an old Xcode version to support really old iOS > devices, Apple?s armv6/armv7 selection was a compile-time switch (supported > using fat binaries). ?I think the arch can be detected based

Hello, I am trying to run this basic C++ hello-world code in my iOS app that has LLVM libraries linked in (the app runs on the actual device - iPad Pro, iOS 13.4.1). #include <iostream> int main (int argh, char *argv[]) { std::cout << "Hello World!" << std::endl; return 0; } So below is the break down of the steps that I do: First I compile this code to an

Hi, Bernie, Thanks for your reply! However, I still have problem by following edk2's code, my test code is attached, what I want to do is build it as a dynamic lib. But I get error from ld: ld: illegal text-relocation to _data_table in table.o from foo in use_table.o for architecture armv7 Do you have any suggestion to solve this? Thanks! //==begin table.c== int data_table[] = {0xff, 0xff};

Can you please provide the full error and information about the failure you saw without your patch? Since you couldn’t build before the patch, and you can’t build with the patch. I suspect there is an underlying issue which isn’t being addressed. -Chris > On Sep 22, 2015, at 2:02 PM, Alex Wang <aw1621107 at gmail.com> wrote: > > Whoops. Forgot to include what happened before the

Sorry if this isn't the right place; but I'm facing an XCode 4 (LLVM 2.0 to Apple, I heard it's LLVM 2.9 under the hood) issue that may involve LLVM, and maybe some people on this list could help me short-circuit the source. I have a code pattern that, when used in XCode 4 in Objective C++ files, causes the whole IDE to go crash. It is a stripped sample to highlight the issue. In

Following a blend of instructions on 3 web pages, I have succeeded in getting LLVM 3.2 (with clang, extras, and compiler-rt) building - but not testing - on Xcode. I used CMake 2.8.10 GUI to create the Xcode project file. Below are my notes. First, I believe CMake ends up setting things up so that Xcode has 1 warning after scanning the project having to do with hires images or some such… it takes

Those look like the linker is being passed the same .o file built twice, ex: ../Objects-normal/x86_64/asan_globals_test.o ../lib/asan/tests/asan_globals_test.cc.asan.o So, the symbols are colliding. Something is set up wrong in the xcode project. -Nick On Dec 19, 2012, at 9:48 AM, Relph, Richard wrote: > Following a blend of instructions on 3 web pages, I have succeeded in getting LLVM

Different, but still failing (this time with Xcode 4.4…) /Users/rrelph/llvm/tot/xcode/bin/Debug/clang sanitizer_allocator_test.cc.i386.o sanitizer_common_test.cc.i386.o sanitizer_flags_test.cc.i386.o sanitizer_libc_test.cc.i386.o sanitizer_list_test.cc.i386.o sanitizer_printf_test.cc.i386.o sanitizer_stackdepot_test.cc.i386.o sanitizer_test_main.cc.i386.o gtest-all.cc.i386.o

Hi Richard! On Thu, Dec 20, 2012 at 12:48 AM, Nick Kledzik <kledzik at apple.com> wrote: > Those look like the linker is being passed the same .o file built twice, > ex: > ../Objects-normal/x86_64/asan_globals_test.o > ../lib/asan/tests/asan_globals_test.cc.asan.o > > So, the symbols are colliding. Something is set up wrong in the xcode > project. > > -Nick

+llvm-commits (correct list) On Tue, Sep 22, 2015 at 12:32 PM, Alexey Samsonov <vonosmas at gmail.com> wrote: > Could you describe the build failures you see after applying this patch? > I'll let Chris judge if adding -Wl,-syslibroot makes sense for iossim, or > that problem should be solved differently. > > On Tue, Sep 22, 2015 at 9:37 AM, Alex Wang via llvm-dev <

The behavior here is consistent with setting SDKROOT in the environment to an OS X SDK. -Chris > On Sep 22, 2015, at 2:28 PM, Alex Wang <aw1621107 at gmail.com> wrote: > > Logs + commands added to the earlier gist. > > Only thing different from a plain trunk build is adding -Wl,-v and -Wl,-t to the > iossim link flags. > >> On Sep 22, 2015, at 5:17 PM, Chris

Dear LLVM community I need some help please. I want to use LLVM's clang and lld within a MacOSX sandboxed app. This is because sandboxing does not allow calls to /usr/bin/clang. The clang binary works fine to compile a file, but ld64.lld comes up with the error "cannot find framework". However similar arguments using /usr/bin/ld instead of ld64.lld works fine. Here are the

Hi, I am currently studying the possibility to make the transition from gcc 4.2 to llvm-gcc 4.2 for the projects I am working on. These projects are huge projects, most of the source code is written in C++ but we have objc, c and assembly code. We are targeting MacOSX 10.5 and MacOSX 10.6. Our build system is currently running on MacOSX 10.5 and uses Xcode 3.1.4 with gcc 4.2. It is used to