Closed
Bug 697666
Opened 13 years ago
Closed 13 years ago
Don't build the jstracer by default
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla10
People
(Reporter: matjk7, Assigned: matjk7)
References
Details
Attachments
(1 file)
2.01 KB,
patch
|
dmandelin
:
review+
|
Details | Diff | Splinter Review |
+++ This bug was initially created as a clone of Bug #693815 +++ Now that the tracer is disabled we should consider not building it by default, for a small win in binary/installer size.
Flags: in-testsuite-
Assignee | ||
Comment 1•13 years ago
|
||
Attachment #569907 -
Flags: review?(khuey)
Comment on attachment 569907 [details] [diff] [review] patch This looks fine, but I'd rather one of the js people sign off on it.
Attachment #569907 -
Flags: review?(khuey) → review?(dmandelin)
Updated•13 years ago
|
Attachment #569907 -
Flags: review?(dmandelin) → review+
Comment 3•13 years ago
|
||
Matheus, can you measure the binary/installer size win?
I have a local patch that removes the tracer entirely, it was about ~500KB from the js binary on Linux.
Comment 5•13 years ago
|
||
I'd like browser-level measurements, before and after :) I guess it's libxul that will end up smaller?
Comment 6•13 years ago
|
||
At least on Windows, libmozjs is still built separate from libxul.
Assignee | ||
Updated•13 years ago
|
Keywords: checkin-needed
Comment 7•13 years ago
|
||
http://hg.mozilla.org/integration/mozilla-inbound/rev/8c0a324fc4ed
Keywords: checkin-needed
Target Milestone: --- → mozilla10
Comment 8•13 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/8c0a324fc4ed
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•