Region-based memory management in cyclone

By D. Grossman, G. Morrisett, Trevor Jim, Michael W. Hicks, Yanling Wang, J. Cheney. ACM-SIGPLAN Symposium on Programming Language Design and Implementation, 2002

450 citations recorded by the source corpus.

Subfields: Artificial Intelligence, Computer Networks and Communications, Hardware and Architecture

View Paper: https://www.semanticscholar.org/paper/562a27c239847fb5940af3601b30f43f7d24f6f7

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Artificial Intelligence

In Computer Networks and Communications

In Hardware and Architecture

Citations in the corpus

RustBelt: securing the foundations of the rust programming language (2017, background): “…including łownership typež systems [Clarke et al. 1998]; region-or typestate-based systems for łsafe Cž programming in languages like Cyclone [Jim et al. 2002] and Vault [DeLine and Fähndrich 2001]; and substructural type systems like Ynot [Nanevski et al. 2008], Alms [Tov and Pucella 2011],…”
Cyclone: A Safe Dialect of C (2002, background): “Cyclone’s region analysis is described in greater detail in a separate paper [21].”
DieHard: probabilistic memory safety for unsafe languages (2006, methodology): “While Cyclone uses region-based memory management and safe explicit deallocation [16, 38], CCured relies on the BDW garbage collector to protect against double frees and dangling pointers.”
Subtyping for session types in the pi calculus (2005, background): “Cyclone [12] is a C-like type-safe polymorphic imperative language.”
Ownership, encapsulation and the disjointness of type and effect (2002, background): “Neither Cyclone nor Vault deal with objects and the consequent subtyping.”
SoftBound: highly compatible and complete spatial memory safety for c (2009, background): “Other previously proposed complementary techniques such as conservative garbage collection [9], reference-counted smart pointers, probabilistic approximations of an infinite-sized heap [6], temporal capabilities [5, 47], or regionbased memory management [19, 23, 25] may be employed to detect or prev”
Ownership types for safe programming: preventing data races and deadlocks (2002, unknown): “ment [16, 25].”
LLVM: a compilation framework for lifelong program analysis & transformation (2004, unknown): “to avoid using interprocedural techniques [17, 23]).”
LIFT: A Low-Overhead Practical Information Flow Tracking System for Detecting Security Attacks (2006, methodology): “Security Attack Detection Methods Some softwarebased dynamic methods detect certain types of vulnerabilities at runtime by statically or dynamically instrumenting source code [22, 26] or binary code [23, 33].”
Interprocedural compatibility analysis for static object preallocation (2003, background): “Other researchers [17] require the programmer to provide annotations (via a rich type systems) that specify the region that each object is allocated into.”