You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JIT is quite perilous from the correctness and security standpoints, but this is currently not addressed in the README.
If you write an interpreter in Rust you can use rustc to guarantee memory safety, but with JIT you're essentially emitting arbitrary assembly at runtime and jumping into it. No amount of memory safety guarantees on the original code will guarantee memory safety in the generated code.
Please document how this is addressed (if at all).
P.S. Thank you for the very interesting project that's pushing the boundaries of safety as we know it!
The text was updated successfully, but these errors were encountered:
Shnatsel
changed the title
JIT safety not documented
JIT safety is not documented
Nov 6, 2019
JIT is quite perilous from the correctness and security standpoints, but this is currently not addressed in the README.
If you write an interpreter in Rust you can use
rustc
to guarantee memory safety, but with JIT you're essentially emitting arbitrary assembly at runtime and jumping into it. No amount of memory safety guarantees on the original code will guarantee memory safety in the generated code.Please document how this is addressed (if at all).
P.S. Thank you for the very interesting project that's pushing the boundaries of safety as we know it!
The text was updated successfully, but these errors were encountered: