Closed
Bug 1641352
Opened 5 years ago
Closed 5 years ago
Irregexp: GC-free regexp parsing
Categories
(Core :: JavaScript Engine, task, P2)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla79
Tracking | Status | |
---|---|---|
firefox79 | --- | fixed |
People
(Reporter: iain, Assigned: iain)
Details
Attachments
(2 files)
When parsing a regexp containing named captures, irregexp will allocate a FixedArray (which we implement using an ArrayObject) to hold the named capture data. This is undesirable for the SM parser, which only wants to know whether the regexp has valid syntax and should not allocate any GC things.
To fix this, I upstreamed a patch that adds a second entry point for parsing that only checks syntax (and enforces it with the V8 equivalent of an AutoAssertNoGC).
After a re-import, GC-free parse is a piece of cake.
Assignee | ||
Comment 1•5 years ago
|
||
This patch was auto-generated using import-irregexp.py.
Assignee | ||
Comment 2•5 years ago
|
||
Depends on D77296
Updated•5 years ago
|
Priority: -- → P2
Pushed by iireland@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a5279519ad7c
Re-import Irregexp r=mgaudet
https://hg.mozilla.org/integration/autoland/rev/84ba4c53cb3f
Use VerifyRegExpSyntax in CheckPatternSyntaxImpl r=mgaudet
Comment 4•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/a5279519ad7c
https://hg.mozilla.org/mozilla-central/rev/84ba4c53cb3f
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox79:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla79
You need to log in
before you can comment on or make changes to this bug.
Description
•