Changeset 7f995d70
- Timestamp:
- Aug 12, 2025, 9:07:08 PM (5 weeks ago)
- Branches:
- master
- Children:
- 499a45a
- Parents:
- 6c58850
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/theses/mike_brooks_MMath/uw-ethesis-frontpgs.tex
r6c58850 r7f995d70 129 129 \begin{center}\textbf{Abstract}\end{center} 130 130 131 This is the abstract. 131 All modern programming languages provide three high-level containers (collections): array, linked-list, and string. 132 Often array is part of the programming language, while linked-list is built from (recursive) pointer types, and string from a combination of array and linked-list. 133 For all three types, languages and/or their libraries supply varying degrees of high-level mechanisms for manipulating these objects at the bulk and component level, such as copying, slicing, extracting, and iterating among elements. 134 Unfortunately, these three aspects of C cause 60\%--70\% of the reported software vulnerabilities involved memory errors, and 70\%-80\% of hacker attack-vectors target these types. 135 Therefore, hardening these three C types goes a long way to make the majority of C programs safer. 136 137 This work looks at extending these three foundational container types in the programming language \CFA, which is a new dialect of the C programming language. 138 The thesis describes improvements made to the \CFA language design, both syntax and semantics, to support the container features, and the source code created within the \CFA compiler, libraries, and runtime system to implement these features. 139 This work leverages preexisting work within the compiler's type and runtime systems generated by prior students working on the \CFA project. 140 141 Overall, this work has produced significant syntactic and semantic improvements to C's container types. 142 \begin{enumerate}[leftmargin=*] 143 \item 144 Introduce a small number of subtle changes to the typing rules for the C array, while still achieving significant backwards compatibility 145 \item 146 Create a new polymorphic mechanism in the \CFA @forall@ clause to specify array dimension values, similar to a fixed-typed parameter in a \CC \lstinline[language=C++]{template}. 147 The new array type, enabled by prior features, defines an array with guaranteed runtime bound checks (often optimizer-removable) and implicit (guaranteed accurate) inter-function length communication. 148 \item 149 Create a new polymorphic list type and its runtime library following the established design pattern of intrusive link-fields for performance reasons, especially in concurrent programs. 150 \item 151 Create a new string type and runtime library comparable to the \CC @string@ type, including analogous coexistence with raw-character pointers, enabling programs to work with strings by value, without incurring excessive copying. 152 Substrings are supported, including the ability for overlapping ranges to share edits transparently. 153 \end{enumerate} 154 The thesis includes a performance evaluation that shows the \CFA containers perform comparably with their C counterparts in many programming cases. 132 155 133 156 \cleardoublepage
Note:
See TracChangeset
for help on using the changeset viewer.