Hoist YARR WTF::BumpPointerAllocator to ThreadData and consider replacing it with LifoAlloc adapter

RESOLVED WONTFIX

Status

()

Core
JavaScript Engine
RESOLVED WONTFIX
6 years ago
3 years ago

People

(Reporter: cdleary, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [MemShrink:P3])

I haven't looked at it too hard, but the BumpPointerAllocator for YARR seems to do roughly what our LifoAlloc does, which lives on the thread data already as tempLifoAlloc. We shouldn't have more than one LIFO allocator if we can help it.
Blocks: 673274
I'm going to label this as MemShrink, since consolidating to one LIFO-style allocator could possibly avoid alloc/free thrashing in the WTF::BumpPointerAllocator and multiple simultaneously outstanding chunks of memory.
No longer blocks: 673274
Whiteboard: [MemShrink]
Whiteboard: [MemShrink] → [MemShrink:P3]
This bug is no longer relevant because YARR has been replaced by irregexp in bug 976446.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
See Also: → bug 976446
Summary: Hoist WTF::BumpPointerAllocator to ThreadData and consider replacing it with LifoAlloc adapter → Hoist YARR WTF::BumpPointerAllocator to ThreadData and consider replacing it with LifoAlloc adapter
You need to log in before you can comment on or make changes to this bug.