search for: _based_

I am asking this question to see if it is possible or desirable to build a compilation/runtime system for C/C++ that can support the following: 1. allow bc to call native (in dynamically loaded *.so) 2. allow native to call bc (through JIT or interpreter) 3. can compile/interpret C/C++ sources _BASED_ on type info in precompiled bc Motivation: The class files produced by the java compiler carries sufficient information that another pass of compilation of java source can be done by including clas/jar files only: A.java => A.class B.java => B.class C.java => C.class [ABC].class => A...

...pport the > following: > > 1. allow bc to call native (in dynamically loaded *.so) You can do this today, e.g., with lli -load=native.so file.bc > 2. allow native to call bc (through JIT or interpreter) You can also do this today as well. > 3. can compile/interpret C/C++ sources _BASED_ on type info in > precompiled bc OK, I didn't quite understand what you meant at first, but it makes sense with the rest of your message. See the end of my response. > Motivation: [skip java-related stuff] > Given that llvm bytecode might become a viable distribution format > _i...