similar to: [LLVMdev] Converting C++ to Java

From: http://address-sanitizer.googlecode.com/svn-history/r1624/wiki/Android.wiki > AddressSanitizer is fully supported in AOSP starting with JellyBean release. To run > applications built with ASan you'll need an -eng build of Android. > > To build any part of Android system with ASan, add > LOCAL_ADDRESS_SANITIZER:=true to the appropriate Android.mk. I don't see that

You are citing the "Android platform workflow" section, which is about sanitizing components of the Android system itself. For NDK apps, see "Android NDK workflow" in the same document. You need -eng build because preloading libraries into dalvik vm is not allowed in user builds. JellyBean includes several bugfixes in the dynamic loader that asan needs. Was there any useful

Evgeniy, thanks for your help. > You need -eng build because preloading libraries into dalvik vm is not > allowed in user builds. JellyBean includes several bugfixes in the > dynamic loader that asan needs. Do you have the sha1 hashes for any of those patches? I might be able to track down a build that includes them. > Was there any useful output in adb logcat when your program

Hi all, does anyone here know if Google has considered trading out the Dalvik VM for LLVM? What specifically I have in mind is that apps could be compiled to LLVM IR and distributed (after optimization) in that form, and then compiled to machine code on the Android machine itself. This would leave only ISA optimizations to the Android machine. It would seem, from my limited perspective, that

Hello, I'm generating C code (and the resulting obj files) using llvm 3.4 for both unix and windows. And I use the dreaded weak references, that, for windows, are not too widely supported. When I link my application on linux, I have no issue. But when I'm doing the same on windows using mingw I got a duplicate symbol error :

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

Thanks for your clear answer. Do you know what modifier should I use to declare such weak symbols in my llvm intermediate code? So that it can be compiled to the .o file with the weak attribute ? Le 10 févr. 2014 19:44, "Reid Kleckner" <rnk at google.com> a écrit : > COFF doesn't support the same kind of concept of 'weak' that ELF does. > This is the issue that

Thanks for the response Nick, Do you think there is value in adding the check for FixupOffset > 0xffffff into the ARM backend? The lack of that seems like it could silently record incorrect offsets from the assignment later in RecordARMScatteredRelocation(): MRE.r_word0 = ((FixupOffset << 0) | (Type << 24) | (MovtBit << 28) |

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

Hats off to the Android NDK team! http://developer.android.com/tools/sdk/ndk/index.html Important changes: * Added the Clang 3.1 compiler to the NDK. The GNU Compiler Collection (GCC) 4.6 is still the default, so you must explicitly enable the Clang compiler option as follows: * For ndk-build, export NDK_TOOLCHAIN_VERSION=clang3.1 or add this environment variable setting

So instead of using linkagetypes.weak I should use externalweaklinkage ? Le 11 févr. 2014 18:29, "Reid Kleckner" <rnk at google.com> a écrit : > You'd have to use extern_weak linkage. Clang compiles the foo declaration > to: > $ clang -cc1 -emit-llvm -o - t.c | grep declare.*@foo > declare extern_weak i32 @foo(...) #1 > > > > On Tue, Feb 11, 2014 at

+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

> The main advantage of the clang-built Android ARM(32-bit) hammerhead kernel for my Nexus 5 has been the better battery usage when compared to that of gcc-built kernel, with the same kernel config and hardware(my Nexus 5 Android Smartphone). Details of the same can be found below. To be fair, the GCC version which comes with the android ndk has not been updated for four years, while the clang

Hey Guys, I'm working on a project in Android related to System-level Audio DSP Effects for Tuning Android Audio. I want to leverage Faust ( https://faust.grame.fr/) to allow users to program their own filters. Faust provides a libfaust implementation which includes a JIT Compiler which leverages LLVM and seems to be the best path for me to use. Unfortunately I'm having problems

Hi, We are trying to use clang as a drop-in replacement for the gcc come with Android NDK. I found that MC/ELF doesn't not handle Thumb functions properly, e.g., bit 0 of the function name in the .symtab is not set to 1, and some thumb instructions are not generated correctly, e.g., the addresses for tBL/tBLX are not calculated right. With that attached patch, we can compile and run some

cc +andrewhsieh +loganchien On Tue, Nov 13, 2012 at 11:21 PM, Joe Abbey <jabbey at arxan.com> wrote: > Hats off to the Android NDK team! > > Thanks for including me here, but I'd like to clarify that this is all from the really hard work of Andrew Hsieh and Logan Chien, and a few other Android engineers. (I'm actually not working on Android anymore, Andrew and Logan have

Hi, Does LLVM have java frontend which can change Java bytecode to LLVM IR? Thanks a lot! Best, Linhai -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160112/1d9c0c7b/attachment.html>

I'm fairly sure the problem is that we still support building with gcc 4.8.x, and that version of gcc did not have std::to_string. It is not just an NDK issue. -Hal On 05/17/2017 06:05 AM, Pavel Labath via llvm-dev wrote: > Hi Diana, > > I am responsible for that bot, and probably a great number of those fixups. > > The root of the problem is that android NDK comes with a

> 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

Hmmm.... following up on your point I've noticed something strange. futimens is missing from the NDK (r9b; it's not in any headers and the libc.so files are the same all the way back to android-9), which is why I thought it's missing from Android generally. The NDK is by far the easiest way to cross-compile since it provides a standalone cross-compilation toolchain. It is however