Closed
Bug 642003
Opened 13 years ago
Closed 5 months ago
[meta] Analyze v8 benchmark scores in detail
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: dmandelin, Unassigned)
References
(Depends on 2 open bugs)
Details
(Keywords: meta)
We need to know what we need to do besides type inference here. What will GC fix and what do we need other work for?
Comment 1•13 years ago
|
||
https://wiki.mozilla.org/V8bench_Info is a ready-made one-stop shop for holding info about v8bench. It would be great if what's learned could be put into that wiki page, so that the information isn't fragmented across a bunch of bugs.
Reporter | ||
Comment 2•13 years ago
|
||
(In reply to comment #1) > https://wiki.mozilla.org/V8bench_Info is a ready-made one-stop shop for holding > info about v8bench. It would be great if what's learned could be put into that > wiki page, so that the information isn't fragmented across a bunch of bugs. I'll add summaries there when I get a chance.
Reporter | ||
Comment 3•13 years ago
|
||
(In reply to comment #2) > (In reply to comment #1) > > https://wiki.mozilla.org/V8bench_Info is a ready-made one-stop shop for holding > > info about v8bench. It would be great if what's learned could be put into that > > wiki page, so that the information isn't fragmented across a bunch of bugs. > > I'll add summaries there when I get a chance. OK, I've summarized my findings there.
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Updated•2 years ago
|
Severity: normal → S3
Updated•5 months ago
|
Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•