Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Peter Boyland

dblp:259/9517 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
1since 2021 · last 2023
0000-0002-2530-3329ORCID · reported

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1 · 1 since 2021

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Program synthesis and code generation · 33% Software maintenance and evolution · 33% Programming languages and type systems · 33%
Network and information security
1 paper
Systems and software security · 100%

Topics — the 3 heaviest of 4, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Program synthesis and code generation
code translation
0.712023
Aliasing Limits on Translating C to Safe Rust · Proc. ACM Program. Lang. 2023
Software maintenance and evolution › software reengineering › software modernization › software migration › language migration
c-to-rust translation
0.712023
Aliasing Limits on Translating C to Safe Rust · Proc. ACM Program. Lang. 2023
Systems and software security
memory safety
0.212023
Aliasing Limits on Translating C to Safe Rust · Proc. ACM Program. Lang. 2023

Methods — techniques the papers use, named apart from their topics

pointer analysis · 1.3ownership inference · 1.3
YearPublicationVenuePosition
2023 Aliasing Limits on Translating C to Safe Rust
abstract
The Rust language was created to provide safe low-level systems programming. There is both industrial and academic interest in the problem of (semi-)automatically translating C code to Rust in order to exploit Rust's safety guarantees. We study the effectiveness and limitations of existing techniques for automatically translating unsafe raw pointers (in Rust programs translated from C) into safe Rust references via ownership and lifetime inference. Our novel evaluation methodology enables our study to extend beyond prior studies, and to discover new information contradicting the conclusions of prior studies. We find that existing translation methods are severely limited by a lack of precision in the Rust compiler's safety checker, causing many safe pointer manipulations to be labeled as potentially unsafe. Leveraging this information, we propose methods for improving translation, based on encoding the results of a more precise analysis in a manner that is understandable to an unmodified Rust compiler. We implement one of our proposed methods, increasing the number of pointers that can be translated to safe Rust references by 75% over the baseline (from 12% to 21% of all pointers).
Mehmet Emre, Peter Boyland, Aesha Parekh, Ryan Schroeder, Kyle Dewey, Ben Hardekopf
Proc. ACM Program. Lang.2