search for: openshadinglanguag

This may seem odd, but I want to really encourage the list to help Larry Gritz with this issue. I've been following the development of his project (OpenShadingLanguage) for months now and he has a *very* good use case for LLVM. It may be tempting to just "send him to the docs", but if anyone here can help take their use of LLVM to the next level, I can tell you that many, many people will benefit. Larry is a careful, committed and experienced coder and...

I have a DSL that creates LLVM IR on the fly and JITs to x86 at runtime. (https://github.com/imageworks/OpenShadingLanguage) Primarily, we have a main app that uses the library that implements our DSL. But we have other usage cases in which we have written dynamically-loaded plugins to 3rd party apps that we don't control, and our plugins use our language, which necessitates linking to LLVM. Unfortunately, LLVM...

...isticated" JIT user and are using either internal > APIs (either by integrating with LLVM, or by other C++ tricks), or are > using obscure or poorly documented public APIs (e.g., why is > runJITOnFunction exposed?) please make me aware of it! Hi, Daniel! We (http://code.google.com/p/openshadinglanguage/) are using LLVM to JIT. We do it all through the EE, retrieving JITed code through getPointerToFunction, not reaching into any JIT internals. -- Larry Gritz lg at larrygritz.com / lg at imageworks.com

On 11.05.2012, at 21:17, Larry Gritz wrote: > I have a DSL that creates LLVM IR on the fly and JITs to x86 at runtime. (https://github.com/imageworks/OpenShadingLanguage) > > Primarily, we have a main app that uses the library that implements our DSL. But we have other usage cases in which we have written dynamically-loaded plugins to 3rd party apps that we don't control, and our plugins use our language, which necessitates linking to LLVM. > >...

...taneously. I'm currently using the old JIT, but would happily switch to MCJIT if its speed (especially ability to lazily compile functions as the old one can) were to improve and memory was as good. (Here's the GitHub page for the project I'm thinking of: https://github.com/imageworks/OpenShadingLanguage/) On Dec 9, 2013, at 11:35 AM, "Kaylor, Andrew" <andrew.kaylor at intel.com> wrote: > Below is an outline of various usage models for MCJIT that I put together based on conversations at last month's LLVM Developer Meeting. If you're using or thinking about using MCJI...