Closed
Bug 1717758
Opened 3 years ago
Closed 3 years ago
Make CompileToStencilXDR return opaque object
Categories
(Core :: JavaScript Engine, task)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
91 Branch
| Tracking | Status | |
|---|---|---|
| firefox91 | --- | fixed |
People
(Reporter: arai, Assigned: arai)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
https://phabricator.services.mozilla.com/D118312#inline-655826
Currently CompileToStencilXDR returns an ArrayBuffer, but it's used only by EvalStencilXDR, and modifying the ArrayBuffer content isn't something useful for automated tests, unless the format is completely fixed (stabilized?).
Also, if we want to fuzz XDR decoder, it should be done with explicit/dedicate testing function that understands the format, instead of operating on the ArrayBuffer with normal typed-array API.
|
Assignee | |
Comment 1•3 years ago
|
||
|
||
Updated•3 years ago
|
Assignee: nobody → arai.unmht
Status: NEW → ASSIGNED
Pushed by arai_a@mac.com:
https://hg.mozilla.org/integration/autoland/rev/2908e06fa1ac
Return opaque object from compileToStencilXDR testing function, and mark it fuzzing-safe. r=nbp
|
||
Comment 3•3 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox91:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
|
|
Assignee | |
Updated•3 years ago
|
Blocks: stencil-backlog
You need to log in
before you can comment on or make changes to this bug.
Description
•