Closed Bug 514045 Opened 16 years ago Closed 15 years ago

Dynamic strings should probably use unmanaged gc memory

Categories

(Tamarin Graveyard :: Virtual Machine, defect, P4)

defect

Tracking

(Not tracked)

VERIFIED WONTFIX
Q3 11 - Serrano

People

(Reporter: stejohns, Assigned: stejohns)

Details

They currently use managed memory but the lifetime is controlled. Before making this change, memory and speed impact must be measured. Also, the "mmfx" api will need to have an equivalent to GC::Size(), to recover the actual memory allocated (as opposed to requested).
size_t mmfx_size(ptr, requestedSize) was the api i thought of when this topic came up. passing in requestedSize lets this be a no-op when mmfx_new/delete map to the standard impls.
Priority: -- → P3
Target Milestone: --- → flash10.1
Priority: P3 → P4
Target Milestone: flash10.1 → flash10.2
Another issue is that if we allocate the memory outside the GC heap then GC accounting will be off, this will add to the cost as we can't allow that. So it's probably a wash - string data are pointerfree and don't stress the GC much.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
bulk verifying resolved !fixed issues
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.