Closed GoogleCodeExporter closed 9 years ago
Oh. The solution I propose is to change the semantics of saving an allocation.
Instead of allocating an ent and fiddling pointers, the saverec would hold an
ent
and an address and restore would copy the data back instead of exchanging
addresses.
Restore would still need to allocate an ent to free the copy space.
Original comment by luser.droog
on 4 Dec 2013 at 12:49
I don't this this is worth the effort. Restore still needs to allocate an ent.
So there's no real savings, just a delay.
Original comment by luser.droog
on 21 Feb 2015 at 10:18
Original issue reported on code.google.com by
luser.droog
on 4 Dec 2013 at 12:47