Closed
Bug 1483340
Opened 7 years ago
Closed 7 years ago
Write a CacheIR test case for comparisons involving an HTMLDDA object
Categories
(Core :: JavaScript Engine: JIT, enhancement, P3)
Core
JavaScript Engine: JIT
Tracking
()
RESOLVED
FIXED
mozilla68
People
(Reporter: mgaudet, Assigned: vincent, Mentored)
References
(Blocks 1 open bug)
Details
(Keywords: good-first-bug)
Attachments
(1 file)
js/src/jit-test/tests/cacheir/compare.js should be modified to add test cases that use the builtin createIsHTMLDDA [1] to make sure that the CacheIR compare handling for these exotic objects doesn't regress
The important oddities of these objects are documented in the ECMAScript standard [2], Section B.3.7
[1]: https://searchfox.org/mozilla-central/rev/2466b82b729765fb0a3ab62f812c1a96a7362478/js/src/shell/js.cpp#7338
[2]: https://tc39.github.io/ecma262/#sec-IsHTMLDDA-internal-slot
| Reporter | ||
Updated•7 years ago
|
Component: JavaScript Engine → JavaScript Engine: JIT
Updated•7 years ago
|
Mentor: mgaudet
Priority: -- → P3
| Assignee | ||
Comment 1•7 years ago
|
||
Can I work on this? :-)
| Assignee | ||
Updated•7 years ago
|
Flags: needinfo?(mgaudet)
| Reporter | ||
Comment 2•7 years ago
|
||
Hey, it's definitely free for the taking.
Where you'd want to add test cases is https://searchfox.org/mozilla-central/source/js/src/jit-test/tests/cacheir/compare.js
You'll want to test all the ways in which an IsHTMLDDA object differ from regular objects.
You'll want to build the SpiderMonkey shell and then test it using ../jit-test/jit_test.py --jitflags=all ./dist/bin/js cacheir/compare.js.
Flags: needinfo?(mgaudet)
| Assignee | ||
Updated•7 years ago
|
Assignee: nobody → vi.le
| Assignee | ||
Comment 3•7 years ago
|
||
Pushed by mgaudet@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/da9552ba5fec
Add CacheIR test case for HTMLDDA object;r=mgaudet
| Reporter | ||
Comment 5•7 years ago
|
||
Thanks so much for this! Let me know if you need help finding another bug to jump on.
Comment 6•7 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox68:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
Updated•6 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•