In or out?: putting write barriers in their place

dc.contributor.authorBlackburn, Stephen
dc.contributor.authorMcKinley, Kathryn
dc.date.accessioned2015-12-07T22:21:37Z
dc.date.issued2002
dc.date.updated2015-12-07T08:59:43Z
dc.description.abstractIn many garbage collected systems, the mutator performs a write barrier for every pointer update. Using generational garbage collectors, we study in depth three code placement options for remembered-set write barriers: inlined, out-of-line, and partially
dc.identifier.isbn1581135394
dc.identifier.urihttp://hdl.handle.net/1885/20126
dc.publisherAssociation for Computing Machinery Inc (ACM)
dc.relation.ispartofProceedings of the 3rd international symposium on memory management
dc.relation.isversionof1 Edition
dc.subjectKeywords: Data storage equipment; Database systems; Optimization; Performance; Program compilers; Copying collection; Garbage collected systems; Write barrier code; Java programming language Copying collection; Generational collection; Java; Write barriers
dc.titleIn or out?: putting write barriers in their place
dc.typeBook chapter
local.bibliographicCitation.lastpage184
local.bibliographicCitation.placeofpublicationNew York
local.bibliographicCitation.startpage175
local.contributor.affiliationBlackburn, Stephen, College of Engineering and Computer Science, ANU
local.contributor.affiliationMcKinley, Kathryn, University of Texas
local.contributor.authoremailu3789498@anu.edu.au
local.contributor.authoruidBlackburn, Stephen, u3789498
local.description.embargo2037-12-31
local.description.notesImported from ARIES
local.identifier.absfor080308 - Programming Languages
local.identifier.ariespublicationU4049553xPUB11
local.identifier.scopusID2-s2.0-1442313462
local.identifier.uidSubmittedByU4049553
local.type.statusPublished Version

Downloads

Original bundle
Now showing 1 - 1 of 1
No Thumbnail Available
Name:
01_Blackburn_In_or_out?:_putting_write_2002.pdf
Size:
118.54 KB
Format:
Adobe Portable Document Format