search for: whatevervm

...create software for different environments: C/C++, JVM, CLR, Parrot, etc. I.e. one language for different environments, but not write once, run anywhere. Now what would be the role of LLVM in such an infrastructure? Just backend for C/C++ linkage, and I should go and look elsewhere for JVM/CLR/whateverVM? Should I look into LLVM subprojects? Which ones? Regards, Jo

On 5 October 2011 18:03, Justin Holewinski <justin.holewinski at gmail.com> wrote: >  So why must LLVM try to meet *both* goals?  Instead, different types of > front-ends can use custom intermediate representations that meet their > needs, and then lower to platform-specific LLVM IR before final code > emission.  I'm afraid that if LLVM gets into the game of trying to be the

...nt environments: C/C++, JVM, CLR, Parrot, etc. > I.e. one language for different environments, but not write once, run > anywhere. > > Now what would be the role of LLVM in such an infrastructure? > Just backend for C/C++ linkage, and I should go and look elsewhere for > JVM/CLR/whateverVM? > Should I look into LLVM subprojects? Which ones? It depends on what you want to do with the IR. If you want to create object files, LLVM is great. You just need to map the semantics of the various HLLs onto the LLVM IR language, as with any translator. For any kind of code-generator-ish...

...rent environments: C/C++, JVM, CLR, Parrot, etc. > I.e. one language for different environments, but not write once, run > anywhere. > > Now what would be the role of LLVM in such an infrastructure? > Just backend for C/C++ linkage, and I should go and look elsewhere for > JVM/CLR/whateverVM? > Should I look into LLVM subprojects? Which ones? It depends on what you want to do with the IR. If you want to create object files, LLVM is great. You just need to map the semantics of the various HLLs onto the LLVM IR language, as with any translator. For any kind of code-generator-ish t...