Closed Bug 1155197 Opened 9 years ago Closed 9 years ago

ubi::Node implementation of jsObjectClassName is needlessly indirect

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla40
Tracking Status
firefox40 --- fixed

People

(Reporter: jimb, Assigned: jimb)

Details

Attachments

(1 file)

The specialization of jsObjectClassName for JS::ubi::Nodes that refer to JSObjects is needlessly indirect. The jsObjectClassName override can be placed directly in the specialization of JS::ubi::Concrete for JSObject.

(This change also fixes ASAN failures in combination with some other patches I have yet to land, but I'll be durned if I know why.)
Attachment #8593373 - Flags: review?(terrence)
Comment on attachment 8593373 [details] [diff] [review]
For JS::ubi::Node, provide jsObjectClassName directly in JSObject specialization.

Review of attachment 8593373 [details] [diff] [review]:
-----------------------------------------------------------------

Sorry, this was what I should have done originally.
Attachment #8593373 - Flags: feedback+
Attachment #8593373 - Flags: review?(terrence) → review+
Assignee: nobody → jimb
Flags: in-testsuite+
Target Milestone: --- → mozilla40
https://hg.mozilla.org/mozilla-central/rev/e958fbf5cbbc
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: