search for: aosps

On Fri, May 19, 2017 at 4:32 PM, Daniel Berlin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > i think you'd have to write some idiom recognizer here. The ones we have > won't do it. > > I guess my other question would be how commonly this happens. If it's common > and matters a lot, awesome. > I wouldn't do it just to fix SPEC :P > > (people who

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/libjpeg-turbo -I external/libpng -I

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

...) 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...

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

On Mon, Nov 25, 2013 at 12:36 PM, Alp Toker <alp at nuanti.com> wrote: > > 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? >

This is only available for apps that target API level 19 and up. On 18 and lower, the futimens() function won't be available via libc.so. You will need to target API 19 (KitKat) in order to actually use it. If I do an "nm -D prebuilts/ndk/9/platforms/android-19/arch-arm/usr/lib/libc.so", I can see futimens() is present. On the others, it is definitely missing. Steve On Mon, Nov

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

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

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

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

Yes, llvm-config. Thanks for the pointer to the build script - that's what I was looking for. -Greg On Thu, Jan 31, 2013 at 5:24 PM, Andrew Hsieh <andrewhsieh at google.com>wrote: > You mean llvm-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

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 =

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,

[add subject] Dear LLVM community, hope all of you had a good start into 2018 and a quiet branching of LLVM 6.0. With the latest LLVM release out of the way and a longer development phase starting, we would like to restart the process of including Polly and isl into core LLVM to bring changes in early on before the next LLVM release. Short summary: * Today Polly is already part of each LLVM

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

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-all is very useful for debugging and learning about LLVM. I would hope that would be implemented for the new PM before removing the old PM. I'd personally consider it a blocker. -Troy > -----Original Message----- > From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of Eric Christopher > via llvm-dev > Sent: Tuesday, July 09, 2019 7:40 PM > To:

I don't exactly remember when I last tried it and I didn't realize there was r342896. I'll check it out. Thanks. On Wed, Jul 10, 2019 at 1:14 PM Philip Pfaffe <philip.pfaffe at gmail.com> wrote: > > Printing was implemented in r342896. > @Hiroshi: Are there specific issues or limitations you encountered with it? > > Cheers, > Philip > > On Wed, Jul 10,