Closed
Bug 589727
Opened 16 years ago
Closed 16 years ago
Typed Float32 Arrays broken on mozilla-central trunk
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| blocking2.0 | --- | beta5+ |
People
(Reporter: humph, Unassigned)
References
Details
(Keywords: regression, Whiteboard: fixed-in-tracemonkey)
Attachments
(1 file)
|
446 bytes,
patch
|
sayrer
:
review+
|
Details | Diff | Splinter Review |
The bug in bug 586387 was re-introduced with this recent merge:
http://hg.mozilla.org/mozilla-central/rev/7fb1bd5802f0.
Comment 1•16 years ago
|
||
no test in bug 586387. boo.
| Reporter | ||
Comment 2•16 years ago
|
||
| Reporter | ||
Comment 3•16 years ago
|
||
I haven't written trace-tests before, but following what I see in the tree, maybe this is what you want. It certainly fails here.
Attachment #468307 -
Flags: review?(sayrer)
Comment 4•16 years ago
|
||
OK, so what happened here is this:
vlad checked in changes to nanojit that were clobbered by a nanojit import. All nanojit changes must go to nanojit-central to avoid this fate.
we didn't land a test for this in TM, which would have caught this problem quite quickly.
| Reporter | ||
Comment 5•16 years ago
|
||
Thanks for looking at this, Robert. Do you have an ETA for re-landing these bits on m-c? My audio landing is blocked on it being there, and I'm hoping to get it in prior to feature freeze.
If there's more or different tests you need, let me know and I'll try to help.
blocking2.0: --- → beta5+
Comment 6•16 years ago
|
||
The test was landed here:
http://hg.mozilla.org/tracemonkey/rev/7f8a3c0942fb
The previously-clobbered nanojit change was relanded, see bug 586387 for details.
Whiteboard: fixed-in-tracemonkey
Updated•16 years ago
|
Attachment #468307 -
Flags: review?(sayrer) → review+
| Reporter | ||
Comment 7•16 years ago
|
||
That's great, thanks for landing there. How about mozilla-central?
Comment 8•16 years ago
|
||
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•