Closed Bug 513616 Opened 10 years ago Closed 9 years ago

[meta] nanojit: clean up register allocator

Categories

(Core Graveyard :: Nanojit, defect)

x86
Linux
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: njn, Assigned: njn)

References

Details

(Whiteboard: Tracking)

Nanojit's register allocator is poorly documented, hard to understand, and contains at least one subtle-but-pervasive bug.

I plan to improve this situation via a series of small patches that refactor code, improve documentation, and fix bugs.  (In fact, I've already started doing this.)  I plan to do it that way because I don't have a clear end goal in my mind, but I do see various small improvements to make, which well then enable further small improvements, etc.

Lest this seems like needless pedantry and tidy-ups:  making these changes will also improve my understanding of the register allocator in general, which will then help me make performance improvements to it later on.  (The code improvements will also make it easier for others to make performance improvements.)

This is a meta bug for tracking these improvements.
bug 514374 introduces an ugly use of allocator.free (~allocator.free). It should be cleaned up as part of this bug.
Blocks: 514374
(In reply to comment #1)
> bug 514374 introduces an ugly use of allocator.free (~allocator.free). It
> should be cleaned up as part of this bug.

I think we already had one occurrence of ~allocator.free anyway.

Also, I don't think bug 514374 should be blocked by this meta-bug, as it will prevent bug 514374 from being closed until this bug is closed.  Filing a new bug for removing ~allocator.free and making it block this bug would be better.
Depends on: 514551
(In reply to comment #2)
> 
> Also, I don't think bug 514374 should be blocked by this meta-bug, as it will
> prevent bug 514374 from being closed until this bug is closed.  Filing a new
> bug for removing ~allocator.free and making it block this bug would be better.

Done: bug 514551 created, and the 514374 block has been removed.
No longer blocks: 514374
Depends on: 516348
Depends on: 512181
Depends on: 515313
Depends on: 529725
Depends on: 538924
Component: JavaScript Engine → Nanojit
QA Contact: general → nanojit
Whiteboard: Tracking
Depends on: 514102
Depends on: 461065
Depends on: 572117
I'm gonna close this bug, it's served its purpose even though there are a couple of blocking bugs still open.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.