VMAllocators can already do this.
Code looks fine and harmless, may as well. Odd though, is this needed for making Assemblers short-lived? I'd have thought the opposite: that making them short-lived would *remove* the need for any kind of reset function (which plainly we're making-do without, presently).
The assembler and filter create temporary data, which we will allocate from a tempAlloc in the compiler (TraceRecorder and NativeRegExpCompiler). There the allocator will simply be destroyed. For the dataAlloc (currently allocator) and codeAlloc we can use reset().
Summary: add a way to flush CodeAllocs without deleting/recreating [nanojit] → TM: add a way to flush CodeAllocs without deleting/recreating [nanojit]
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.