| D. Grossman. Type-safe multithreading in Cyclone. In Proceedings of the 2003. |
....programs by allowing explicit memory management for objects shared between threads. It allows threads to communicate through objects in shared regions in addition to the heap. A shared region is deleted when all threads exit the region. However, programs in a system with only shared regions (e.g. [33]) will have memory leaks if two long lived threads communicate by creating objects in a shared region. This is because the objects will not be deleted until both threads exit the shared region. To solve this problem, we introduce the notion of subregions within a shared region. A subregion can be ....
....subtyping and method overriding. Cyclone [34] is a dialect of C with a region type system. Our work improves on these two systems by combining the benefits of ownership types and region types in a unified framework. An extension to Cyclone handles multithreaded programs and provides shared regions [33]. Our work improves on this by providing subregions in shared regions and portal fields in subregions, so that long lived threads can share objects without using the heap and without having memory leaks. Other systems for regions [29, 30] use runtime checks to ensure memory safety. These systems ....
D. Grossman. Type-safe multithreading in Cyclone. In Workshop on Types in Language Design and Implementation (TLDI), January 2003.
....programs by allowing explicit memory management for objects shared between threads. It allows threads to communicate through objects in shared regions in addition to the heap. A shared region is deleted when all threads exit the region. However, programs in a system with only shared regions (e.g. [33]) will have memory leaks if two long lived threads communicate by creating objects in a shared region. This is because the objects will not be deleted until both threads exit the shared region. To solve this problem, we introduce the notion of subregions within a shared region. A subregion can be ....
....subtyping and method overriding. Cyclone [34] is a dialect of C with a region type system. Our work improves on these two systems by combining the bene ts of ownership types and region types in a uni ed framework. An extension to Cyclone handles multithreaded programs and provides shared regions [33]. Our work improves on this by providing subregions in shared regions and portal elds in subregions, so that long lived threads can share objects without using the heap and without having memory leaks. Other systems for regions [29, 30] use runtime checks to ensure memory safety. These systems ....
D. Grossman. Type-safe multithreading in Cyclone. In Workshop on Types in Language Design and Implementation (TLDI), January 2003.
....by allowing explicit memory management for objects shared between threads. Our system allows threads to communicate through objects in shared regions in addition to the heap. A shared region is deleted when all threads exit the region. However, programs in a system with just shared regions (e.g. [27]) will have memory leaks if two long lived threads communicate by creating objects in a shared region. This is because the objects will not be deleted until both threads exit the shared region. To solve this problem, we introduce the notion of subregions within a shared region. A subregion can be ....
....that handles subtyping and method overriding. We improve on this by combining the benefits of ownership types and region types in a unified framework. Cyclone [28] is a dialect of C with a region type system. An extension to Cyclone handles multithreaded programs and provides shared regions [27]. Our work improves on this by providing subregions in shared regions and portal fields in subregions, so that long lived threads can share objects without using the heap and without having memory leaks. Other systems for regions [25, 26] use runtime checks to ensure memory safety. These systems ....
D. Grossman. Type-safe multithreading in Cyclone. In Workshop on Types in Language Design and Implementation (TLDI), January 2003.
No context found.
Dan Grossman. Type-safe multithreading in Cyclone. In ACM International Workshop on Types in Language Design and Implementation, pages 13--25, 2003.
No context found.
Dan Grossman. Type-safe multithreading in Cyclone. In ACM International Workshop on Types in Language Design and Implementation, pages 13--25, New Orleans, LA, January 2003.
No context found.
D. Grossman. Type-safe multithreading in Cyclone. In Proceedings of the 2003.
No context found.
D. Grossman. Type-safe multithreading in cyclone. In Proceedings of the 2003.
No context found.
D. Grossman. Type-safe multithreading in cyclone. In ACM Workshop on Types in Language Design and Implementation. ACM Press, 2003. 21
No context found.
Dan Grossman. Type-safe multithreading in Cyclone. In Workshop on Types in Language Design and Implementation (TLDI), January 2003.
No context found.
D. Grossman. Type-safe multithreading in Cyclone. In Proceedings of the ACM Workshop on Types in Language Design and Implementation, pages 13--25, 2003.
No context found.
D. Grossman. Type-safe multithreading in Cyclone. In TLDI 03: Types in Language Design and Implementation, pages 13--25. ACM Press, 2003.
No context found.
D. Grossman. Type-safe multithreading in Cyclone. In pages 13--25. ACM Press, 2003.
No context found.
D. Grossman. Type-safe multithreading in cyclone. In Workshop on Types in Language Design and Implementation (TLDI), Jan. 2003.
No context found.
Dan Grossman. Type-safe multithreading in Cyclone. In Workshop on Types in Language Design and Implementation (TLDI), January 2003.
No context found.
Dan Grossman. Type-safe multithreading in Cyclone. In Workshop on Types in Language Design and Implementation (TLDI), January 2003.
No context found.
D. Grossman. Type-safe multithreading in cyclone. In Workshop on Types in Language Design and Implementation (TLDI), Jan. 2003.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC