search for: _ideally_

...e to call funcs in native solibs. HOWEVER, to interpret code that refs funcs in the precompiled solibs, cint has to parse the relevant headers used by the precompiled solibs and cint has many limitations compared to gcc/g++ parser. Given that llvm bytecode might become a viable distribution format _ideally_ i would like to see a llvm object file format to carry similar kind of info for another pass of gcc/g++: so with: A.[h, cxx] => A.bc B.[h, cxx] => B.bc C.[h, cxx] => C.bc [ABC].bc => ABC.bc we can perform: llvm-g++ X.cxx -I ABC.bc without having to access the header files [ABC].h. B...

...D_ 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 > _ideally_ i would like to see a llvm object file format to carry > similar kind of info for another pass of gcc/g++: > > so with: > A.[h, cxx] => A.bc > B.[h, cxx] => B.bc > C.[h, cxx] => C.bc > [ABC].bc => ABC.bc > > we can perform: > llvm-g++ X.cxx -I ABC.bc >...