Rust for Morello: Always-On Memory Safety, Even in Unsafe Code (Artifact)

Authors Sarah Harris, Simon Cooksey , Michael Vollmer , Mark Batty



PDF
Thumbnail PDF

Artifact Description

DARTS.9.2.25.pdf
  • Filesize: 0.49 MB
  • 2 pages

Document Identifiers

Author Details

Sarah Harris
  • University of Kent, Canterbury, UK
Simon Cooksey
  • University of Kent, Canterbury, UK
Michael Vollmer
  • University of Kent, Canterbury UK
Mark Batty
  • University of Kent, Canterbury, UK

Acknowledgements

This paper was greatly improved thanks to the responses of anonymous reviewers. We extend our thanks to Jessica Clarke for her invaluable help with CHERI LLVM.

Cite AsGet BibTex

Sarah Harris, Simon Cooksey, Michael Vollmer, and Mark Batty. Rust for Morello: Always-On Memory Safety, Even in Unsafe Code (Artifact). In Special Issue of the 37th European Conference on Object-Oriented Programming (ECOOP 2023). Dagstuhl Artifacts Series (DARTS), Volume 9, Issue 2, pp. 25:1-25:2, Schloss Dagstuhl – Leibniz-Zentrum für Informatik (2023)
https://doi.org/10.4230/DARTS.9.2.25

Artifact

Artifact Evaluation Policy

The artifact has been evaluated as described in the ECOOP 2023 Call for Artifacts and the ACM Artifact Review and Badging Policy

Subject Classification

ACM Subject Classification
  • Software and its engineering → Compilers
  • Software and its engineering → Software safety
  • Software and its engineering → Object oriented languages
Keywords
  • Compilers
  • Rust
  • Memory Safety
  • CHERI

Metrics

  • Access Statistics
  • Total Accesses (updated on a weekly basis)
    0
    PDF Downloads

References

  1. Arm. Arm® Architecture Reference Manual Supplement Morello for A-profile Architecture. Arm, 2020. Google Scholar
  2. Steve Klabnik, Carol Nichols, et al. The Rust Programming Language. The Rust Project Developers, 2021. URL: https://doc.rust-lang.org/1.55.0/book/.
  3. Nicholas D. Matsakis and Felix S. Klock. The rust language. Ada Lett., 34(3):103-104, October 2014. URL: https://doi.org/10.1145/2692956.2663188.
Questions / Remarks / Feedback
X

Feedback for Dagstuhl Publishing


Thanks for your feedback!

Feedback submitted

Could not send message

Please try again later or send an E-mail