lhames wrote: > > llubi is designed to be used as a library. But we currently put all of the > > code under llvm/tools rather than llvm/lib. > > That shouldn't be a big issue (we do the same for llvm-exegesis and we pull > that in as a library in downstream projects). If it is, it's a pretty simple > refactoring to move the interpreter core into a proper library.
Random thought: depending on how the llubi lays out data structures in memory we could probably autogenerate and JIT some (maybe all?) the trampolines necessary to call native code. I don't have a use-case for that --it's just a thought bubble. https://github.com/llvm/llvm-project/pull/220113 _______________________________________________ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
