Jacob Lifshay

imho this is still useful, though it may need to be updated to the latest portable-simd API.

> This means that all of `1 - 2`, `panic!()`, `loop {}` and `[1, 2, 3][3]` are not well formed as constants. `1 - 2` evaluates successfully for signed types....

there probably aren't many Rust projects on there, but it would be nice to support [Debian Salsa](https://salsa.debian.org) as well

Also running into this error when attempting to build [`maturin` v0.8.3](https://github.com/PyO3/maturin) on powerpc64le-unknown-linux-gnu: ``` thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /home/jacob/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.15/build.rs:378:10 ```

I'd expect qemu could be used, you can check and see what rust uses for its testing infrastructure...

Also, you could get some CI infrastructure from https://osuosl.org/services/powerdev/

It might be a good idea to deprecate/remove `write_to_file` and `write_to_memory_buffer` and create new functions `compile_to_file` and `compile_to_memory_buffer`, since the `write_*` function names are misleading.

for the owning type, just use `MemoryBuffer

Well, IMHO, `'static` just means you don't have to worry about the type holding references to things that might be left dangling -- exactly what you want. Just like a...

Hmm, maybe it could be done the other way around: Contexts would have the lifetime of the ExecutionEngine, since the ExecutionEngine handles multiple Contexts. Alternative idea: the safe ExecutionEngine wrapper...