similar to: [LLVMdev] How to build up static call graph for Android native code

Dear Colleagues, I have a fairly vanilla setup of dovecot on FreeBSD, serving IMAP and POP3. Thunderbird/IMAP works fine, and so does mutt/IMAP. However, Android clients (Gmail/IMAP and K-9 Mail) have problems accessing folders other than the INBOX. They either show them empty with no mails (K-9) or just wait forever to view the contents (Gmail app). Do I need to set up some workarounds or

You can try doing this: protocol imap { ? rawlog_dir = %h/rawlogs } then make directory under user's homedir called rawlogs and chmod 0777 it. Then try, you should end up with lots of files that are full of chatter between the client & server, maybe it gives you more indication what goes wrong. Aki On 25.09.2018 05:47, Victor Sudakov wrote: > Dear Colleagues, > > I have a

Why does compiler-rt ship a shared object for ASan on Android instead of a static library? Would statically linking ASan on Android at least be safe for standalone executables? And if I'm wanting to use ASan in C++ code that is invoked from an APK, can I statically link ASan? If not, what is the reason we need to preload Dalvik with the ASan shared object? I assume static linking here

> Static runtime will only intercept calls from the main executable, but > not from any libraries. This may work for simple standalone programs, > but you may run into puzzling failures. What type of failures do you mean? Does the symbol mismatch break assumptions in the ASan runtime? It's easy to imagine, for example, ASan missing use-after-free bugs because the call to free() is

+eugenis@ On Sat, Sep 21, 2013 at 4:58 AM, Greg Fitzgerald <garious at gmail.com> wrote: > Why does compiler-rt ship a shared object for ASan on Android instead > of a static library? Would statically linking ASan on Android at > least be safe for standalone executables? > > And if I'm wanting to use ASan in C++ code that is invoked from an > APK, can I statically

For the same reason we use shared runtime on OSX. We intercept libc calls by declaring a function with the same name in the sanitizer runtime library. Glibc loader puts main executable early in the symbol lookup order, which lets us interpose symbols from shared libraries with symbols from statically linked sanitizer runtime. Android (and AFAIK most other platforms) does not allow that, which is

https://bugzilla.samba.org/show_bug.cgi?id=9860 Summary: Fix Android build Product: rsync Version: 3.1.0 Platform: All OS/Version: Other Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: dpb at corrigendum.ru QAContact: rsync-qa

This is getting a bit off-topic, but since Renato brought up RenderScript, I wonder if the Android libbcc interface wouldn't be a cleaner way to approach this problem. It provides more or less the same functionality as MCJIT and in almost the same way. -Andy From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Renato Golin Sent: Tuesday, November 05,

Is it possible to try your program on a non-Android Linux? It might make debugging a bit less painful. If you haven't updated to the trunk code recently, it's possible that calling finalizeObject more than once would cause a crash. The changes that introduced multiple module support should have fixed that issue. It might be useful to set breakpoints in the memory manager you are using.

On 4 November 2013 23:45, James Lyon <jameslyon0 at gmail.com> wrote: > I'm trying to build LLVM on Android rather than the other way around! > Really just to see if it can be done. I worked out the first problem (my > code was written for the old JIT and I'd missed something in updating to > the MCJIT to make it work on ARM). It still doesn't work, but at this

I suppose I was just doing the "smallest" thing. Disabling the hack entirely also allows it to build and is probably the correct thing to do. I'm not that knowledgeable about glibc vs. Bionic differences so the thing to do would be to test whether those functions work without the "hack" on Android. Unfortunately at the moment I can't get my Android JIT test program

Hi, Is there anybody out there that is experienced with run-time code generation on an android device? Is it even possible to achieve this? I compiled both llvm and clang for x64 android tablet and everything seemed fine until i tried to call exposed generated function through my native code: it gave an error that indicating I dont have rights to execute code in this memory block.(I will add the

The CMake changes look fine to me, landed in r194051! As for the JITMemoryManager.cpp changes, not so sure. Did you try disabling the 'hack' described below instead of patching it? | ||//===----------------------------------------------------------------------===//|| ||// Function stubs that are invoked instead of certain library calls|| ||//|| ||// Force the following functions to be

I've been trying to get LLVM JIT compilation working on Android for the last few days. The patch I needed to get it to build is attached (nothing major - CMake configuration header typo and avoiding open64 which is missing on Android). Sadly even though it builds I can't get generated code to work - it appears at the moment that the generated code doesn't have execute permissions

I asked this question on android-platform at googlegroups.com but never received a response. I suspect most (if not all) people compiling the Android platform are using some version of Ubuntu ... hence the lack of response. I would not normally cross post but am hopeful that another CentOS 5.4 user (not on the android-platform forum) might have successfully built the Android platform. I would

On 30 October 2013 17:08, James Lyon <jameslyon0 at gmail.com> wrote: > Sadly even though it builds I can't get generated code to work - it > appears at the moment that the generated code doesn't have execute > permissions set for some reason (this is 3.3, not svn). Hi, You may have a look at the LLVM Linux builds ( http://llvm.linuxfoundation.org/index.php/Main_Page),

Hey, I am trying to build a haskell cross compiler to android by building the glasgow haskell compiler with target=arm-linux-androideabi. It builds, but the executables the compiler produces segfaults on my android device. This is probably not llvm related, but I want to rule that out. I used the llvm version shipped with ubuntu 12.10 for the build. I was wondering if maybe I have to use llvm

Hi, I believe some Neon code doesn't get invoked properly, because all PRESUME macros were set in my build. Probably not all optimized functions are called directly under iOS. Regards, Victor -----Original Message----- From: Jonathan Lennox Sent: Thursday, August 30, 2018 11:59 AM To: Victor Cherepanov Cc: opus at xiph.org Subject: Re: [opus] NEON detection under iOs On iOS, configure

I'm trying to build LLVM on Android rather than the other way around! Really just to see if it can be done. I worked out the first problem (my code was written for the old JIT and I'd missed something in updating to the MCJIT to make it work on ARM). It still doesn't work, but at this point I have no idea why and it'll be a while before I get to look at it again: the Android

Hi, I see there is an inconsistency in LLVM libc calls. For a modulo (reminder) operation, clang -target arm-none-linux-gnueabi generates "__modsi3". clang -target arm-none-eabi generates "__aeabi_idivmod" clang -target arm-linux-androideabi generates "__modsi3" Android bionic libc doesn't provide a __modsi3, instead it provides