Closed Bug 557898 Opened 14 years ago Closed 13 years ago

Optimize GC allocation by avoiding compare-and-branch on size

Categories

(Tamarin Graveyard :: Garbage Collection (mmGC), defect)

Product:
Tamarin Graveyard
Component:
Garbage Collection (mmGC)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 591914
Milestone:
Future

People

(Reporter: lhansen, Unassigned)

Details

(Whiteboard: PACMAN) 

In bug #528338, Tommy writes: "There's probably a way to get rid of the if (size <= kLargestAlloc) by adding the large alloc to the allocs table and doing a little smarter size->index calculation."

There might be - we don't know.  The compare-and-branch probably does not cost more than a couple of ALU instructions (it's almost perfectly predictable) so any mechanism that gets rid of it must not introduce any code, probably.

Initially targeting "Future" as it's investigative / speculative.
Whiteboard: PACMAN
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.