Ignore:
Timestamp:
Apr 28, 2026, 1:17:46 AM (24 hours ago)
Author:
Michael Brooks <mlbrooks@…>
Branches:
master
Children:
9a35b43
Parents:
b0fff42
Message:

take pg1 out of the weeds on c--rust translation

File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/theses/mike_brooks_MMath/intro.tex

    rb0fff42 r3c5fdb5  
    2222\end{itemize}
    2323
    24 An effort at translating C to safe Rust~\cite{Emre2022} has pointers as the stand-out difficult aspect to analyze.
     24An effort at translating C code to the safe subset of the now-famously safe language Rust~\cite{Emre2022} shows pointers as the stand-out difficult aspect to analyze.
     25It demonstrates the difficulty of automatically determining pointer-referent lifetimes in that its success claim is to reduce the occurrence rate of unsafe dereference operations to about once per 100 lines of code.
     26
     27\begin{comment}
    2528It demonstrates the difficulty of analyzing C pointers for safety.
    2629It first puts a corpus of C programs through a naive Rust translation, which ``succeeds'' by leaving many uses of Rust's \lstinline{unsafe} marker.
     
    3235% 3.3 = 1398/413,428 * 1000
    3336% 220 ~= (99,101 [@tab3.5] - 9631 [@tab4.2] ) / 413,428 [@tab 3.1] * 1000
    34 
     37\end{comment}
    3538
    3639A tool for analyzing C code's use of linked data structures (including, \eg skip list and binary tree) found variations of the linked-list shape to be present in most of the programs in its corpus~\cite{White2016}.
Note: See TracChangeset for help on using the changeset viewer.