Topic:
memory management by garbage collection
Topic:
safe use of pointers
Topic:
stacks
| |
Summary
For improved performance, memory may be allocated in regions or pools. A region may be deallocated as a whole, or each region may have different allocation policies. (cbb 12/07)
Subtopic: region allocator 
| Quote: uses growable regions for safe, explicit memory allocation without relying on a garbage collector [»jimT6_2002]
| | Quote: the Lea memory allocator works as well as custom allocators in six of eight applications; only region allocators do better [»bergED11_2002]
| | Quote: Cyclone has growable memory region, tagged union, polymorphism, and exceptions
|
Subtopic: security
| Quote: use region-based memory allocation for secure systems; smaller trusted computing base, avoids garbage collection pauses, region profiling, safe memory operations without leaks [»walkD7_2000]
| | Quote: secure, region-based memory allocation has a smaller trusted computing base with constant-time operations, easily identified bottlenecks, safe memory operations, and deallocated regions [»walkD7_2000]
| | Quote: Capability Language (CL), provably safe intermediate language for region-based memory management; supports aliasing and extensible OS; best for continuation-passing languages [»walkD7_2000]
|
Subtopic: region analysis
| Quote: use static, region analysis to prevent dereference of a non-live region; e.g., a block's local variables [»jimT6_2002]
| | Quote: use annotations to track memory regions across function calls
| | Quote: region interfaces specify the regions of memory accessed by a procedure
| | Quote: verify region interfaces by computing lower and upper bounds for each pointer and array index variable; a region interface must include the procedure's bounds and the region interfaces of its callees [»rugiR4_2001]
|
Subtopic: real-time
| Quote: static type system for region-based memory management in Java's real-time specification (RTSAJ) [»boyaC6_2003]
|
Subtopic: unique owner
| Quote: region-based, capability language tracks unique memory accesses; i.e., non-aliased accesses [»walkD7_2000]
| | Quote: track non-aliasing of memory regions via tagged capabilities and type system [»walkD7_2000]
| | Quote: use Flanagan and Abadi's race-free type system to prove that Guava objects are never concurrently accessed [»bacoDF10_2000]
| | Quote: in Guava every variable has a region type and every method has a region type signature
| | Quote: Guava variables assigned to regions with the same owner, i.e., a monitor, value, or no owner for new objects [»bacoDF10_2000]
|
Subtopic: heap+region
Quote: reap memory allocator acts like a region allocator until an object is deleted and then as a heap allocator
[»bergED11_2002]
|
Related Topics
Topic: memory management by garbage collection (116 items)
Topic: safe use of pointers (102 items)
Topic: stacks
(6 items)
|
