Jed Brown

Is it appropriate to add a test that pulls in rsmpi? That would require building a Rust toolchain using this Enzyme and then `cargo test` (which would build rsmpi, assuming...

For C (and CPU), the header is included in a corresponding `*.c` source file that does its registration and field specification. I think the question is how to move that...

I think `build.rs` is a better solution and user experience, though it would be possible for `/cpu/self` to invoke a regular compiler (create a temporary file, compile into a shared...

If `build.rs` is compiling the C code, it can also be declaring compatible extern functions on the Rust side. It could use bindgen for that, though it's overkill when there...

There could be a `libceed-builder` crate (to be used by `build.rs`) that would automate locating and building such things. The README comment is about shared library paths if you disable...

RPATH is a choice for the person linking, not a choice that `libxyz.so` can make. Since there are multiple syntaxes for rpath flags, `petsc.pc` does provide a key `ldflag_rpath` with...

One other optional comment about Rust is its `noalias` by default, where C requires `restrict` and `C++` doesn't even have that (in the standard). This is often a substantial performance...

Would you mind updating the figures for nanogemm? Regarding noalias, I was thinking as much of the caller's code, though I also wouldn't say a missed optimization in rustc/LLVM negates...

I should have written more carefully. I was thinking of having `libceed/Cargo.toml` use ```toml [dependencies] libceed-sys = { version = "0.12", path = "../libceed-sys", default-features = false} ``` but skipping...

Do you mean something other than the existing `system` feature? To clarify, is there reason to support building a private shared `libceed.so`/`libceed.dylib` (in most cases implying that the user must...