search for: aosp

...probably use any of the faster bzip2 > impls :P) > Danny, do you know of forks of bzip2 that are more efficient than bzip.org? I haven't seen one. Sirish is going to send a patch to Julian Seward and try to get the change in a new release of bzip2, and from there we may need to ask the AOSP folks to update bzip2. AOSP has the last released bzip2 from Sept 2010. For SPEC benchmarketing, doing the right thing wouldn't help. Maybe we should put this idiom and others under a -fspec flag ;-) Sebastian

Hi Pengxuan, I just saw that the newly added AOSP buildbot allready builds LLVM very nicely. However, it is still red due to the following assertion: FAILED: out/target/product/angler/obj_arm/STATIC_LIBRARIES/libskia_static_intermediates/src/core/SkOpts.o /bin/bash -c "PWD=/proc/self/cwd ulimit -t 180; llvm.inst/bin/clang++ -I external/li...

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 string 'LOCAL_ADDRESS_SANITIZE...

...) who register as resellers with the CRTC. - offer 0-ECRS to VoIPSPs who are registered as resellers with the CRTC at the same rate it is offered to other eligible parties - Wireless Service Providers (WSPs), Canadian Pay Telephone Service Providers (CPTSPs), Alternate Operator Service Providers (AOSPs), Competitive Local Exchange Carriers (CLECs) and Interexchange Carriers (IXCs). - provide the Call Routing Lists and Traffic Operator Position Records (TOPR) lists that are currently provided to traditional 0-ECRS customers. 2.0 SERVICE DESCRIPTION 2. The revision to the 0-ECRS Service is to...

...We work extensively > with LLVM and this allowed us to remove our ugly workaround > for not having this functionality. > > > Hi Steve, > > Is your work on a branch somewhere? > > > It is all available as part of the Android Open Source Project (AOSP). > I should mention that we do not use the JIT path, but LLVM does > require futimens() to build properly for Android (hence us fixing this > missing part of bionic). If you want to look at local patches that we > have for LLVM/Clang, those are available in "external/llvm&quot...

...le in Android KitKat. We work extensively with LLVM >> and this allowed us to remove our ugly workaround for not having this >> functionality. >> > > Hi Steve, > > Is your work on a branch somewhere? > It is all available as part of the Android Open Source Project (AOSP). I should mention that we do not use the JIT path, but LLVM does require futimens() to build properly for Android (hence us fixing this missing part of bionic). If you want to look at local patches that we have for LLVM/Clang, those are available in "external/llvm" and "external/cla...

...ith LLVM >>> and this allowed us to remove our ugly workaround for not having this >>> functionality. >>> >> >> Hi Steve, >> >> Is your work on a branch somewhere? >> > > It is all available as part of the Android Open Source Project (AOSP). I > should mention that we do not use the JIT path, but LLVM does require > futimens() to build properly for Android (hence us fixing this missing part > of bionic). If you want to look at local patches that we have for > LLVM/Clang, those are available in "external/llvm" an...

On 25/11/2013 18:27, Stephen Hines wrote: > futimens() is available in Android KitKat. We work extensively with > LLVM and this allowed us to remove our ugly workaround for not having > this functionality. Hi Steve, Is your work on a branch somewhere? James is putting a lot of time into this, and the LLVM community has been making best efforts to help review his patches which can be

On Mon, 15 Jan 2018 22:44:45 +0100, Tobias Grosser via llvm-dev wrote: <snip> > * How stable/fast/… is Polly today > * We build all of AOSP with rather restrictive compile-time limits > * Bootstrapping time of clang is regressed by 6% (at most) > * Removal of scalar dependences is today very generic and must be > sped up in the future > * Polly still shows up at the top of the middle-end, but larger >...

...it work and add a buildbot or something like that. I think that, on the Android front, it would be really nice to have Clang/LLVM working well, especially on the JIT front, so that we could have a more generic JIT experience, rather than just Renderscript. We should think about that when creating AOSP images in the future. cheers, --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131105/f4e48837/attachment.html>

FWIW, the flags like -print-after, -printer-after-all don't work well with the new pass manager last time I checked. On Mon, Jul 8, 2019 at 12:20 PM Stephen Hines via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > The Android platform build (AOSP) has also switched to the new pass manager recently. We do have a few bugs that we are chasing (hence opt-outs), but it is working quite well otherwise. > > Our current list of issues: > 1) Libsqlite still has a mysterious failure that we haven't been able to reduce well. > 2) https...

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

...lvm-config? It was deleted after the build. You can modify our > build script build-llvm.sh to get it back. > Clang/llvm-3.2 will be available in the next NDK release. There is no > plan to align release between NDK and the one in Chromium. > You can rebuild it from source. Assuming $AOSP points to your android > tree. > > export NDK=$AOSP/ndk > cd $NDK > ./build/tools/download-toolchain-sources.sh /tmp/ndk-$USER/src > ./build/tools/build-llvm.sh /tmp/ndk-$USER/src $NDK > --package-dir=/tmp/ndk-$USER/prebuilt llvm-3.2 --try-64 > > If you have lots of machi...

Hi all, I'm trying to extend the Dalvik VM to load some LLVM assembly from the SD card, JIT it, and execute it. I'm using AOSP 4.0.4, a Galaxy Nexus, and the version of LLVM that comes in the external project of AOSP (LLVM 2.8, I believe?) I have the following LLVM assembly: target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:32:64-v128:32:128-a0:0:32-n32-S32" t...

...it work and add a buildbot or something like that. I think that, on the Android front, it would be really nice to have Clang/LLVM working well, especially on the JIT front, so that we could have a more generic JIT experience, rather than just Renderscript. We should think about that when creating AOSP images in the future. cheers, --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131105/12a7bc15/attachment.html>

...mplicit choice of LLVMs loop optimization future. This is not the case. While Polly is today the only end-to-end high-level loop optimization, other approaches can and should explored (e.g., can there be synergies with the region vectorizer?) * How stable/fast/… is Polly today * We build all of AOSP with rather restrictive compile-time limits * Bootstrapping time of clang is regressed by 6% (at most) * Removal of scalar dependences is today very generic and must be sped up in the future * Polly still shows up at the top of the middle-end, but larger compile time regressions are often...

...Was there any useful output in adb logcat when your program crashed? On Fri, Jun 21, 2013 at 4:47 AM, Greg Fitzgerald <garious at gmail.com> wrote: > 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 string ...

On Thu, 27 Jun 2019 at 17:46, Philip Reames via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > For our downstream usage, we've switched entirely to the new pass manager. We made the switch a couple of months ago. All of our testing is being done with the NPM, and we're about to start deleting (downstream) code which was only needed by the legacy pass manager. > > I

...-print-after, -printer-after-all don't work well > > with the new pass manager last time I checked. > > > > On Mon, Jul 8, 2019 at 12:20 PM Stephen Hines via llvm-dev > > <llvm-dev at lists.llvm.org> wrote: > > > > > > The Android platform build (AOSP) has also switched to the new pass > manager recently. We do have a few bugs that we are chasing (hence opt-outs), > but it is working quite well otherwise. > > > > > > Our current list of issues: > > > 1) Libsqlite still has a mysterious failure that we haven't...

...>> > > with the new pass manager last time I checked. >> > > >> > > On Mon, Jul 8, 2019 at 12:20 PM Stephen Hines via llvm-dev >> > > <llvm-dev at lists.llvm.org> wrote: >> > > > >> > > > The Android platform build (AOSP) has also switched to the new pass >> > manager recently. We do have a few bugs that we are chasing (hence opt-outs), >> > but it is working quite well otherwise. >> > > > >> > > > Our current list of issues: >> > > > 1) Libsqlite still...