search for: renderscript

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

...or :) > > Hi Chris, > > Ok, I think I (now) get your drift. Let's restart the conversation, then. ;) > > If I got it right this time, from your point of view, Dan's arguments > are not accurate because IR never intended to be anything else anyway. > PNaCl, OpenCL, RenderScript, Java-like VMs were aggregated over time > and tried to use IR for what it was not designed to be. I completely > agree with you in that one. Hi Renato, I think you're overreacting here. There is nothing about OpenCL, RenderScript, or VMKit that requires LLVM IR be used like a Platform...

...cl" and "pnacl" folks favor :) Hi Chris, Ok, I think I (now) get your drift. Let's restart the conversation, then. ;) If I got it right this time, from your point of view, Dan's arguments are not accurate because IR never intended to be anything else anyway. PNaCl, OpenCL, RenderScript, Java-like VMs were aggregated over time and tried to use IR for what it was not designed to be. I completely agree with you in that one. If I'm not mistaken, JIT was never intended to be portable, but to test IR during a time back-ends were not stable enough. IR was never intended to cover AB...

...gt; > Thanks > Hongbin > > > > > On Tue, Aug 2, 2016 at 3:25 PM, Jakub Kuderski < > kubakuderski+llvm at gmail.com> wrote: > >> I'm not sure if it was intended, but I think that you responded only to >> me (not to the list). >> >> Anyway, RenderScript currently uses llvm 3.2 IR as binary >> representation/exchangeable format, but the llvm version is higher >> internally. Essentially, there it reads old bitcode and operates on the >> newer one in memory. When it's done, it's also able to output bitcode in >> the ol...

...applications that we build using the translated bitcode. If the > older device (which only has LLVM 3.2) passes those tests, we consider it a > success. I suppose that we could take a 3.2-era BitcodeReader and wash > bitcode back and forth through it, but I don't work directly on > RenderScript these days. > > One word of caution about reusing our BitcodeWriter passes - we have only > ever cared about C99, so we definitely removed some code that relates to > exception handling (and possibly some other C++-specific features). We also > only expect IR constructs that come abo...

Hi mailing list, I has been working on a large project that is based on LLVM 3.1. Recently we are thinking to introduce an LLVM bc converter from LLVM 3.9 to LLVM 3.1, such that we can introduce some of the newest LLVM analyses and optimizations to our LLVM 3.1 based project. Have you worked on similar things that converting LLVM bc downward and has anything to share? Thanks Hongbin

...as well. 4.1 is not expected to read 3.x bitcode, and it will be an error to try to do so. With the new shift to version numbering (i.e. major versions are coming out faster - check the recent archives here), I am not sure how reliable bitcode will be as a storage format. This is something that the RenderScript team is also planning for, since 4.0 will be the last supported release that can easily read the 3.2 IR that we currently generate. No this is not the current situation: with the version numbering change, the policy changed as well. The new and current policy is: we support bitcode since 3.0 till...

...d it >>> will be an error to try to do so. With the new shift to version numbering >>> (i.e. major versions are coming out faster - check the recent archives >>> here), I am not sure how reliable bitcode will be as a storage format. This >>> is something that the RenderScript team is also planning for, since 4.0 >>> will be the last supported release that can easily read the 3.2 IR that we >>> currently generate. >>> >>> >>> No this is not the current situation: with the version numbering change, >>> the policy chang...

On 5 October 2011 16:18, Dan Gohman <gohman at apple.com> wrote: > I think you're overreacting here.  There is nothing about OpenCL, RenderScript, > or VMKit that requires LLVM IR be used like a Platform, as I defined it in my > first paragraph.  I'm aware that some people would like to use LLVM IR as a > Platform, and I'm saying that there are important high-level considerations > to make before doing so, and my impressi...

...ject in a short time, there might be some trend to make 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>

...as well. 4.1 is not expected to read 3.x bitcode, and it will be an error to try to do so. With the new shift to version numbering (i.e. major versions are coming out faster - check the recent archives here), I am not sure how reliable bitcode will be as a storage format. This is something that the RenderScript team is also planning for, since 4.0 will be the last supported release that can easily read the 3.2 IR that we currently generate. > > No this is not the current situation: with the version numbering change, the policy changed as well. The new and current policy is: we support bitcode since...

...ces a function? The same applies to bugpoint. What if the NamedMDNode is used in codegen, and removing it removes the crash? Simply put, I don't like this design, but my objections are weak and I lack an alternative plan. On the other side, there is a precedent for doing this. For example, RenderScript uses metadata to carry reflection information in the .bc files; their pipeline has that nothing else will touch the .bc files from the time their SDK produces it to the time the phone consumes it, so they assume the metadata wil still be there. RS would break if NamedMDNodes were stripped out....

..., so they would be useful for anyone else creating a new backend. 2) Using a subset of LLVM IR as a stable distribution format for portable executables. This is PNaCl's use case. PNaCl's IR subset omits various complex IR features, which we lower using the IR simplification passes [2]. Renderscript is an example of another project that uses IR as a stable distribution format, though I think currently Renderscript is not subsetting IR much. Some examples of PNaCl's IR simplification passes are: * Calling conventions lowering: ExpandVarArgs and ExpandByVal lower varargs and by-value arg...

...her design I can think of (and have thought of) is "module attributes" as an IR-level feature. They would be similar to function attributes. But if we can get away without creating a new IR feature, all the better! > On the other side, there is a precedent for doing this. For example, RenderScript uses metadata to carry reflection information in the .bc files; their pipeline has that nothing else will touch the .bc files from the time their SDK produces it to the time the phone consumes it, so they assume the metadata wil still be there. RS would break if NamedMDNodes were stripped out. >...

...ng with Clang: Joshua Cranmer – Mozilla Session #2 (11:05-12:35): Porting LLVM to a Next Generation DSP: Taylor Simpson – QulC LLVM MC In Practice: Jim Grosbach – Apple, Owen Anderson – Apple Session #3: (1:35-3:05): Using Clang in the Chromium project: Nico Weber, Hans Wennborg – Google Android Renderscript: Stephen Hines – Google Session #4 (1:35-3:05): Polly - First successful optimizations —How to Proceed?: Tobias Grosser – ENS/INRIA SKIR: Just-in-Time Compilation for Parrallelism with LLVM: Jeff Fifield – University of Colorado Session #5: (3:45-6:00): Exporting 3D scenes from Maya to WebGL usi...

...a host of possibilities for stable, portable software that will power a sea of nodes of the coming internet of virtual things. We look forward to working with the community in supporting this exciting new development in pervasive portable performance. [0] http://developer.android.com/guide/topics/renderscript/compute.html [1] https://developer.chrome.com/native-client/nacl-and-pnacl [2] https://www.khronos.org/spir [3] http://www.hsafoundation.com/hsa-developer-tools/ [4] https://developer.apple.com/library/watchos/documentation/IDEs/Conceptual/AppDistributionGuide/AppThinning/AppThinning.html#//apple_r...

On Wed, Oct 5, 2011 at 11:58 AM, Renato Golin <rengolin at systemcall.org>wrote: > On 5 October 2011 16:18, Dan Gohman <gohman at apple.com> wrote: > > I think you're overreacting here. There is nothing about OpenCL, > RenderScript, > > or VMKit that requires LLVM IR be used like a Platform, as I defined it > in my > > first paragraph. I'm aware that some people would like to use LLVM IR as > a > > Platform, and I'm saying that there are important high-level > considerations > > to ma...

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

...for that reason (and others), Android doesn't use the upstream releases. I was wondering if we could make anything so they would. The major benefit wouldn't be, as I explained, specifically for Google/Android, but for Android users, Linux users, Linux distros, LLVM library users (including Renderscript), etc. --renato

...dy interested in LLVM to join. o What is LLVM? LLVM is a collection of modular and reusable compiler and toolchain technologies. It is used as the base of many modern compilers such as clang (C/C++/Objective-C), GHC (Haskell), dragonegg (Ada, Fortran, ...), several commercial OpenCL compilers or RenderScript. Industry, open source community and researchers work on or with LLVM for many reasons. The most cited ones are the modern code base, the liberal BSD like license and the modularity. Around LLVM a large ecosystem was built that includes subprojects like dragonegg, vmkit, Polly, libc++, safecode...