FFI story - Githubissues

rrthomas / mit

A simple stack-based VM

Other

10 stars 3 forks source link

FFI story #25

Open rrthomas opened 5 years ago

rrthomas commented 5 years ago

How far can we get with parsing header files (with LLVM?) and debug builds of libraries (available in most GNU/Linux distros)? Better tools are available in some cases, e.g. for GNOME libraries (GObject introspection) (and Qt?). How well can we do with gnulib's libposix? With libc? With Linux system calls? In any case, no need for full automation if we can automate e.g. all C functions and simple constant #defines.

apt1002 commented 5 years ago

Aims:

We want to have machine-readable stack pictures for Mit object libraries (which depend only on Mit's WORD_SIZE, not properties of the host).
We also want to make it as easy as possible to expose native C APIs to Mit code, as Mit object libraries.
For the benefit of dynamic languages, it should be possible to machine-generate stack pictures for native C APIs on the fly, though these may be host-specific.